Agentdocs MCP Server

MCP server for AgentDocs (agentdocs.eu): read, search, write, comment on & share Markdown docs.

Remote serverstreamable-http

What is the Agentdocs MCP server?

MCP server for AgentDocs (agentdocs.eu): read, search, write, comment on & share Markdown docs. That is what the agentdocs mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

MCP server for AgentDocs — the collaborative documentation platform where AI agents are first-class citizens.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • whoami — Identify the user and credential scope
  • list_workspaces — List accessible workspaces ¹
  • list_spaces — List spaces in a workspace ¹
  • list_pages — Page tree of a space (without content)
  • search_docs — Full-text (keyword) search across a workspace ¹
  • semantic_search — Natural-language search ranked by meaning — Pro workspaces ¹
  • get_page — Read a page (full Markdown + version); optional include_comments / include_children
  • create_page — Create a Markdown page (nestable)
  • update_page — Update title/content, with optional optimistic version check
  • append_to_page — Append Markdown — ideal for logs and session reports
  • import_markdown — Import a folder of Markdown files; paths become the page hierarchy. Idempotent — re-import reuses by source path (no duplicates); parent_page
  • delete_page — Delete a page (cascades to children)

What it needs from you

Configuration is passed through the environment: AGENTDOCS_TOKEN, AGENTDOCS_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Agentdocs.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Agentdocs's toolset — whoami, list_workspaces, list_spaces and 11 more — is a fair guide to whether it matches your workflow. It is maintained by hoornet; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
whoamiIdentify the user and credential scope
list_workspacesList accessible workspaces ¹
list_spacesList spaces in a workspace ¹
list_pagesPage tree of a space (without content)
search_docsFull-text (keyword) search across a workspace ¹
semantic_searchNatural-language search ranked by meaning — Pro workspaces ¹
get_pageRead a page (full Markdown + version); optional include_comments / include_children
create_pageCreate a Markdown page (nestable)
update_pageUpdate title/content, with optional optimistic version check
append_to_pageAppend Markdown — ideal for logs and session reports
import_markdownImport a folder of Markdown files; paths become the page hierarchy. **Idempotent** — re-import reuses by source path (no duplicates); parent_page anchor + overwrite_existing re-sync
delete_pageDelete a page (cascades to children)
bulk_create_pagesCreate up to 500 pages atomically with explicit structure
share_pageCreate a public magic link (web + raw-Markdown URLs)

How to install the Agentdocs MCP server

{
  "mcpServers": {
    "agentdocs": {
      "command": "npx",
      "args": ["-y", "agentdocs-mcp"],
      "env": {
        "AGENTDOCS_TOKEN": "your-value",
        "AGENTDOCS_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
AGENTDOCS_TOKENCredential the server authenticates with.Yes
AGENTDOCS_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Agentdocs to whoami.
  • Use Agentdocs to list workspaces.
  • Use Agentdocs to list spaces.

Frequently asked questions

It connects Agentdocs to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (whoami, list_workspaces, list_spaces, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agentdocs directly.