Gridar

@gridar/mcp-server

Model Context Protocol server for Gridar.

The server exposes the Gridar REST API (https://api.gridar.app/api/v1) as 69 gridar_* tools. An MCP client can read and change the sites, articles, landings, tracked keywords, autopilot, site memory and Search Console data of the Gridar account behind the token, and run SEO checks on them.

Versions

Checked on 2026-10-21 with npm view @gridar/mcp-server version and the hosted server card. The npm package lags behind: use the hosted server.

Requirements

• A Gridar account on the Pro or Agency plan.
• The OAuth login succeeds on every plan, but on Trial and Solo every tool call answers HTTP 403: "Accès API réservé aux plans Pro et Agence".

Install: hosted server (recommended)

Nothing to install on your machine.

What the OAuth login does

1. You add https://mcp.gridar.app/mcp to your client.
2. Without a token, the server answers 401 with a WWW-Authenticate header that points to /.well-known/oauth-protected-resource. The client discovers the OAuth endpoints from there.
3. The client opens the Gridar login page. Sign in if needed, then click Autoriser.
4. Gridar creates an API token named after the client (for example MCP - Claude Code) and hands it to the client.
5. The token shows up at https://www.gridar.app/account/api-keys. Revoke it there to cut access.

Claude (claude.ai and Claude Desktop)

On claude.ai: Settings > Connectors, add a custom connector with the URL https://mcp.gridar.app/mcp. Claude opens the Gridar login page; authorize and the connector is live.

Claude Desktop through its config file uses the mcp-remote bridge:

{

"mcpServers": { "gridar": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.gridar.app/mcp"] } } }

The file lives at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Restart Claude Desktop afterwards.

ChatGPT

1. Open Settings > Connectors, or turn on Developer Mode for custom connectors.
2. Add a connector by URL: https://mcp.gridar.app/mcp.
3. ChatGPT opens the Gridar login page. Authorize.

OpenAI restricts custom connectors by account type. The Gridar page lists ChatGPT Pro, Team, Enterprise, or Developer Mode; check OpenAI's current rules.

Claude Code

claude mcp add --transport http gridar https://mcp.gridar.app/mcp

OAuth starts on the first call. For a session without a browser, pass a token in a header:

claude mcp add --transport http gridar https://mcp.gridar.app/mcp \

--header "Authorization: Bearer btb_xxx"

Cursor

Settings > MCP > Add server, server of type URL: https://mcp.gridar.app/mcp.

Codex CLI, SDKs and other clients

Any MCP client that speaks Streamable HTTP connects to https://mcp.gridar.app/mcp and finds the OAuth flow on its own (see step 2 above). A headless agent sends Authorization: Bearer btb_xxx with a token created at https://www.gridar.app/account/api-keys.

Install: local stdio via npm

The npm package is behind. @gridar/mcp-server on npm is 0.4.2 with 43 tools. The hosted server and this source are 0.7.0 with 69 tools. The tool list in this README matches 0.7.0.

The 26 tools missing from npm 0.4.2: gridar_action_strategic_opportunity, gridar_ai_overview_readiness, gridar_ai_visibility_summary, gridar_approve_strategy, gridar_build_cluster, gridar_check_renderability, gridar_classify_intent, gridar_cluster_map, gridar_create_landing, gridar_export_page_prompt, gridar_generate_landing, gridar_generate_sister_article, gridar_index_coverage, gridar_indexnow_setup, gridar_indexnow_submit, gridar_link_opportunities, gridar_link_pages, gridar_list_strategic_opportunities, gridar_mark_page_built, gridar_propose_keyword_strategy, gridar_pull_build_queue, gridar_refresh_strategic_opportunities, gridar_run_ai_visibility, gridar_serp_analyze, gridar_site_seo_score, gridar_submit_sitemap.

The package installs the gridar-mcp binary and reads its token from BLOG_DASHBOARD_TOKEN.

Claude Desktop:

{

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

Claude Code:

claude mcp add gridar \

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

Any other client: spawn the process over stdio with the token in its environment.

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

To get all 69 tools locally, build this source instead (see Development).

Environment variables

Names only. Never commit a real token.

Stdio (local)

Self-hosted HTTP (node dist/http.js)

In HTTP mode the token comes from each request's Authorization header and is scoped to that request with AsyncLocalStorage. BLOG_DASHBOARD_TOKEN stays a fallback: do not set it on a shared server with MCP_REQUIRE_AUTH=false, or every caller acts as that account.

HTTP endpoints:

Plans and limits

Sources: PLAN_API_LIMITS in backend/sites_mgmt/api_v1.py, Subscription.get_limits() in backend/sites_mgmt/models.py.

• Each tool call sends one request to the Gridar API and counts against the hourly limit. Past the limit the API answers 429.
• Three tools debit the monthly article quota, or one credit once the quota is used up: gridar_generate_article, gridar_generate_sister_article, gridar_generate_landing.
• An API error comes back as a tool error: Gridar API error (HTTP ): , followed by the JSON body.

Tools (69)

The Effect column flags what a call changes:

• destructive: deletes or disables something; the client should confirm first.
• publishes: puts content live or makes a page public.
• quota: debits one article from the monthly quota, or one credit.
• writes: changes data in Gridar without putting anything live.
• none: read only.

Account and sites

Articles

Audit and content

Site health

| gridar_site_seo_score | Composite 0 to 100 site score from 9 weighted checks (i