Scion SDK

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

Documentation · Capabilities · Interfaces · Status

Quick Start

Install Scion SDK as scion-sdk and import it as scion_sdk. The repository, package, CLI, and API identifiers all use the scion-sdk name.

Create a project and install the SDK:

uv init --bare demo-connector
cd demo-connector
uv add scion-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

Scion SDK is the ecosystem's source-integration boundary. It turns vendor APIs and domain tools into secure MCP connectors, transports bounded source evidence into Medulla, 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. Medulla owns durable graph records, checkpoints, content identity, and receipts.

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 Medulla receipts.
• Import deterministic ConnectorPack archives without copying graph types or digest algorithms into connector packages.
• Stream authenticated immutable repository snapshots into the 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 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: Medulla owns durable graph state; Arbora is the one door for admission, auth, served operations, and MCP and A2A serving.

Architecture

Explore the live architecture

The SDK depends directly on medulla. The Rust serde types in Medulla are the source of truth. The SDK holds hand-written SourceIngest, ConnectorPack, IndexRepository, and WriteBack clients, tested on round-trip vectors. The SDK adds no parallel graph contract. Spec IDs use the SCION- prefix.

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

Scion SDK is released under the MIT License.