The index365 MCP server. It gives Claude Code, Codex, and Cursor read access to your audit runs and findings, plus the ability to start audits, over the public /api/v1.

This is a thin wrapper: no audit logic, no database access, no filesystem access, no ambient workspace permissions. It authenticates with a scoped i365_ API key from the host environment and is read-only by default (starting an audit needs the runs:write scope).

index365 runs two audits: AI-Readiness (how well AI agents and AI search can read a site) and Marketing Signal (find, trust, act, measure, improve). Each run produces a score plus findings with stable IDs, evidence, and machine-readable remediation.

Install

Claude Code

claude mcp add index365 -e INDEX365_API_KEY=<your i365_ key> -- npx -y @index365/mcp

Codex / Cursor / any MCP host

{
  "mcpServers": {
    "index365": {
      "command": "npx",
      "args": ["-y", "@index365/mcp"],
      "env": { "INDEX365_API_KEY": "<your i365_ key>" }
    }
  }
}

Create an API key in the dashboard (Org settings -> API keys). index365 mcp config (from @index365/cli) prints this block for you.

Tools

Read: list_projects, get_run_status, list_findings, get_finding, get_report_context, get_marketing_signal_report, list_integrations, list_connected_signals. Run: start_audit, run_marketing_signal_audit.

Prompts: triage_findings, prepare_pr_plan, marketing_fix_plan, summarize_run_for_slack.