# MCP Catalog

The **MCP Catalog** is Catalyst's organization-wide library of pre-defined MCP server connections. Each entry is a template that fixes the provider, upstream URL, transport, and default authentication shape — you supply a resource name and a credential when you enable it in a project.

Browse from the CLI with `diagrid mcpserver catalog list`, and inspect any entry with `diagrid mcpserver catalog get <entry-name> -o yaml`. To enable an entry or declare a custom MCP server, see [Manage MCP Servers](https://docs.diagrid.io/operate/project-operations/mcp-servers). For the concept, see [Model Context Protocol](https://docs.diagrid.io/concepts/mcp).

## Built-in catalog entries

All entries use the `streamable-http` transport and a 30-second default timeout.

| Entry name | Provider | Upstream URL | Default auth |
|---|---|---|---|
| `atlassian-mcpserver` | Atlassian Rovo (Jira, Confluence) | `https://mcp.atlassian.com/v1/mcp` | `Authorization` header |
| `cloudflare-dev-platform-mcpserver` | Cloudflare Developer Platform (Workers, R2, KV, D1) | `https://bindings.mcp.cloudflare.com/mcp` | SPIFFE JWT in `Cf-Access-Jwt-Assertion` header |
| `datadog-mcpserver` | Datadog (metrics, logs, traces, incidents) | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` | `DD-API-KEY` + `DD-APPLICATION-KEY` headers |
| `github-mcpserver` | GitHub Copilot MCP | `https://api.githubcopilot.com/mcp/` | `Authorization` header |
| `linear-mcpserver` | Linear (issues, projects, workflows) | `https://mcp.linear.app/mcp` | `Authorization` header |
| `notion-mcpserver` | Notion (pages, databases) | `https://mcp.notion.com/mcp` | `Authorization` header |
| `pendo-mcpserver` | Pendo (product analytics) | `https://app.pendo.io/mcp/visitor/shttp` | OAuth 2.0 client credentials |
| `sentry-mcpserver` | Sentry (issues, projects, DSNs) | `https://mcp.sentry.dev/mcp` | `Authorization` header |
| `slack-mcpserver` | Slack (channels, messages) | `https://mcp.slack.com/mcp` | `Authorization` header |
| `snowflake-mcpserver` | Snowflake Cortex Agents | `https://<your-account>.snowflakecomputing.com/api/v2/cortex/mcp` | OAuth 2.0 client credentials |
| `stripe-mcpserver` | Stripe (payments, billing) | `https://mcp.stripe.com` | `Authorization` header |
| `tavily-mcpserver` | Tavily (AI web search) | `https://mcp.tavily.com/mcp` | `Authorization` header |

Two entries include placeholder values you must replace before applying: the Cloudflare entry needs your Access Application audience, and the Snowflake entry needs your account locator and OAuth client secret.

## Authentication shapes

The catalog ships three authentication shapes. Each can also be configured on a custom `MCPServer` resource — see [Authentication](https://docs.diagrid.io/develop/mcp/mcp-authentication).

| Shape | Used by | Configured under |
|---|---|---|
| Static header API key | `atlassian`, `datadog`, `github`, `linear`, `notion`, `sentry`, `slack`, `stripe`, `tavily` | `spec.endpoint.streamableHTTP.headers[]` |
| OAuth 2.0 client credentials | `pendo`, `snowflake` | `spec.endpoint.streamableHTTP.auth.oauth2` |
| SPIFFE JWT-SVID | `cloudflare-dev-platform` | `spec.endpoint.streamableHTTP.auth.spiffe.jwt` |

## See also

- [Manage MCP Servers](https://docs.diagrid.io/operate/project-operations/mcp-servers) — enable a catalog entry or declare a custom MCP server.
- [Model Context Protocol](https://docs.diagrid.io/concepts/mcp) — what MCP is and how it runs on Catalyst.
- [Develop with MCP](https://docs.diagrid.io/develop/mcp) — connect clients, add servers, and control access.