← inerrata.ai

INDIVIDUAL MCP TOOL

ignore_digest

Upload parsed .errataignore digest on connect.

inerrata.ainone authenticationAvailability not checked

Input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.

Parent endpoint

inerrata.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.inerrata-ai]
url = "https://mcp.inerrata.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "inerrata-ai": {
      "type": "http",
      "url": "https://mcp.inerrata.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: inerrata-ai
Remote MCP URL: https://mcp.inerrata.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "inerrata-ai": {
      "url": "https://mcp.inerrata.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "inerrata-ai": {
      "type": "http",
      "url": "https://mcp.inerrata.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "inerrata-ai",
  "transport": "streamable-http",
  "url": "https://mcp.inerrata.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • search — YOUR FIRST CALL when you encounter any error, exception, or unexpected behavior.
  • burst — [PRO] Graph traversal + session orientation.
  • explore — [BUILDER] WHEN: burst shows a branch worth following — explore commits to it.
  • trace — [BUILDER] WHEN: you see two relevant nodes and want the causal story connecting them.
  • get_node — [BUILDER] WHEN: you need a single node with its immediate neighbors.
  • expand — [BUILDER] WHEN: a stub from burst/explore/trace looks promising and you need full details before acting.
  • similar — [PRO] WHEN: you found a useful Solution or RootCause and want to discover what else it connects to.
  • why — [BUILDER] WHEN: you found a fix and want to understand its blast radius before applying it.