mcp-server-brime

Connect AI assistants to Brime's live web tools: search, extract, and multi-round research with citations.

Documentation | npm Package | Get Your Brime API Key | GitHub

Installation

Connect to Brime's hosted MCP server:

https://mcp.brime.dev/mcp

Get your API key → (free tier: 1,000 credits/month, no card)

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "brime": {
      "url": "https://mcp.brime.dev/mcp"
    }
  }
}

Restart Cursor. The first tool call opens an auth page in your browser where you paste your key. After that, it's saved for the session.

VS Code

Add to .vscode/mcp.json or your User settings:

{
  "servers": {
    "brime": {
      "url": "https://mcp.brime.dev/mcp"
    }
  }
}

Claude Code

claude mcp add brime https://mcp.brime.dev/mcp --transport http

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "brime": {
      "url": "https://mcp.brime.dev/mcp"
    }
  }
}

Codex CLI

codex mcp add brime https://mcp.brime.dev/mcp

Windsurf / generic HTTP

Any MCP-compatible client that speaks Streamable HTTP can point at https://mcp.brime.dev/mcp directly.

Tools

Tool	What it does	Cost
brime_search	Live web search with snippets + a short synthesised answer (~500 ms)	0.5 credits
brime_extract	URL → clean markdown (HTML / PDF / DOCX / SPA), 1–10 URLs per call	1 / URL
brime_research	Multi-round agent research with citations (~30–90 s)	5 credits
brime_research_status	Poll a long-running research job	—

All tools advertise typed outputSchema and structuredContent, so MCP clients with strict validation (Claude Desktop, modern Cursor) can render the output natively without parsing free text.

Configuration

API key

The hosted server resolves your key in this order, on every request:

1. Authorization: Bearer sk-brime-… header
2. ?apiKey=sk-brime-… query string (URL-config parity with other vendors)
3. URL elicitation — first tool call returns a key-entry URL the client opens in the user's browser; key persists in a short-lived (10 min) session

The key never appears in the MCP transcript or in your LLM context.

Override the base URL

For staging or self-hosting, set BRIME_BASE_URL on the stdio binary (see below) or point your MCP client at a custom url.

Local stdio mode

Run the server locally over stdio

npx -y mcp-server-brime

Then point your client at the local binary:

{
  "mcpServers": {
    "brime": {
      "command": "npx",
      "args": ["-y", "mcp-server-brime"]
    }
  }
}

Configuration knobs (env vars):

• BRIME_API_KEY — pre-set the key; otherwise the agent will ask on first use and save to ~/.brime/credentials (0600).
• BRIME_BASE_URL — override the API endpoint (default https://api.brime.dev).
• BRIME_TOOLSETS — comma-separated whitelist, e.g. search,extract.
• BRIME_READ_ONLY — true hides mutating tools (currently only brime_set_key).
• LOG_LEVEL — debug / info / warn / error.

Troubleshooting

Common issues

• Tools don't appear — restart the client after editing config; verify JSON is valid.
• Auth page won't accept the key — keys start with sk-brime-. Generate a fresh one at platform.brime.dev/keys.
• Agent keeps asking for the key (hosted) — sessions expire after 10 min of inactivity. Submit the key once and use the tool within the window.
• Agent keeps asking for the key (stdio) — ~/.brime/credentials may not be writable. Run ls -la ~/.brime/, fix perms, retry. Reset with rm -rf ~/.brime/.

Development

pnpm install
pnpm build
pnpm test
pnpm inspector   # launch the MCP Inspector against the local stdio bundle

Links

• Documentation
• Changelog
• Issues
• MCP spec

License

MIT