@gridar/mcp-server

Model Context Protocol server for Gridar.

Drive most of the Gridar dashboard from Claude Code, Claude Desktop, Cursor, Codex, Continue, or any other MCP-compatible client. Generate articles, edit them, track keywords, audit SEO, configure autopilot, and surface GSC proof of value.

What it does

Once installed, your AI client gets 61 tools covering the dashboard surface.

Discovery & status

Articles

Briefing & audit

Keywords

Competitors & SEO

Autopilot

RAG memory (per-site brain)

Proof of value (GSC attribution)

Reporting

Strategic SEO opportunities

Conversation patterns

You: Generate a guide article on "meilleur CRM PME Quebec" for site 12, in French, then audit it and publish if it scores above 80.

Claude: (calls gridar_get_brief -> gridar_generate_article -> gridar_audit_article -> gridar_update_article with status='published') Done. Score 87/100. Published as /blog/meilleur-crm-pme-quebec.

You: Show me the proof page for site 12 and copy its public URL to share with my client.

Claude: (calls gridar_proof_summary then gridar_enable_proof_share) +3.2k impressions gained, +118 clicks. Public URL: https://gridar.app/proof/xxxxxxxxxxxxxxxx

You: Add a manual note to site 12's brain so future generation always mentions our 2026 Quebec compliance certification.

Claude: (calls gridar_add_memory with kind='decision') Saved.

Two ways to run

If you're not sure: use the hosted HTTP transport.

Installation

1. Get an API token

Sign in at https://gridar.app and visit Account -> API keys to create a personal token. Tokens look like btb_xxxxxxxx and are shown once. Requires Pro or Agency plan (free and solo are blocked).

2a. Hosted HTTP transport (recommended)

The server is reachable at https://mcp.gridar.app/mcp. Auth is per-request via Authorization: Bearer <your_token>.

Claude Code

claude mcp add gridar --transport http https://mcp.gridar.app/mcp \
  --header "Authorization: Bearer btb_your_token_here"

Claude Desktop

{
  "mcpServers": {
    "gridar": {
      "transport": "streamable-http",
      "url": "https://mcp.gridar.app/mcp",
      "headers": {
        "Authorization": "Bearer btb_your_token_here"
      }
    }
  }
}

Codex CLI / Cursor / any HTTP-aware MCP client

Same shape: URL + Authorization header. Refer to your client's MCP HTTP transport docs.

2b. Stdio (local npm)

Claude Desktop

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

{
  "mcpServers": {
    "gridar": {
      "command": "npx",
      "args": ["-y", "@gridar/mcp-server"],
      "env": {
        "BLOG_DASHBOARD_TOKEN": "btb_your_token_here"
      }
    }
  }
}

Restart Claude Desktop.

Claude Code

claude mcp add gridar --env BLOG_DASHBOARD_TOKEN=btb_xxx -- npx -y @gridar/mcp-server

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.gridar]
command = "npx"
args = ["-y", "@gridar/mcp-server"]
env = { BLOG_DASHBOARD_TOKEN = "btb_your_token_here" }

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "gridar": {
      "command": "npx",
      "args": ["-y", "@gridar/mcp-server"],
      "env": { "BLOG_DASHBOARD_TOKEN": "btb_xxx" }
    }
  }
}

Any other client

Spawn with stdio transport:

BLOG_DASHBOARD_TOKEN=btb_xxx npx -y @gridar/mcp-server

Configuration

Stdio mode (local npm)

HTTP mode (self-hosting gridar-mcp-http)

Auth is per-request: every POST /mcp must carry Authorization: Bearer btb_xxx. The token is propagated to the Gridar REST API for that single request via Node AsyncLocalStorage, so a single hosted process safely serves many users without cross-contamination.

Endpoints:

• POST /mcp - MCP Streamable HTTP (initialize + tool calls)
• GET /mcp - SSE notifications stream
• DELETE /mcp - explicit session teardown
• GET /health - healthcheck JSON { status, name, version, transport }

Costs & quotas

• generate_article consumes 1 article from monthly quota (or 1 credit)
• bulk_audit and rebuild_memory are heavier (Gemini / Voyage tokens billed to your plan)
• All other tools are free under the plan-level rate limit (Pro: 30/h, Agency: 200/h)

Safety notes

Destructive tools (clearly marked in their descriptions):

• gridar_delete_article permanently removes a hosted article + cascades attribution
• gridar_delete_memory removes a RAG chunk
• gridar_revoke_proof_share kills the public proof URL immediately
• gridar_untrack_keyword is a soft delete (sets is_active=False)

When a user asks for one of these in chat, the MCP-compatible client will typically ask for confirmation. If you want stricter gating, restrict your API token's scope or use a separate token for read-only sessions.

Development

cd mcp-server
npm install
npm run build
BLOG_DASHBOARD_TOKEN=btb_xxx node dist/index.js

Debug with the MCP Inspector:

BLOG_DASHBOARD_TOKEN=btb_xxx npx @modelcontextprotocol/inspector node dist/index.js

License

MIT