What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants interact with external tools. Valoryx MCP server gives AI agents direct access to your documentation.

Learn about MCP

Local (stdio)

Available now

Runs alongside the binary on your machine. Zero network overhead. Works with self-hosted and cloud installations.

Cloud (remote HTTP)

Available now

No binary needed. Connect via HTTPS with your API key. Streamable HTTP transport, stateless, Bearer token auth.

Endpoint:

https://app.valoryx.dev/mcp

Quick Setup

Any MCP client that speaks HTTP. Zero install — just add the endpoint and your API key.

{
  "mcpServers": {
    "docplatform": {
      "type": "http",
      "url": "https://app.valoryx.dev/mcp",
      "headers": {
        "Authorization": "Bearer dp_live_..."
      }
    }
  }
}

Test with curl: curl -X POST https://app.valoryx.dev/mcp -H "Authorization: Bearer dp_live_..." -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Add to your project .mcp.json:

{
  "mcpServers": {
    "docplatform": {
      "type": "stdio",
      "command": "docplatform",
      "args": ["mcp", "--workspace", "my-docs"],
      "env": {
        "DOCPLATFORM_API_KEY": "dp_live_..."
      }
    }
  }
}

Add to Claude Desktop settings (Settings, Developer, MCP Servers):

{
  "mcpServers": {
    "docplatform": {
      "command": "docplatform",
      "args": ["mcp", "--workspace", "my-docs"],
      "env": {
        "DOCPLATFORM_API_KEY": "dp_live_..."
      }
    }
  }
}

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "docplatform": {
      "command": "docplatform",
      "args": ["mcp", "--workspace", "my-docs"],
      "env": {
        "DOCPLATFORM_API_KEY": "dp_live_..."
      }
    }
  }
}

24 Tools

Everything your AI assistant needs to manage documentation

Read & Discover (8)

list_workspacesList accessible workspaces

get_workspaceWorkspace details (members, pages, git status)

list_pagesList all pages (lightweight)

get_treeFull page tree hierarchy

get_manifestFull workspace map with link graph (best for agents)

read_pageRead page content + metadata + hash

get_contextRAG context: page + parent + siblings + linked

searchFull-text search across all pages

Write & Edit (5)

write_pageCreate or update (smart upsert, no hash needed)

update_pageUpdate with conflict detection (hash required)

delete_pageSoft-delete a page

move_pageMove/rename (auto-updates wikilinks)

writing_assistAI improve / shorten / simplify / translate

Workspaces & Versions (5)

create_workspaceCreate a new documentation workspace

list_versionsList workspace versions (v1.0, v2.0, etc.)

create_versionSnapshot current state as a version

exportExport workspace as static site (zip_base64)

get_activityActivity feed (recent actions, reverse chrono)

Quality & Theming (4)

validate_linksScan for broken wikilinks

quality_scanFull quality audit (score + findings)

get_themeGet published site theme

update_themeSet theme (default, dark, forest, rose, amber)

Collaboration (2)

list_commentsRead threaded comments on a page

add_commentAdd a comment or threaded reply

Machine-readable reference: endpoint — call tools/list for the full schema.

See It in Action

A real AI session updating documentation

User: We just shipped OAuth support. Update the
      authentication docs to include the new flow.

Claude: I'll update the authentication docs.
[calls docplatform_search: "authentication"]
Found: docs/auth/overview.md

[calls docplatform_read_page: "auth/overview"]
Current content describes basic auth only.

[calls docplatform_update_page: "auth/overview"
 with new OAuth 2.0 section added]
✓ Page updated. Content hash: a3f8c2...
✓ Auto-committed to git: "Add OAuth 2.0 docs"

[calls docplatform_get_context: "auth/overview"]
Found 2 linked pages that reference auth.

[calls docplatform_update_page: "api-keys"]
✓ Updated API keys page with OAuth token section

[calls docplatform_validate_links]
✓ No broken links across workspace.

Done. Updated auth docs + 1 linked page.
Changes auto-synced to git. Published docs
updated within 30 seconds.

Context Graph

When your AI reads a page, it gets the full picture

docplatform_get_context("auth/overview")

Returns:
  page       → auth/overview.md (full content)
  parent     → auth/_index.md
  children   → auth/oauth.md, auth/api-keys.md
  siblings   → auth/sso.md, auth/webauthn.md
  linked     → getting-started/quickstart.md
  metadata   → workspace slug, page path, content hash

No other documentation platform provides this level of context to AI agents.

Security

API Key Auth

Bearer token, scoped per workspace. SHA-256 hashed with pepper. Read tools need read scope; write tools need edit or admin.

Conflict Detection

Hash-based optimistic concurrency prevents data loss.

Audit Trail

Every mutation logged with user, timestamp, and operation.

Git Sync

Every MCP write becomes a git commit. Full history.

Troubleshooting

Issue	Solution
"workspace not found"	Verify slug matches URL in app settings
"invalid API key"	Check key has not been rotated; regenerate in Settings, API Keys
"command not found: docplatform"	Verify binary is in PATH (which docplatform)
"tools not appearing"	Fully quit and reopen your MCP client (servers load on startup)
"connection refused"	Ensure docplatform serve is running before starting MCP client
"conflict detected"	Re-read with read_page, merge changes, retry update
HTTP endpoint returns HTML / 404	Self-hosted only: the `mcp-server` subcommand listens on `:8081` — add a reverse proxy route at `/mcp`. On cloud (app.valoryx.dev/mcp) it is pre-configured.
403 "scope does not allow this action"	Create a new key in Settings → API Keys with the required scope: `read` for read tools, `edit` or `admin` for write tools.
406 "Not Acceptable"	HTTP transport requires `Accept: application/json, text/event-stream` header.

Ready to connect AI to your docs?

Get your API key and start using MCP in under a minute.

Install Valoryx Read the Guide

Connect your docs to AI