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.3.9.
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
IndexRepositoryboundary 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 the operator's first connector, then choose the reference that matches the work:
- Documentation home
- Capabilities
- Architecture
- Connector servers
- Schema disclosure
- Source synchronization
- Repository ingestion
- Extension interfaces
- Current status
Sibling authorities: Epistemic Graph owns durable graph state and generated contracts; Arbora 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 checked dependency requirements | Arbora 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.
1 maintainer
Metadata
1 maintainer
Release files for agent-connector-sdk 0.3.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agent_connector_sdk-0.3.9.tar.gz | 741.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_connector_sdk-0.3.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / agent_connector_sdk-0.3.9.tar.gz
| Download URL | agent_connector_sdk-0.3.9.tar.gz |
|---|---|
| Size | 741.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ecf26876e6bd5209751b43e7257695edaa0d27b21e58f723144cc7a93a68b71
|
|
BLAKE2b-256 checksum How to use checksums |
fcd1a132f17265bebda5acda56eccceb0b6c60e08e710e60e1f57fdc03ddc3c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / agent_connector_sdk-0.3.9-py3-none-any.whl
| Download URL | agent_connector_sdk-0.3.9-py3-none-any.whl |
|---|---|
| Size | 740.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17ab75e2cf171f68ab70b5f385b6676c576f5833dd5ce7152662d07816679ecb
|
|
BLAKE2b-256 checksum How to use checksums |
4dd0d2b1b21c89675207b5a442d529293bb5f01e135c403a8f92065f71044127
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for agent-connector-sdk 0.3.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
