Set up AppSignal MCP - AppSignal Documentation

AppSignal MCP is a public HTTP endpoint at https://appsignal.com/api/mcp. Authenticate once, then add the endpoint to your AI tool using the instructions for your editor or app.

Authentication

You need an AppSignal account to get started. AppSignal MCP supports two authentication methods — pick whichever fits the AI agent you’re configuring:

OAuth — sign in with your AppSignal account once. Access is granted at the application level and exposes all read and write tools at once. The simplest setup for every agent in this guide: each one connects to the endpoint directly.
Bearer token — generate a long-lived MCP token with fine-grained permissions per toolset. Each token can be set to read, write, or disabled per area, scoped to specific applications, and configured to automatically expose new tools as they ship. Best when you want to limit what an agent can do.

If you’re getting started and your agent supports OAuth, that’s the quicker path. If you need per-tool permissions or per-app scoping, generate an MCP token instead. To generate a Bearer token:

Select your profile icon.
Go to Account Settings.
Select MCP Tokens to create a new token.

The token form has two long checklists: the applications to scope the token to, and the permissions to expose. Each list has a Select all toggle in its header that checks or clears every box at once.

Configuration

Configure AppSignal MCP in your AI agent’s settings using the HTTP endpoint https://appsignal.com/api/mcp. Each of the following sections has tabs for OAuth and Bearer token — pick whichever you set up in the Authentication section.

If the OAuth tab errors out for your editor, fall back to the Bearer token tab and let us know in our Discord community so we can tighten these instructions.

Claude Code

claude mcp add --transport http appsignal https://appsignal.com/api/mcp

claude mcp add --transport http appsignal https://appsignal.com/api/mcp \
  --header "Authorization: Bearer <YOUR_MCP_TOKEN>"

With OAuth, Claude Code starts the browser-based sign-in flow the first time AppSignal tools are invoked. See the Claude Code MCP docs for transport flags and CLI reference.

Claude app

The Claude app — Claude.ai on the web, and the desktop and mobile apps — connects to AppSignal MCP as a custom connector over OAuth. There’s no Bearer token option in the app.

In Claude, open Settings, then Connectors.
Select Browse, search for appsignal, and open the AppSignal connector. If it isn’t listed, select Add custom connector and enter the URL https://appsignal.com/api/mcp instead.
Select Connect, then complete the AppSignal sign-in when prompted.
Start a chat and try a prompt such as “List my AppSignal applications”. You can connect or disconnect AppSignal at any time from Settings → Connectors.

Custom connectors are available on the Free, Pro, Max, Team, and Enterprise plans; Free is limited to one custom connector. On Team and Enterprise, an organization admin manages the available connectors. See the Claude custom connector guide for details.

Cursor

Add AppSignal from Cursor’s settings, or by editing mcp.json directly. To add it from the settings UI:

Go to your Cursor settings.
Open the Customize tab, select MCPs, then select + Add New MCP Server.
Select User, enter the values below in the JSON file that opens, and save your configuration.

Selecting User writes to ~/.cursor/mcp.json and makes AppSignal available everywhere. The dropdown also lists your open workspaces under Workspaces, and picking one writes .cursor/mcp.json in that workspace instead, which you can commit so your team picks it up.

{
  "mcpServers": {
    "appsignal": {
      "url": "https://appsignal.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "appsignal": {
      "url": "https://appsignal.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_TOKEN>"
      }
    }
  }
}

Cursor connects to the endpoint over streamable HTTP in both cases. The difference is how you authorize:

OAuth: leave the headers out. Cursor opens a browser tab where you grant access and choose the authorization scopes, then finishes the connection.
Bearer token: include the Authorization header. Cursor authorizes with the scopes you configured on the token and connects without opening a tab.

Either way, appsignal appears under Connected in the MCPs list with a green indicator and a tool count once it is working. See the Cursor MCP docs for the full schema.

Devin

Devin, formerly Windsurf, connects to AppSignal from its Cascade MCP marketplace. You can directly edit its ~/.codeium/windsurf/mcp_config.json file or from the UI with the following steps:

