Our MCP server

The Flare MCP server allows you to integrate Flare's error tracking and performance monitoring capabilities directly into your AI-powered development workflows. Use it with AI assistants like Claude to automatically monitor, analyze, and resolve application errors, and investigate performance issues.

What is MCP?

MCP (Model Context Protocol) is an open protocol that enables AI assistants to securely connect with external data sources and tools. By using the Flare MCP server, your AI assistant gains direct access to your error tracking and performance monitoring data and can perform actions in Flare on your behalf.

Key features

With the Flare MCP server, you can ask your AI assistant to:

• "Show me the latest errors from my project"
• "Fix the error regarding the PHP syntax error in myfile.php"
• "Mark the error as resolved in Flare"
• "Fix error ERROR-ID-HERE and mark the error as resolved"
• "Show me all slow routes in my app"
• "Show me the monitoring summary for my project"
• "List the slowest database queries from the last 7 days"
• "Show me traces for this route aggregation"
• "Snooze this error until next week"
• "Assign this error to Alex"
• "Create a note in Flare with the results of your investigation about this error"
• "Show me the latest logs from my project"
• "Search the logs for any database connection errors"

Authentication

The Flare MCP server is at https://flareapp.io/mcp and authenticates with OAuth 2.1. Every supported client opens a browser, sends you to Flare to grant access, and stores a refreshable token. No tokens are pasted by hand and the client never sees your password.

When you authorize, you pick which teams and projects the connection can access — the same scope picker used for personal access tokens.

If your client doesn't support MCP OAuth yet, you can fall back to a personal access token sent as a Bearer header.

Installation

Pick your client and follow the steps. After installation, jump to Project hint so your assistant knows which Flare project to use.

Claude Code

Add the server with the Claude Code CLI:

claude mcp add --transport http flare https://flareapp.io/mcp

Then in a Claude Code session, run /mcp and follow the browser prompt to authorize. Tokens are stored and refreshed automatically.

Verify with:

claude mcp get flare

Claude Desktop and claude.ai

Custom connectors live in the same place on Claude Desktop and claude.ai:

1. Open Settings → Connectors (or Organization settings → Connectors on Team and Enterprise plans).
2. Click Add custom connector.
3. Set the Remote MCP server URL to https://flareapp.io/mcp.
4. Click Add, then complete the OAuth flow in your browser.

Codex (CLI, desktop app, and IDE extension)

The Codex CLI, desktop app, and IDE extension share a single config file at ~/.codex/config.toml. Add:

[mcp_servers.flare]
url = "https://flareapp.io/mcp"

Then start the OAuth flow:

codex mcp login flare

If you set up the server through the desktop app's Settings → MCP panel instead, the same entry appears in config.toml and the OAuth flow runs in your browser when you first use the server.

Cursor

Add Flare in Cursor Settings → MCP → Add custom server, or drop this into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "flare": {
      "url": "https://flareapp.io/mcp"
    }
  }
}

Cursor opens a browser to authorize the first time the server is used and stores the resulting token for you.

OpenCode

Add Flare to opencode.json (project root) or ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flare": {
      "type": "remote",
      "url": "https://flareapp.io/mcp"
    }
  }
}

Then authorize:

opencode mcp auth flare

OpenCode discovers the OAuth endpoints automatically via dynamic client registration (RFC 7591) and stores tokens at ~/.local/share/opencode/mcp-auth.json.

Alternative: pinned access token

If your client doesn't support MCP OAuth yet (for example JetBrains' Junie), create a personal access token with read and write scope and send it as a Bearer header.

For Junie, edit ~/.junie/mcp/mcp.json:

{
  "mcpServers": {
    "flare": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://flareapp.io/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <YOUR-PERSONAL-ACCESS-TOKEN>"
      }
    }
  }
}

Project hint

To help your AI assistant pick the right project when there's more than one, add a one-line hint to your project's instructions file (for example CLAUDE.md, AGENTS.md, or your IDE's equivalent):

When the user asks to show or investigate errors, performance issues,
or logs, use the Flare MCP server. The project name in Flare is
INSERT-YOUR-PROJECT-NAME-HERE.

Alternative: agent skill

If you're looking for a simpler setup that works across more AI coding tools, check out the Flare agent skill. It teaches any compatible AI coding agent to use the Flare CLI, with no per-client server configuration required.

Beta status

This functionality is currently in beta. If you have any feedback or questions, please reach out to us at [email protected].

Available commands

Once configured, your AI assistant can:

• List projects: View all projects associated with your Flare account
• Show errors: Display recent errors from a specific project
• View error details: Get full information about a specific error including stack traces and context
• Resolve errors: Mark errors as resolved directly from your AI conversation
• Snooze errors: Snooze errors to temporarily suppress notifications (until a date, forever, for a number of occurrences, or until the next application version)
• Unsnooze errors: Resume notifications for previously snoozed errors
• Assign errors: Assign errors to team members for follow-up
• List team members: View team members for a project to find assignees
• Search errors: Find errors matching specific criteria
• Create notes: Add investigation notes to errors for team collaboration
• Browse logs: Search, filter, and paginate through project logs by severity, hostname, entry point type, or free-text search
• Monitor performance: View monitoring summaries, list aggregations by type (routes, queries, jobs, commands), inspect detailed metrics and trends, and browse traces for any aggregation

Security

Each OAuth connection from a client to the Flare MCP server is scoped to the teams and projects you select during the consent flow, and you can revoke it at any time from your account settings. Personal access tokens used as a Bearer fallback can be scoped and revoked from the personal access tokens screen.