Connect via MCP

Indexhog runs a hosted, remote Model Context Protocol (MCP) server. Point an MCP-capable client at one URL, sign in once, and your agent can manage projects, organizations, and billing through the same API the dashboard uses. The server is an OAuth 2.1 resource server — you authorize in the browser, so there is no API key to copy or store.

The server URL

Add this server to your client. On first use the client opens a browser window for you to sign in and authorize — the OAuth 2.1 + PKCE handshake (discovery, dynamic registration, token exchange) happens automatically.

{
"mcpServers": {
  "indexhog": {
    "url": "https://mcp.indexhog.com"
  }
}
}

Agent discovery

Inspect the REST surface that backs the MCP tools:

• OpenAPI 3.1 specification — Machine-readable contract for API clients and code generators.
• Capabilities manifest — Agent-oriented inventory of endpoints, scopes, authentication, and features.

Add the server to your client

Claude (Desktop & claude.ai)

Open Settings → Connectors → Add custom connector, give it a name, and paste the server URL:

https://mcp.indexhog.com

Claude prompts you to sign in and authorize on first use. The tools then appear in the connector list.

Claude Code

Add the server from the CLI as a streamable-HTTP transport:

claude mcp add --transport http indexhog https://mcp.indexhog.com

Run /mcp inside Claude Code to trigger the browser sign-in, then confirm the server shows as connected.

Cursor

Add it to your project's .cursor/mcp.json (or the global ~/.cursor/mcp.json):

{
"mcpServers": {
  "indexhog": {
    "url": "https://mcp.indexhog.com"
  }
}
}

Open Settings → MCP, confirm the server is listed, and complete the sign-in when prompted.

VS Code

Register the server with the CLI:

code --add-mcp '{"name":"indexhog","url":"https://mcp.indexhog.com"}'

Or add it to .vscode/mcp.json using the same shape as the Cursor example above.

Other clients (mcp-remote fallback)

Clients that only speak stdio can bridge to the remote server with mcp-remote:

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

Authentication & sessions

The server implements OAuth 2.1 + PKCE with dynamic client registration (RFC 7591) and exposes protected-resource metadata (RFC 9728), so compliant clients discover everything they need from the URL alone.

• Discovery: GET https://mcp.indexhog.com/.well-known/oauth-protected-resource returns the authorization server (https://api.indexhog.com/api/auth).
• Token: the client runs the OAuth flow in your browser and sends Authorization: Bearer <jwt> on every call.
• Sessions are short-lived. A 401 always carries a WWW-Authenticate: Bearer … header pointing at the resource-metadata URL, so clients re-authorize automatically.
• Request bodies are capped at 1 MB.

Available tools

The MCP server exposes the agent-callable subset of the external contract as tools, grouped below. The live, always-current list is whatever your client's tools/list returns — treat that as the source of truth and follow the linked references for full arguments and responses.

API-key management and other auth-tier operations remain REST/session-only. External documentation does not automatically make an operation an MCP tool.

Use the product skill

The product skill packages everything an agent needs to drive Indexhog — connection rules, org-context flow, pagination and response-envelope conventions, tool disambiguation, and step-by-step workflows. Install it alongside the MCP server for far fewer first-run mistakes.

• Download the bundle: product-skill.zip
• View the source: SKILL.md · workflows.md

To install in Claude Code, unzip into your skills directory:

mkdir -p ~/.claude/skills
unzip product-skill.zip -d ~/.claude/skills
# → ~/.claude/skills/product/SKILL.md

For claude.ai, upload the unchanged product-skill.zip in Settings → Capabilities → Skills.

Troubleshooting

Best Practices

• Let the client handle OAuth: Never paste tokens into MCP config — the browser sign-in is the supported path and keeps credentials out of files.
• Pick the org once per session: Resolve the organization id early and reuse it; most failures trace back to missing org context.
• Prefer MCP for agents, REST for CI: Interactive agents authorize via OAuth; headless automation uses a scoped tkn_ PAT on the REST API.
• Ship the skill with the server: The skill encodes the conventions (offset/limit pagination, the response envelope) that agents otherwise learn by failing.

Next Steps

1. Authenticate the REST way too: Follow Quick Start to issue a PAT for headless automation.
2. Choose scopes intentionally: Review Scopes & Permissions before issuing tokens.
3. Browse the surface: Start at the Projects reference to see what the tools wrap.