Document360 MCP server
Document360 in any MCP client, through Memtro: Document360 does not publish this server. Memtro's Document360 connector reads Document360 through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Document360 knowledge base: workspaces, the category tree, articles with their status (draft, published, unpublished), an article's content on request, labels and workflow statuses; can create a draft article or a category, edit, publish, unpublish, archive or delete an article, set its labels and move it through the review workflow.
Reads
document360_workspacesWorkspaces (what older Document360 called project versions) in the knowledge base: id, name, slug and which is the default.document360_categoriesThe category tree of a workspace, flattened with a depth per category.document360_articlesArticles in a workspace (metadata, no content): title, status (draft, published, unpublished), category, versions, last modified.document360_articleOne article: title, status, versions, URL and, when include_content is set, its content (Markdown or HTML as written) cut to max_chars.document360_usersTeam accounts on the project, by name and portal role, with the user_id document360_create_draft_article needs as the author.document360_labelsLabels defined on the project (id, name, description), for document360_set_article_labels.document360_workflow_statusesThe review workflow's statuses (id, name, whether articles in it are read-only, whether moving there needs a comment)…
Acts, when you ask
These change something in Document360. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
document360_create_draft_articleCreates a new draft article in a Document360 category.document360_update_articleEdits a Document360 article's title, content, category (a move), position or hidden flag.document360_publish_articlePublishes a version of a Document360 article, so everybody who can read the knowledge base site (often the public) sees it…document360_unpublish_articleUnpublishes a Document360 article, so readers of the knowledge base site no longer see it; the content is kept as a draft.document360_create_categoryCreates a category (a folder, a page or an index) in a Document360 workspace.document360_set_article_labelsSets the labels on a Document360 article.document360_update_article_workflow_statusMoves a Document360 article to another review-workflow status, and can set its assignees and a due date.document360_archive_articleArchives one language version of a Document360 article: it leaves the knowledge base site and search and becomes read-only until somebody restores it…document360_delete_articlePermanently deletes a Document360 article and all its versions and languages.
Connect it
First connect Document360 on Dashboard → Connections, then add Memtro to your client once. The Document360 tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Document360 connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which help articles are still drafts in Getting started?
- › What does our published article on single sign-on say?
- › Which articles in the Billing category changed most recently?
- › Draft an article in Troubleshooting called Resetting your password, with Priya as author.
- › Publish the latest draft of the export errors article.
Questions
- Is this an official Document360 MCP server?
- No. It is Memtro's MCP server with Memtro's Document360 connector behind it: the connector reads Document360 through its API with the credentials you connect on Dashboard → Connections, and Document360 publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Document360?
- Only when you ask, and only what it has been granted: create a draft article in a category (unpublished until someone publishes it in Document360); edit an article's title, content, category, order or hidden flag (content edits go to a new draft); publish an article version so readers of the knowledge base see it; unpublish an article so readers no longer see it; create a category in a workspace; replace the set of labels on an article; move an article to another workflow status and assign reviewers (assignees are notified); archive one language version of an article (read-only and off the site until restored); delete an article and all its versions (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.