×The contract registry your coding agents query before they write tracking code.
Connect Cursor, Claude Code, Windsurf, or any MCP-compatible agent to your event contracts. Implementing agents look up canonical events instead of inventing new ones; reviewing agents validate changes deterministically — before anything merges.
Capabilities
What you get with the MCP Server integration
Search the registry, reuse the canonical event
search_events, get_event, search_contracts, and get_contract give agents the real event names, property schemas, and quality rules — so they reuse checkout_completed instead of inventing checkoutCompleted.
Deterministic pre-commit validation
validate_tracking classifies a proposed change as breaking, additive, or cosmetic against active contracts — the same check that gates your PRs in CI, available to the agent before it commits.
Propose contracts, humans approve
For genuinely new events, propose_contract files a draft for human review — agents extend the plan without writing into it. check_event_health and explain_violation give reviewing agents warehouse reality and root-cause context.
Install kit included
The MCP settings page generates your MCP config (.mcp.json / .cursor/mcp.json) and an AGENTS.md section that tells every agent opening your repo to query suky before touching tracking code.
Setup
How to connect MCP Server
Go to Settings → Integrations → MCP Server in suky.
Generate an API key for your workspace.
Copy the install kit: the MCP config into .mcp.json (or .cursor/mcp.json) and the AGENTS.md section into your repo instructions.
Your agents now search contracts, validate tracking changes, and propose drafts — before code merges.
Ready to connect MCP Server?
Invite-only while we onboard the Founding 25 — request an invite and I'll set you up.