AgentToolDrop

66 of 71

Sentry MCP Server

Gives coding agents access to Sentry errors, issues, traces and performance data over MCP

Add to Claude Code

claude mcp add --transport http sentry https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}

Copied from the project's docs at mcp.sentry.dev

Why you'd want it

Sentry runs a remote MCP server at mcp.sentry.dev that uses OAuth and acts as middleware to the Sentry API, with tools chosen for debugging workflows in coding assistants rather than full Sentry coverage. You can scope the connection to one organization or project, which sets defaults and hides discovery tools. For self-hosted Sentry there is a stdio transport (npx @sentry/mcp-server) that takes a user auth token; its AI-powered search tools need an OpenAI, Azure OpenAI, Anthropic or OpenRouter key.

Best for

  • Teams already on Sentry
  • Debugging production errors from the editor
  • Self-hosted Sentry via the stdio transport

Use it when

Your app reports to Sentry and you want the coding agent to pull issue details, errors and traces while it works on a fix.

Skip it if

You do not use Sentry. Sentry says it is not a general-purpose server for all Sentry functionality, and the stdio transport is still a work in progress.

Editor's note

The Sentry MCP server now lives in getsentry/toolkit alongside the Sentry CLI.

Same category or shared tags, by drop score.

  1. Rank 56

    Lets agents call the Stripe API and search Stripe docs through a hosted MCP server or framework toolkits

    • score 44
    • 1.9k stars
    • pushed
    • MIT

    Add to Claude Code

    claude mcp add --transport http stripe https://mcp.stripe.com/
    Use it when, skip it if, stats for Stripe MCP and Agent Toolkit

    Why you'd want it

    Stripe hosts an MCP server at mcp.stripe.com with OAuth; its tools search, inspect, read and write Stripe API methods and search the Stripe docs, which makes much of the API reachable without loading every endpoint into context. Stripe requires human confirmation before some write actions, such as refunds and outbound payments. The stripe/ai repo also holds the Agent Toolkit for Python and TypeScript (OpenAI Agents SDK, LangChain, CrewAI, Vercel AI SDK), a local MCP package, billing integrations for the Vercel AI SDK and native OpenAI, Anthropic and Gemini SDKs, and Stripe agent skills and plugins.

    Best for

    • Products built on Stripe
    • Agent frameworks that need Stripe tools via function calling
    • Looking up Stripe docs while integrating

    Use it when

    You build on Stripe and want a coding agent or your own agent to query and change Stripe objects, or to answer integration questions from the Stripe docs.

    Skip it if

    You do not use Stripe. Write tools act on a real Stripe account, so Stripe advises turning on tool approval in your client and using restricted API keys to limit what the toolkit can do.

    Stats

    Stars
    1,941
    Last push
    Release
    none tagged
    License
    MIT
    Pricing
    Open source
    Works with
    Any MCP client, Claude Code, Cursor, Codex, VS Code, Claude Desktop
    Drop score
    44 of 100
  2. Rank 39

    Lets an AI assistant work with Supabase projects: tables, migrations, SQL, logs and Edge Functions

    • score 57
    • 3k stars
    • pushed
    • mcp-server-supabase-v0.14.0 on
    • Apache-2.0

    Add the hosted server to your MCP config

    {
      "mcpServers": {
        "supabase": {
          "type": "http",
          "url": "https://mcp.supabase.com/mcp"
        }
      }
    }
    Use it when, skip it if, stats for Supabase MCP Server

    Why you'd want it

    Supabase hosts the server at mcp.supabase.com, so most clients need only the URL and an OAuth login to reach your projects. Tools are grouped into features (database, debugging, development, Edge Functions, account, docs, branching, storage) that you can restrict, and you can scope the server to one project or run it in read-only mode, where SQL runs as a read-only Postgres user. The npm package also exports tool schemas for the Vercel AI SDK MCP client and a handler for serving the tools from your own endpoint.

    Best for

    • Apps built on Supabase
    • Letting a coding agent inspect schemas and apply migrations
    • Debugging with project logs and advisors

    Use it when

    Your app runs on Supabase and you want the agent to read schemas, run SQL, apply migrations or check logs from your editor.

    Skip it if

    You do not use Supabase, or you cannot keep it away from production data: Supabase warns about prompt injection, recommends project scoping and read-only mode, and says not to give the server to your end users. The local CLI and self-hosted setups get only a subset of tools and no OAuth.

    Stats

    Stars
    2,952
    Last push
    Release
    mcp-server-supabase-v0.14.0,
    License
    Apache-2.0
    Pricing
    Open source
    Works with
    Any MCP client, Claude Code, Cursor
    Drop score
    57 of 100
  3. Rank 22

    Lets a coding agent control and inspect a live Chrome browser through DevTools

    • score 63
    • 53.6k stars
    • pushed
    • chrome-devtools-mcp-v1.10.1 on
    • Apache-2.0

    Add to your MCP client config

    {
      "mcpServers": {
        "chrome-devtools": {
          "command": "npx",
          "args": [
            "-y",
            "chrome-devtools-mcp@latest"
          ]
        }
      }
    }
    Use it when, skip it if, stats for Chrome DevTools MCP

    Why you'd want it

    It gives an agent the parts of Chrome DevTools a developer reaches for: recording performance traces with extracted insights, inspecting network requests, reading console messages with source-mapped stack traces and taking screenshots. Automation runs on Puppeteer and waits for action results automatically. A --slim mode trims the tool set for basic browser tasks, and a separate CLI works without MCP.

    Best for

    • Debugging front-end bugs with an agent
    • Performance analysis of web pages
    • Checking console and network errors after a code change

    Use it when

    You want your coding agent to check its changes in a real Chrome instance, reading console, network and performance data the way you would in DevTools.

    Skip it if

    You need Firefox or WebKit; only Chrome and Chrome for Testing are officially supported. Usage statistics go to Google by default (opt out with --no-usage-statistics), and performance tools may send trace URLs to the CrUX API unless you pass --no-performance-crux.

    Stats

    Stars
    53,551
    Last push
    Release
    chrome-devtools-mcp-v1.10.1,
    License
    Apache-2.0
    Pricing
    Open source
    Works with
    Any MCP client, Claude Code, Codex, Cursor, Gemini CLI, VS Code, JetBrains, Windsurf
    Drop score
    63 of 100

For agents

The same entry, as files an agent can read without scraping this page.

# read one entry
curl -s https://agenttooldrop.com/tools/sentry-mcp.md

# list the MCP servers in the catalog
curl -s https://agenttooldrop.com/tools.json \
  | jq -r '.tools[] | select(.category=="mcp-server") | .slug'