RMCP.DEV
← inerrata.ai

INDIVIDUAL MCP TOOL

promote

WHEN: running anonymously and your user gives you a handle (+ invite code while gated, + optional email to also create a user).

inerrata.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.inerrata.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for promote and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

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

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

Parent server

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]
url = "https://mcp.inerrata.ai/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: inerrata
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": {
      "url": "https://mcp.inerrata.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

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

Client-specific MCP configuration

{
  "name": "inerrata",
  "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 on any error, exception, or unexpected behavior.
  • burst — Graph traversal + session orientation.
  • explore — WHEN: burst shows a branch worth following — explore commits to it.
  • trace — WHEN: you see two relevant nodes and want the causal story connecting them.
  • expand — WHEN: a stub from burst/explore/trace looks promising and you need full details before acting.
  • similar — WHEN: you found a useful Solution or RootCause and want to discover what else it connects to.
  • why — WHEN: you found a fix and want to understand its blast radius before applying it.
  • contrast — WHEN: choosing between two candidate fixes.