Canyon
Book a Demo
Canyon/Docs/MCP integration
AI engine

MCP integration

Canyon speaks MCP natively. Every Canyon-native capability — design system, data sources, metrics, repos — is exposed as MCP tools. Your own MCP servers plug into the same layer, so agents can reach your systems without bespoke integration work.

BetaUpdated April 2026•Reference•Canyon v1.0
BetaThese docs are in beta
Expect gaps and drift from the live product. Something unclear or missing? Grab 30 minutes with the team and we will walk you through it.
Talk to support

Canyon-native tools

Canyon ships with a rich set of built-in MCP tools the platform uses internally, and that are available to any MCP-speaking agent (Claude Code, Cursor, Lovable, your own). Every built-in tool is deterministic and idempotent — agents can retry freely without side effects.

Design system
list_themes()Available themes with metadata
get_theme(id)Full token set (primitives, semantic, components)
get_design_tokens(theme_id)Compiled tokens, ready to consume
Components & patterns
list_components()Browse the component library
get_component(name)Self-contained bundle: source, dependencies, usage
search_components(query)Semantic search across components
get_pattern(type)Full pattern implementation ready to drop in
validate_design(code, theme)Design-compliance check
Data & metrics
get_metric_catalog()Discover metrics available to this caller
query_metrics(...)Governed query, typed results, row-level filtered
describe_source(name)Schema, freshness, lineage
Project & code
list_projects()Projects the caller can see
read_file(path)Read a source file from a project
propose_change(...)Queue a code change for review or automatic build

Aggregator & tool router

Every MCP server — Canyon-native or yours — is stitched together behind a single router. The aggregator namespaces every tool (design.get_theme, metrics.query, repo.propose_change), monitors the health of each upstream, and filters which tools are exposed to which project based on its RBAC scope.

┌─────────────────────────────────────────────────────────────────────────────────────────┐
│  CANYON MCP AGGREGATOR                                                                  │
│  ════════════════════════════════════════════════════════════════════════════════════════│
│                                                                                         │
│    ┌───────────────────┐  ┌───────────────────┐  ┌───────────────────┐                  │
│    │  Design system    │  │   Data sources    │  │    Metrics        │                  │
│    │  (Canyon-native)  │  │  (your warehouse) │  │  (semantic layer) │                  │
│    └─────────┬─────────┘  └─────────┬─────────┘  └─────────┬─────────┘                  │
│              │                      │                      │                            │
│              └──────────────────────┼──────────────────────┘                            │
│                                     ▼                                                   │
│                        ┌────────────────────────┐                                       │
│                        │   Tool Router          │                                       │
│                        │   • Namespace tools    │                                       │
│                        │   • Per-project scope  │                                       │
│                        │   • Health + audit     │                                       │
│                        └────────────────────────┘                                       │
│                                     │                                                   │
│    ┌────────────────────────────────┼────────────────────────────────┐                  │
│    ▼                                ▼                                ▼                  │
│  ┌───────────────────┐  ┌───────────────────┐  ┌───────────────────┐                    │
│  │  Source control   │  │  Notifications    │  │  Your MCP server  │                    │
│  │  (repo ops)       │  │  (Slack, Teams…)  │  │  (custom tools)   │                    │
│  └───────────────────┘  └───────────────────┘  └───────────────────┘                    │
│                                                                                         │
│  TRANSPORTS: stdio · SSE · HTTP                                                         │
└─────────────────────────────────────────────────────────────────────────────────────────┘
stdioSSEHTTPPer-project scope

What plugs in today

These are examples of what customers have already wired up. Canyon doesn’t care where the MCP server runs — cloud, on-prem, or inside your own VPC — as long as it speaks the protocol.

SnowflakeLive
DatabricksLive
BigQueryLive
PostgreSQLLive
SQL ServerLive
MongoDBLive
GitHub / GitLabLive
SlackLive
Microsoft TeamsLive
Linear / JiraLive
Notion / ConfluenceLive
OpenMetadata / Unity CatalogAlpha
SAP S/4HANAAlpha
Dynamics 365Alpha
ServiceNowAlpha
Any MCP-compliant serverYour own
Don’t see your system?
Anything with a documented API can be made MCP-native in a day or two. Bring us the system; we’ll bring the adapter.

Adding your own server

Canyon’s extension model is deliberately boring: you add an MCP server configuration to your organization, the aggregator discovers it, namespaces its tools, and exposes them to the projects you authorize. Secrets are encrypted at rest; health checks run in the background.

{
  "name": "Warehouse metrics",
  "type": "stdio" | "sse" | "http",
  "config": {
    "command": "…",
    "args": ["…"],
    "env": { "DATABASE_URL": "…" }   // Encrypted at rest
  },
  "health_status": "healthy" | "unhealthy" | "unknown",
  "last_checked_at": "timestamp"
}
The seam is stable
Because MCP is an open protocol, tools you build for Canyon are instantly usable by any other MCP-speaking agent (Claude Code, Cursor, Lovable, your own). Your investment in tool surfaces is never wasted on a proprietary plugin format.