Settings

Team-level configuration. Project data sources live in each project's settings.

MCP tokens

Authenticate the Offcrawl MCP server from Claude or any MCP client — set the token as OFFCRAWL_MCP_TOKEN in your mcp-config. Scoped tokens only see one project. Admin-only.

Loading…

How to connect

The MCP server exposes Offcrawl's data to Claude — ask questions in plain language (“list projects”, “crawl-budget waste on agence-slashr”, “striking-distance pages”) and it reads reports, the Explorer and log aggregates. Create a token above, then wire it in. Phase 1 runs over stdio on the box; the claude.ai connector is on the roadmap.

1 · Add it to a Claude Code session

Replace <your-token> with the secret shown once at creation.

claude mcp add offcrawl --env OFFCRAWL_MCP_TOKEN=<your-token> \
  -- pnpm --dir /opt/offcrawl/apps/mcp start

2 · Or via an mcp-config.json (headless runs)

Same file the weekly insights runner uses.

{
  "mcpServers": {
    "offcrawl": {
      "command": "pnpm",
      "args": ["--dir", "/opt/offcrawl/apps/mcp", "start"],
      "env": { "OFFCRAWL_MCP_TOKEN": "<your-token>" }
    }
  }
}

3 · Headless one-off

--strict-mcp-config isolates it to just this server; --allowedTools scopes to the offcrawl tools.

claude -p "quel est le budget de crawl gaspillé sur agence-slashr ?" \
  --mcp-config mcp-config.json --strict-mcp-config --allowedTools mcp__offcrawl

Tools: list_projects, get_project_context, get_report, query_explorer, get_url_facts_overview, get_logs_aggregate, save_insight. A scoped token only sees its project.