Context Protocol

Model Context Protocol support

Understand how Source Parts extends the Model Context Protocol to deliver real-time component intelligence to any assistant.

Namespaces and tool discovery

Tools ship under the `inventory`, `pricing`, `automation`, and `governance` namespaces. Assistants can fetch the manifest at runtime by calling `/mcp/manifest`.

Start the MCP server locally

# Run the Source Parts MCP server locally
npx @sourceparts/mcp serve --api-key $SOURCEPARTS_API_KEY

Schema extensions

Source Parts augments standard MCP responses with `traceId`, `latencyMs`, and `ratelimit` metadata. These fields remain optional for strict MCP-compliant clients.

Trace IDs map one-to-one with backend requests in the Source Parts observability pipeline.
Rate limit metadata includes the window size and remaining calls, enabling assistants to degrade gracefully.