The MCP (Model Context Protocol) server exposes your event schema as a semantic layer for IDEs and AI agents.
Configuration
Add the following to your IDE's MCP config (e.g. .cursor/mcp.json):
The exact config — with your key filled in — is available in the app under Integrations → MCP Server, or run npx suky init to write it for you.
Available tools
| Tool | Description |
|---|---|
| list_events | List all events in the event schema with optional filters. |
| get_event | Get the full property schema for a specific event. |
| search_events | Semantic search across event names and descriptions. |
| validate_tracking | Check a proposed tracking change against the contract before it ships. |
| get_sdk_snippet | Generate a tracking-call snippet for an event and your CDP SDK. |
| check_event_health | Report warehouse health for an event — freshness, volume, violations. |
| propose_contract | Draft a contract for a new or changed event for review. |
These are a subset — the server exposes read tools plus agent tools that can propose contracts, resolve violations, and open fix PRs. The MCP server is a Pro feature.