Skip to content
Back to search

ssis-export-toolkit

MCP server that lets Claude generate, deploy, schedule and run SSIS packages exporting SQL Server tables to Azure Blob Storage as CSV. Signed requests, policy-checked, no secrets in packages.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hachecom--ssis-export-toolkit/badge.svg)](/listings/hachecom--ssis-export-toolkit)

HTML

<a href="/listings/hachecom--ssis-export-toolkit"><img src="/api/listings/hachecom--ssis-export-toolkit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 62 lines
  1. # ssis-export-toolkit
  2. An MCP server that lets an AI assistant (Claude) create, deploy, schedule and run **SSIS packages** that move SQL Server tables to
  3. **Azure Blob Storage** as CSV. Governed by design: one installation per SQL Server VM, one MCP per person, every action signed and
  4. policy-checked.
  5. You give orders in plain language ("export `dbo.Orders` to Blob Storage every day at 03:00"). The assistant turns them into a
  6. declarative spec, generates the `.dtsx` packages and the project, and a small signed-request executor on the VM deploys them to
  7. SSISDB, runs them, verifies the result and creates the SQL Agent job. Nobody runs scripts by hand except the one-time installation by
  8. the administrator.
  9. ```
  10. Claude + ssis-builder MCP (your PC) --signed request--> Blob Storage (ssis_control/) <--pull every minute-- executor (VM) --> SSISDB / SQL Agent
  11. ```
  12. ## Why
  13. - **Repetitive packages, generated.** Export packages differ only in table, columns, types and file name. A spec describes the
  14. interface; the generator renders the package deterministically (same input, same output, diff-friendly).
  15. - **Safe by construction.** No secrets in packages or specs; the storage key lives in the VM's DPAPI store. Source queries must be
  16. `SELECT`-only. Requests are Ed25519-signed per person and checked against a policy that only an administrator can change.
  17. - **Auditable.** Every action records who did it (executor log, request status, job description).
  18. ## Who does what
  19. | Role | What | Guide |
  20. |---|---|---|
  21. | Administrator (once per VM) | install the executor, store the storage key, authorise colleagues, own the security rules | [docs/ADMIN_GUIDE.md](docs/ADMIN_GUIDE.md) |
  22. | User (once per PC) | clone, run `scripts/ssis_builder_setup_pc.ps1`, send your public key to the administrator | [docs/USER_GUIDE.md](docs/USER_GUIDE.md) |
  23. | Everybody, on each release | `git pull`; VM-side changes need the administrator | [docs/UPGRADING.md](docs/UPGRADING.md) |
  24. ## Tools (MCP)
  25. - Specs and packages: `ssis_spec_create`, `ssis_interface_spec_create`, `ssis_validate`, `ssis_generate_export`, `ssis_generate_bundle`.
  26. - VM operations: `ssis_executor_status`, `ssis_deploy`, `ssis_configure`, `ssis_run`, `ssis_verify`, `ssis_cleanup`.
  27. - Jobs: `ssis_schedule`, `ssis_job_enable`, `ssis_job_status`, `ssis_job_delete`.
  28. - Administration and identity: `ssis_executor_installer`, `ssis_invite_colleague`, `ssis_my_public_key`.
  29. ## Safety model (short)
  30. Allowed operations, databases, object-name prefixes and containers are defined in a policy that lives on the VM. A request is
  31. rejected unless its signature verifies, it has not expired (max 60 min), it was never seen before (replay protection) and it passes
  32. the policy. Details: [docs/executor.md](docs/executor.md).
  33. ## Status
  34. Early-stage. The spec, generators, signing and executor logic are covered by unit tests (simulated channel and SSISDB). Generated
  35. `.dtsx` files cannot be validated without SSDT/`dtexec`: run the first deployment against a test server. Imports (Blob Storage ->
  36. table) are specified but the import generator is not built yet; see [package generators](docs/package-generators.md).
  37. ## Develop
  38. ```powershell
  39. python -m venv .venv; .\.venv\Scripts\pip install -r requirements.txt
  40. .\.venv\Scripts\python -m unittest discover -s tests
  41. ```
  42. Docs: [package generators](docs/package-generators.md), [interface spec v2](docs/interface-spec-v2.md), [executor](docs/executor.md).
  43. ## License
  44. MIT, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.