Skip to main content
The Flare API MCP server is still in beta and is subject to change.
Flare provides a Model Context Protocol (MCP) server that exposes Flare’s search and platform APIs to any MCP-capable client. It lets agents query Flare’s threat-intel dataset, investigate a tenant’s monitored events, and manage monitoring configuration such as identifiers and severity rules, without writing any code against the REST API. The server supports two authentication methods: OAuth, where you sign in with your Flare account, and API keys. See Choosing an authentication method. For a documentation-only companion server (search across the Flare API docs themselves), see the Documentation MCP .

Available Tools

The server exposes over 30 tools. Highlights: To see every tool and its parameters, ask your MCP client to list the server’s tools.
Some tools create, edit, or delete tenant configuration. Tool calls run with your user’s permissions.
search_global requires the Global Search permission on the target tenant. Each call counts against the tenant’s monthly Global Search quota.For additional information, please refer to Global Search Quota.

Prompt Examples

  • What has Flare picked up on our monitored domain scatterholt.com in the last 24 hours?
  • Search the whole Flare dataset for chat messages mentioning "acme-corp" in the last 7 days.
  • Why did this event match our identifiers?
  • Create an identifier for the domain scatterholt.com.
  • What fields can I search on the stealer_log event type?
  • Which tenants do I currently have access to?

Connecting to the Server

The MCP server is available at the following URL:
  • https://api.flare.io/mcp

Choosing an authentication method

OAuth Setup

OAuth connections use your default tenant. To work in another tenant, connect with an API key and set X-Flare-Tenant-Id (see Targeting a specific tenant).

Claude (claude.ai and Claude Desktop)

  1. Go to Settings → Connectors → Add custom connector.
  2. Enter https://api.flare.io/mcp.
  3. Click Connect and sign in with your Flare account.
The connector is then available in both claude.ai and Claude Desktop.

ChatGPT

  1. Go to Plugins → Add → Add custom MCP server.
  2. Enter https://api.flare.io/mcp and choose OAuth authentication.
  3. Sign in with your Flare account when prompted.

API Key Setup

Authentication

In the configurations below, replace <api-key> with a Flare API key. Follow the Authentication Guide to generate one.

Targeting a specific tenant

Requests default to your account’s default tenant. To scope MCP tool calls to a specific tenant, set the X-Flare-Tenant-Id header on the MCP connection to the target tenant id. The header is optional: omitting it uses your default tenant. You can find your tenant ids via the profile_get MCP tool, or on the Profile page under the “Tenants” section (also documented in the Authentication Guide ).

Claude Code

The quickest way to add the server to a project’s config is through the Claude Code CLI:
Alternatively, you may create an .mcp.json file at the root of your project and restart Claude Code once the file is in place:
.mcp.json
The Flare tools will appear under the flare server in the /mcp command output, and Claude will call them automatically when your prompts match their descriptions.
Store the API key outside version control. Claude Code also supports reading headers from environment variables — see the Claude Code MCP docs for details.

Quotas & Rate Limits

  • Calls to search_global (Global Search) consume the tenant’s monthly Global Search quota. See Rate Limits and Quotas .
  • Standard API rate limits apply to all tools.