Deliver an API and MCP server the customer owns.
Build work happens in the customer's repository and infrastructure. The dashboard records the handoff, staging URL, acceptance checklist and monitoring connection.
Handoff package
| Artifact | Purpose |
|---|---|
| API source | Customer-owned implementation |
| MCP server | One Streamable HTTP endpoint for assistants |
| OpenAPI document | Machine-readable REST contract |
| Docker / CI files | Customer's deployment pipeline |
| Checks | Expected capabilities and responses |
| Rollback notes | How to return to the previous version |
Acceptance path
- An Owner can put the generated server in a new private repository from OpenAPI to MCP. That records the repository and marks the source delivered. It does not deploy the server or start monitoring.
- Customer deploys to staging.
- Knotbind runs tool discovery and a Baseline.
- Customer tests capabilities in the real assistants.
- Owner accepts the handoff and monitoring starts.
The server-side handoff publisher uses
KNOTBIND_GITHUB_TOKEN, or a GitHub App when that token is
empty (KNOTBIND_GITHUB_APP_ID,
KNOTBIND_GITHUB_APP_INSTALLATION_ID, and
KNOTBIND_GITHUB_APP_PRIVATE_KEY). The App key stays in the
process environment. After an Owner deploys an approved repair, Knotbind
also opens one pull request in that configured repository. A failed pull
request does not undo the deployment.