Integrations

Syndicate Code integrates with external tool servers via MCP, provides an LSP server for editor integration, and exposes a GraphQL API for programmatic control-plane access.

MCP

MCP (Model Context Protocol) integration allows Syndicate Code to connect to external tool servers. Because MCP servers operate outside the Syndicate Code process boundary, every MCP tool invocation must pass through the full governed execution lifecycle — canonicalization, policy evaluation, approval, permit issuance, and boundary validation — before any call is transmitted.

MCP servers are untrusted by default. Trust is earned through evidence accumulation over time.

syndicate mcp add filesystem \
  --url http://localhost:5050 \
  --transport sse \
  --trust-tier 0 \
  --capability-declaration ./mcp/filesystem.yaml

LSP

The LSP integration provides real-time governance state in editors — checkpoint notifications, permit status, and evidence stream events surfaced as editor diagnostics or status bar items.

GraphQL API

The GraphQL API exposes the control plane for programmatic access: session management, audit queries, approval operations, policy introspection, and trust state management.

In this section

• MCP — registering servers, capability declarations, trust model, governed invocation path
• LSP — editor integration, diagnostics, status bar
• GraphQL API — schema, authentication, session and audit operations