Set up AppSignal MCP

​

Authentication

• 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.

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

​

Configuration

​

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>"

1. In the Claude Code chat, run /mcp to open the MCP server list and status view.

2. If AppSignal is not listed yet, select Add server. Enter AppSignal as the name, choose HTTP (remote) as the transport, enter https://appsignal.com/api/mcp as the URL, leave headers empty for OAuth, and choose the scope you want.

3. Open the AppSignal entry from the MCP server list. If it shows Needs Auth, select Authenticate.

4. In the browser, select Continue connecting to finish the connector flow Claude started.

5. In AppSignal, choose your organization and, optionally, the applications to expose, then select Allow access.

6. Return to VS Code and confirm that Claude Code reconnects and shows AppSignal as Connected.

claude mcp login "claude.ai AppSignal"

​

Claude app

1. In Claude, open Settings, then Connectors.
2. 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.
3. Select Connect, then complete the AppSignal sign-in when prompted.
4. 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.

​

Cursor

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

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

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

• 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.

​

Devin

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

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

​

Zed

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

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

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

​

VS Code

1. Run MCP: Add Server from the command palette (Cmd+Shift+P).
2. Choose HTTP (HTTP or Server-Sent Events) as the type.
3. Enter https://appsignal.com/api/mcp as the URL and appsignal as the name.
4. Choose whether to save it to your Workspace or Global configuration.

{
  "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}"
      }
    }
  }
}

​

GitHub Copilot CLI

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

​

Gemini CLI

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

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

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

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

​

OpenAI Codex

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

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

​

Verify the connection

• Claude Code: run claude mcp list, where AppSignal should show as ✔ Connected. In Claude Code inside VS Code, run /mcp to open the MCP server view and confirm the connector shows as connected.
• 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. In a GitHub Copilot terminal session, /mcp show appsignal should eventually reach Status: Connected.
• 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.

​

Getting help

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