Run Devin: Cascade MCP Registry from the command palette to open the Cascade MCP marketplace.
Select Add custom MCP.
Enter the values below in the mcp_config.json that opens, then save.
Select the refresh control next to the server to reload it.

AppSignal then appears under Installed as Enabled, with the number of tools it exposes.

JSON Bearer token

{
  "mcpServers": {
    "appsignal": {
      "serverUrl": "https://appsignal.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_TOKEN>"
      }
    }
  }
}

Devin treats a serverUrl entry as a streamable HTTP server. The entry above authorizes with an MCP token. To use OAuth instead, leave the headers out and Devin opens the browser sign-in when it connects. See the Devin MCP docs for more configuration options.

Zed

Add AppSignal from Zed’s settings, or by editing the settings file directly. To add it from the settings UI:

Open Settings → AI → General → MCP servers → Configure, or run agent: open settings from the command palette (Cmd+Shift+P) and select MCP servers.
Select Add server, then Add remote server.
Enter appsignal as the name and https://appsignal.com/api/mcp as the URL.
If you’re using a token rather than OAuth, add an Authorization header.

To edit the file instead, open the command palette, run zed: open settings file, and add a context_servers section:

{
  "context_servers": {
    "appsignal": {
      "url": "https://appsignal.com/api/mcp"
    }
  }
}

{
  "context_servers": {
    "appsignal": {
      "url": "https://appsignal.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_TOKEN>"
      }
    }
  }
}

When the Authorization header is omitted, Zed initiates the standard MCP OAuth flow against AppSignal and caches the session in your keychain, so you only sign in once. Zed applies settings changes without a restart. See the Zed MCP docs for the full context_servers schema.

VS Code

If you use GitHub Copilot under a company account, make sure MCP servers in Copilot is set to Enabled in your organization settings (Settings → Copilot → Policies → Features → MCP servers in Copilot). Add AppSignal from VS Code’s settings, or by editing mcp.json directly. A workspace .vscode/mcp.json applies to one project. To use AppSignal across every project, put the same servers block in your user-level configuration instead, which you can open with MCP: Open User Configuration from the command palette (Cmd+Shift+P). To add it from the settings UI:

Open Chat → Settings → MCP Servers.
Select + to add a server.
Choose HTTP (HTTP or Server-Sent Events) as the type.
Enter https://appsignal.com/api/mcp as the URL and appsignal as the name.
Choose whether to save it for your user or the workspace.

VS Code writes the server into mcp.json and lists it under User or Workspace in the MCP Servers view. Open that mcp.json to see the entry, where VS Code shows its running state and tool count above the server name. To edit the file directly instead, use these values:

{
  "servers": {
    "appsignal": {
      "url": "https://appsignal.com/api/mcp",
      "type": "http"
    }
  }
}

{
  "inputs": [
    {
      "type": "promptString",
      "id": "appsignal_mcp_token",
      "description": "AppSignal MCP token",
      "password": true
    }
  ],
  "servers": {
    "appsignal": {
      "type": "http",
      "url": "https://appsignal.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:appsignal_mcp_token}"
      }
    }
  }
}

With OAuth, VS Code initiates the sign-in flow the first time AppSignal tools are used. VS Code starts MCP servers on demand rather than at startup, so AppSignal stays idle until you open Copilot Chat and use it. See the VS Code MCP docs for input variables and headers.

GitHub Copilot CLI

The GitHub Copilot CLI uses OAuth for MCP authentication. Run the following to add AppSignal:

Bash

copilot mcp add appsignal https://appsignal.com/api/mcp

Follow the OAuth prompt to authorize AppSignal. Once connected, AppSignal tools will be available in Copilot CLI sessions. The server is written to ~/.copilot/mcp-config.json; a workspace-level .mcp.json works too. Run copilot mcp list to confirm AppSignal is registered with type http. See the GitHub Copilot CLI MCP docs for the interactive /mcp add flow.

Gemini CLI

Gemini CLI reads MCP servers from ~/.gemini/settings.json (user-level) or .gemini/settings.json in a project. Add AppSignal under mcpServers:

