Agent Connector SDK

Build secure connectors once. Serve, synchronize, and write back through one governed contract.
_{The typed source-integration boundary for MCP services and Epistemic Graph.}

Documentation · Capabilities · Interfaces · Status

---

Quick Start

Create a project and install the SDK:

uv init --bare demo-connector
cd demo-connector
uv add agent-connector-sdk
uv sync
uv run connector-sync --help

The command prints the supervised synchronization options without opening a source session. Continue with the connector tutorial to build and run a one-file MCP connector, observe its health response, add declarative content, certify the live schema, and join source synchronization.

Overview

Agent Connector SDK is the ecosystem's source-integration boundary. It turns vendor APIs and domain tools into secure MCP connectors, transports bounded source evidence into Epistemic Graph, indexes immutable repository snapshots, and applies authorized changes back to source systems.

Connector packages retain vendor behavior. The SDK owns transport, lifecycle, certification, and effect execution. Generated Epistemic Graph contracts own durable graph records, checkpoints, content identity, and receipts.

Package version: 0.1.0.

Key Capabilities

• Build FastMCP servers with authentication, safe exposure, health, visibility, rate limits, change subscriptions, and consistent tool surfaces.
• Publish skills, prompts, ontologies, SHACL shapes, and connector manifests as typed MCP content.
• Extract bounded source pages and advance checkpoints only from matching durable Epistemic Graph receipts.
• Import deterministic ConnectorPack archives without copying graph DTOs or digest algorithms into connector packages.
• Stream authenticated immutable repository snapshots into the generated IndexRepository boundary without becoming a semantic writer.
• Govern write-back through dry-run, authorization, source-version checks, idempotency, and uncertain-effect reconciliation.
• Certify extension identity, live MCP schemas, pagination, and safety behavior before activation.

Documentation

Start with Build your first connector, then choose the reference that matches the work:

• Documentation home
• Capabilities
• Architecture
• Connector servers
• Source synchronization
• Repository ingestion
• Extension interfaces
• Current status

Sibling authorities: Epistemic Graph owns durable graph state and generated contracts; Graph OS owns authenticated runtime composition.

Architecture

Boundary	Owned here	Owned elsewhere
Connector service	MCP lifecycle, exposure policy, content capture, certification	Vendor models and business semantics stay in the connector package.
Source ingest	Discovery, bounded extraction, transport, receipt verification	Epistemic Graph owns mapping, checkpoints, provenance, and commit receipts.
Repository ingest	Authenticated snapshots, stable manifests, bounded object transport	Epistemic Graph owns indexing, graph projection, and semantic interpretation.
Write-back	Preview, source-version checks, apply, and reconciliation	Epistemic Graph owns change sets, authorization decisions, and durable outcomes.
Runtime composition	Typed ports and verified dependency requirements	Graph OS supplies authenticated identity, clients, and live authority.

The SDK depends directly on epistemic-graph>=2.27.0. Generated SourceIngest, ConnectorPack, IndexRepository, and WriteBack clients and models are the graph boundary; the SDK adds no parallel graph contract.

Contributing

Issues and pull requests are welcome. Follow AGENTS.md for ownership, isolation, and validation rules, and run the affected tests and public-surface gates before submitting a change.

License

Agent Connector SDK is released under the MIT License.