Connect an AI agent

Claude (claude.ai and Claude Desktop)

1. In Claude, open Customize, then Connectors, choose + Add and then Add custom connector.
2. Name it FlareWarden, enter the server address, https://mcp.flarewarden.com/mcp, and choose Continue.
3. Under Authentication, choose Sign in when needed. The public tools then work at once, and Claude asks you to sign in the first time you ask about your account. Claude may mark No sign-in as detected; with it, the account tools can't sign in. Leave the OAuth client on Use Claude's published identity and choose Add.
4. Ask Claude about your sites. When it shows Authorization required, choose Connect. Claude opens FlareWarden, where you sign in, choose the account, the permissions and the daily monitor budget, and approve.

On Claude's Team and Enterprise plans an Owner adds custom connectors for the organization; see Claude's guide to custom connectors.

Claude Code

The plugin

The FlareWarden plugin adds the server and ten skills that guide Claude through common jobs, such as setting up a site, running a status page or writing an uptime report:

/plugin marketplace add Flare-Warden/agent-plugins
/plugin install flarewarden@flarewarden

The plugin connects without a token. To use your account through it, run /mcp in Claude Code, choose the FlareWarden server and sign in in your browser.

The server with a personal token

Create a personal access token, then add the server with it:

claude mcp add --transport http flarewarden https://mcp.flarewarden.com/mcp \
  --header "Authorization: Bearer fwp_…"

Leave out --header to sign in through /mcp instead.

ChatGPT

Add FlareWarden as a custom MCP server: on ChatGPT's Plugins page choose the plus button and then Add custom MCP server, name it FlareWarden, enter the server address and choose OAuth for authentication. ChatGPT then sends you to FlareWarden to sign in and approve the connection. Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace's settings.

Cursor

Add the server to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for every project. With a personal token in the environment variable FLAREWARDEN_TOKEN:

{
  "mcpServers": {
    "flarewarden": {
      "url": "https://mcp.flarewarden.com/mcp",
      "headers": { "Authorization": "Bearer ${env:FLAREWARDEN_TOKEN}" }
    }
  }
}

Without headers, Cursor can sign you in to FlareWarden with OAuth instead.

Codex

Add the server to Codex's config.toml, with a personal token in the environment variable FLAREWARDEN_TOKEN:

[mcp_servers.flarewarden]
url = "https://mcp.flarewarden.com/mcp"
bearer_token_env_var = "FLAREWARDEN_TOKEN"

Or leave out bearer_token_env_var and run codex mcp login flarewarden to sign in. The plugin's Codex and Cursor marketplace files are in github.com/Flare-Warden/agent-plugins.

Any other MCP client

• Transport: Streamable HTTP at the server address. The server keeps no session, so every request stands alone.
• Signing in: OAuth 2.1, authorization code with PKCE (S256). A call that needs your account is answered HTTP 401 with a WWW-Authenticate header naming the server's protected resource metadata, which leads to FlareWarden's authorization server. Clients register with a Client ID Metadata Document or Dynamic Client Registration.
• Or a token: send a personal access token as Authorization: Bearer fwp_… on every request.
• Server card: https://mcp.flarewarden.com/mcp/server-card

The read-only server

https://mcp.flarewarden.com/mcp/readonly lists only the tools that read and need no permission beyond Read: 24 of the 65 tools. It never lists a tool that changes something, nor the plan and draft tools that lead to one. Signing in through it asks for Read alone.

A connection approved for the read-only server never reaches the full one. A connection approved for the full server, and every personal token, also works on the read-only server.