mcp server

Guidance your customers' agents can call.

InteractiveDox ships a hosted MCP server. Point your support bot at it, or let your customers point Cursor, Claude, ChatGPT or Copilot at it, and they read the same verified guidance your help center publishes. With an API key, your own agents can edit it too, under the same revision history as your team.

Quick start

The server is hosted; there is nothing to install or run. Read tools take your portal's product ID as an argument. You will find that ID, along with snippets pre-filled for your portal, in your workspace under MCP Connectors.

Cursor

Add to ~/.cursor/mcp.json
{
  "mcpServers": {
    "interactivedox-docs": {
      "url": "https://agent-id.interactivedox.com/mcp/portal"
    }
  }
}

Claude Code

One command in your terminal
claude mcp add --transport http interactivedox-docs \
  https://agent-id.interactivedox.com/mcp/portal

Claude Desktop

Add to claude_desktop_config.json
{
  "mcpServers": {
    "interactivedox-docs": {
      "url": "https://agent-id.interactivedox.com/mcp/portal"
    }
  }
}

ChatGPT

Settings, then Connectors, then Add MCP server
Name:  interactivedox-docs
URL:   https://agent-id.interactivedox.com/mcp/portal

Read and search, no key required

Anything a visitor to your published portal can read, an agent can read too.

  • portal_list_pagesPublic

    List a portal's navigation: every page, group and tab with slug, title, type and parent. The starting point for understanding a portal's structure.

  • portal_read_pagePublic

    Read one page's raw content (MDX or HTML) and metadata by slug.

  • portal_searchPublic

    Full-text search across one portal. The index rebuilds on every commit, so results reflect the current, verified docs.

Writes, governed like everything else

Write tools require a workspace API key, passed as Authorization: Bearer ata_…. Every write lands as a git commit in the portal's repository, so agent edits carry the same versioned, superseding history as your team's.

  • portal_create_pageAPI key

    Create a page, group or tab. Provisions the portal repo on first use.

  • portal_save_pageAPI key

    Replace one page's content, with an optional commit message. Search reindexes automatically.

  • portal_update_nodeAPI key

    Update a node's settings: title, icon, visibility, description.

  • portal_move_nodeAPI key

    Rename a slug, reparent, or reorder. Descendant slugs cascade in a single commit.

  • portal_delete_pageAPI key

    Delete a page; its children hoist to the parent.

Agents reading your guidance get the same verified, current answers as your customers. That is the point: one source of truth for both kinds of reader.