{
  "mcpServers": {
    "appsignal": {
      "httpUrl": "https://appsignal.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "appsignal": {
      "httpUrl": "https://appsignal.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_TOKEN>"
      }
    }
  }
}

Leave headers out to use OAuth: when the endpoint returns 401, Gemini CLI discovers the flow and opens the browser sign-in. You can also add the server from the command line. Pass --transport http, because gemini mcp add defaults to the stdio transport and would otherwise store the URL as a command to run:

Bash

gemini mcp add --transport http appsignal https://appsignal.com/api/mcp

To use a token rather than OAuth, pass it as a header:

Bash

gemini mcp add --transport http appsignal https://appsignal.com/api/mcp \
  --header "Authorization: Bearer <YOUR_MCP_TOKEN>"

Restart your Gemini CLI session after adding the server, then run /mcp list to confirm it connected. See the Gemini CLI MCP docs for the full mcpServers schema and gemini mcp commands.

OpenAI Codex

Codex connects to AppSignal MCP as a streamable HTTP server. It shares one configuration across the CLI, the IDE extension, and the ChatGPT desktop app, so you only set this up once. To use OAuth, add the server with --url:

Bash

codex mcp add appsignal --url https://appsignal.com/api/mcp

Codex opens the AppSignal authorization page as part of adding the server, so there’s no separate sign-in step. On that screen, choose your organization and, optionally, the applications to expose, leaving them unchecked for all. Run codex mcp login appsignal if you need to authenticate again later. To use a token instead, edit ~/.codex/config.toml (or .codex/config.toml in a project). Set bearer_token_env_var to the name of an environment variable that holds an MCP token:

[mcp_servers.appsignal]
url = "https://appsignal.com/api/mcp"
bearer_token_env_var = "APPSIGNAL_MCP_TOKEN"

Then set APPSIGNAL_MCP_TOKEN in your environment. See the Codex MCP docs for http_headers, OAuth, and the full mcp_servers schema.

Verify the connection

After adding the server, confirm your agent can reach it before you rely on it.

Claude Code: run claude mcp list, where AppSignal should show as ✔ Connected. Run /mcp inside a session to inspect the server and its tools.
Codex: run codex mcp list. The Auth column shows OAuth or Bearer token for a server that is set up correctly. Inside a session, /mcp lists the connected servers and their tools.
GitHub Copilot CLI: run copilot mcp list, where AppSignal should be listed with type http.
Gemini CLI: run /mcp list inside a session. If AppSignal is missing from a correct config, check that you have trusted the folder.
Zed: open Settings → AI → MCP servers. The indicator next to appsignal turns green and its tooltip reads “Server is active”.
VS Code: open Copilot Chat and select the tools icon. VS Code starts MCP servers on demand, so AppSignal stays idle until something uses it.
Cursor: open the MCPs list in settings, where appsignal appears under Connected with a green indicator and a tool count.
Devin: open the Cascade MCP marketplace, where appsignal appears under Installed as Enabled with its tool count.

Then try a prompt that calls a read tool, such as “List my AppSignal applications”. A list of your app_name/app_environment pairs confirms the tools are working. If the agent reports no applications, check that you authorized the right organization during OAuth, or that your MCP token is scoped to the applications you expect. For what AppSignal MCP logs, how to fix a failing tool call, and what the toolset deliberately leaves out, see Using AppSignal MCP.

Getting help

We encourage you to join our Discord community where you can:

Get help with AppSignal MCP setup
Share feedback and suggestions
Connect with other developers using AppSignal MCP
Stay updated on new features and improvements

Look for the dedicated #mcp channel where our team actively monitors and responds to questions.

​Authentication

​Configuration

​Claude Code

​Claude app

​Cursor

​Devin

​Zed

​VS Code

​GitHub Copilot CLI

​Gemini CLI

​OpenAI Codex

​Verify the connection

​Getting help

Authentication

Configuration

Claude Code

Claude app

Cursor

Devin

Zed

VS Code

GitHub Copilot CLI

Gemini CLI

OpenAI Codex

Verify the connection

Getting help