Skip to content
Agent Month
Email

MCP integrations

Connect AI agents to your internal tools

The Model Context Protocol (MCP) lets Claude Code, Cursor, and other agents work against your real systems — safely, with auth and audit. Pick a tool to see how to wire it up, and what a production setup needs.

Observability

Datadog

→

Metrics, traces, logs, and monitors for your production systems.

Sentry

→

Error tracking and performance monitoring for applications.

Grafana

→

Dashboards and alerting over your metrics and logs.

PagerDuty

→

On-call scheduling and incident response.

Project management

Linear

→

Issue tracking and project planning for engineering teams.

Jira

→

Issue and project tracking across large organizations.

Code & VCS

GitHub

→

Source code, pull requests, issues, and Actions.

GitLab

→

Source code, merge requests, issues, and CI/CD pipelines.

Databases

PostgreSQL

→

Your relational application or analytics database.

MySQL

→

Your relational application database.

MongoDB

→

Your document database.

Data & warehouse

Snowflake

→

Your cloud data warehouse.

BigQuery

→

Google Cloud’s serverless data warehouse.

Elasticsearch

→

Your search and log analytics cluster.

Infra & cloud

AWS

→

Your cloud infrastructure — compute, storage, networking, and more.

Kubernetes

→

Your container orchestration platform.

Vercel

→

Your frontend deployment platform.

Comms & docs

Slack

→

Your team’s messaging and notifications.

Notion

→

Your team’s docs, specs, and knowledge base.

Confluence

→

Your organization’s wiki and documentation.

Figma

→

Your design files and components.

Payments & business

Stripe

→

Your payments, subscriptions, and billing data.

Salesforce

→

Your CRM — accounts, opportunities, and contacts.

AI coding clients

Claude Code

→

Anthropic’s terminal-native coding agent. Discovers MCP servers from your project or user config, calls their tools in the middle of a task, and (for headless use) can be driven from CI.

Cursor

→

AI-native code editor (VS Code fork). Adds MCP support in its settings so any MCP server’s tools show up alongside Cursor’s own agent and inline-edit flows.

How to connect any MCP server

The wiring is the same for every tool on this page — only the server and its credentials change. Each tool page covers those specifics; here’s the shared flow.

Claude Code

  1. Pick or build the MCP server for your tool (see the tool’s page for whether an official or community server exists).
  2. Register it with claude mcp add <name> <command> [--env KEY=VALUE]. Project config lives in .mcp.json (commit it to standardize the team); user config in ~/.claude/mcp.json.
  3. Provide credentials out of band — from the environment or a secret store, never hardcoded in the repo.
  4. Restart Claude Code (or run /mcp) so it discovers the server’s tools, then confirm the expected tools appear.
  5. Run a read-only task first to validate scope before granting any write access.

Cursor

  1. Open Cursor → Settings → MCP and add the server (command or URL + transport).
  2. Commit .cursor/mcp.json so every engineer gets the same tools.
  3. Supply credentials via env or Cursor’s secret storage — not the committed file.
  4. Reload Cursor and verify the tools appear; pair with a .cursorrules file so agents use them inside your golden path.

If tools don’t appear, it’s almost always auth or transport — see MCP server not connecting, and note hosted servers often need OAuth rather than a plain API key.

The MCP security checklist

A working connection is the easy part. This is what separates a safe, team-wide integration from a liability — it applies to every tool on this page.

  • Scope every credential to the minimum access the task needs — never a full-access token.
  • Default to read-only; add write actions one at a time, deliberately.
  • Log every tool call with who, what, and when, queryable from your observability stack.
  • Keep credentials out of the repo and the agent’s sandbox — inject them at the boundary from a secret store.
  • Gate high-impact or irreversible actions (writes, deploys, money movement) behind explicit human approval.
  • Run a read-only smoke test to validate scope before granting any write access.