Ask your app anything — revenue, errors, read-cost, growth — and get rendered charts back.
Ask your app anything — revenue, errors, read-cost, growth — and get rendered charts back. The prism — crossdeck mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 13 defined tools rather than through you.
Most MCP servers are a connector to one system. Prism is an intelligence layer over your whole app — because Crossdeck already joins the layers about your users (identity · revenue · entitlements · errors · analytics · database read-cost) into one source of truth, by identity.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
list_projects — list every app this connector can read (your portfolio)get_portfolio — the coverage map: for each app, which surfaces are instrumented vs a blind spot. Load it first so a later blank reads as a known blind spot, not ause_project — set the current app for subsequent tools ("switch to ")get_revenue — MRR, paying-customer count, per-rail split (Stripe/Apple/Google), optional daily trendget_customers — the customer census: the paying-customer count (plus total / active where instrumented). The canonical "how many customers does this app have" answerget_read_cost — database read-cost split into per-user reads vs un-attributed overhead, by operationget_error_impact — for one error: how many distinct users hit it, and how many are paying (counts)get_error_affected_users — the named paying users an error hit, each with monthly revenue and last-hit, sorted by revenue at risk. *Returns your own identifiers only —get_customer — one customer across every layer Crossdeck joins by identity: what they pay × active entitlements × read-costget_host_analytics — page views + unique visitors for a host/subdomain you own (optional daily series)get_host_top_pages — top pages or referrers for a host you owndraw_user_growth — an interactive line chart of visitors + page views over timeYou will need one environment variable: CROSSDECK_SECRET_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Prism — Crossdeck's toolset — list_projects, get_portfolio, use_project and 10 more — is a fair guide to whether it matches your workflow. It is maintained by com.cross-deck; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_projects | list every app this connector can read (your portfolio). |
| get_portfolio | the coverage map: for each app, which surfaces are instrumented vs a blind spot. Load it first so a later blank reads as a known blind spot, not a fact. |
| use_project | set the current app for subsequent tools ("switch to <app>"). |
| get_revenue | MRR, paying-customer count, per-rail split (Stripe/Apple/Google), optional daily trend. |
| get_customers | the customer census: the paying-customer count (plus total / active where instrumented). The canonical "how many customers does this app have" answer. |
| get_read_cost | database read-cost split into per-user reads vs un-attributed overhead, by operation. |
| get_error_impact | for one error: how many distinct users hit it, and how many are paying (counts). |
| get_error_affected_users | the **named paying users** an error hit, each with monthly revenue and last-hit, sorted by revenue at risk. *Returns your own identifiers only — never emails/names you didn't provide.* |
| get_customer | one customer across every layer Crossdeck joins by identity: what they pay × active entitlements × read-cost. |
| get_host_analytics | page views + unique visitors for a host/subdomain you own (optional daily series). |
| get_host_top_pages | top pages or referrers for a host you own. |
| draw_user_growth | an interactive line chart of visitors + page views over time. |
| open_moat_dashboard | a customer's cross-layer dashboard (pay × entitlements × read-cost) rendered as cards. |
{
"mcpServers": {
"prism": {
"command": "npx",
"args": ["-y", "ENOENT"],
"env": {
"CROSSDECK_SECRET_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CROSSDECK_SECRET_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.