Skip to main content

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. For the concept, see Model Context Protocol.

Built-in catalog entries​

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

Entry nameProviderUpstream URLDefault auth
atlassian-mcpserverAtlassian Rovo (Jira, Confluence)https://mcp.atlassian.com/v1/mcpAuthorization header
cloudflare-dev-platform-mcpserverCloudflare Developer Platform (Workers, R2, KV, D1)https://bindings.mcp.cloudflare.com/mcpSPIFFE JWT in Cf-Access-Jwt-Assertion header
datadog-mcpserverDatadog (metrics, logs, traces, incidents)https://mcp.datadoghq.com/api/unstable/mcp-server/mcpDD-API-KEY + DD-APPLICATION-KEY headers
github-mcpserverGitHub Copilot MCPhttps://api.githubcopilot.com/mcp/Authorization header
linear-mcpserverLinear (issues, projects, workflows)https://mcp.linear.app/mcpAuthorization header
notion-mcpserverNotion (pages, databases)https://mcp.notion.com/mcpAuthorization header
pendo-mcpserverPendo (product analytics)https://app.pendo.io/mcp/visitor/shttpOAuth 2.0 client credentials
sentry-mcpserverSentry (issues, projects, DSNs)https://mcp.sentry.dev/mcpAuthorization header
slack-mcpserverSlack (channels, messages)https://mcp.slack.com/mcpAuthorization header
snowflake-mcpserverSnowflake Cortex Agentshttps://<your-account>.snowflakecomputing.com/api/v2/cortex/mcpOAuth 2.0 client credentials
stripe-mcpserverStripe (payments, billing)https://mcp.stripe.comAuthorization header
tavily-mcpserverTavily (AI web search)https://mcp.tavily.com/mcpAuthorization 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.

ShapeUsed byConfigured under
Static header API keyatlassian, datadog, github, linear, notion, sentry, slack, stripe, tavilyspec.endpoint.streamableHTTP.headers[]
OAuth 2.0 client credentialspendo, snowflakespec.endpoint.streamableHTTP.auth.oauth2
SPIFFE JWT-SVIDcloudflare-dev-platformspec.endpoint.streamableHTTP.auth.spiffe.jwt

See also​