Repository reference
MCP server and connector authoring
Build an upstream MCP server that composes cleanly, with stable tools, bounded schemas, explicit side effects, safe errors, and documented security expectations.
This is the current integration contract, not a shipped connector SDK or publication pipeline. Container isolation and broader MCP capability support remain planned.
Use this reference when
- Designing a remote HTTP MCP server for registration and composition.
- Defining tool schemas, risk, provider scopes, idempotency, pagination, limits, and machine-readable errors.
- Testing authentication, SSRF, egress, denial, timeout, session revocation, provenance, and audit behavior.
What it covers
Protocol and tool contract
The supported MCP slice, minimum initialize/list/call behavior, stable naming, self-contained JSON Schema, and bounded payloads.
Security and side effects
Credential-free endpoints, future credential brokerage, DNS/egress controls, risk labels, idempotency, retries, and safe errors.
Integration and publication
A ten-step local verification loop and the provenance, SBOM, compatibility, documentation, and revocation evidence future publication requires.
Read the full repository reference
This page is a discovery map, not a shortened replacement for the maintained source. The complete reference includes exact tables, commands, boundaries, and cross-links in docs/connector-authoring.md.
Open the complete Markdown reference ↗