MCP server · Documents and wikis

ReadMe MCP server

ReadMe in any MCP client, through Memtro: ReadMe does not publish this server. Memtro's ReadMe connector reads ReadMe 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

ReadMe developer docs: search the docs, list guide categories and their pages, read a guide page's text, and read the changelog. Can publish, edit or delete changelog entries and guide pages, and create or rename categories, when asked. Guides and categories need a ReadMe Refactored project.

Reads

  • readme_searchSearch the company's ReadMe docs (guides, API reference, changelog and custom pages): title, excerpt, section, version and the page link.
  • readme_list_categoriesThe categories of a docs section (guides by default) in sidebar order, for one version.
  • readme_category_pagesThe pages in one docs category (by its title from readme_list_categories), with slug, parent and last update.
  • readme_get_guideOne guide page by slug: title, state, visibility, its text (markdown or MDX, cut at max_chars), the docs link and last update.
  • readme_list_changelogsChangelog entries from the docs: title, type (added, fixed, improved, deprecated, removed), author, visibility, dates and an excerpt.

Acts, when you ask

These change something in ReadMe. 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.

  • readme_create_changelogPublishes a new changelog entry on the company's ReadMe docs site.
  • readme_update_changelogEdits an existing ReadMe changelog entry (by slug from readme_list_changelogs): title, text (replaces it), type or visibility.
  • readme_delete_changelogPermanently deletes one ReadMe changelog entry (by slug), removing it from the docs site for every reader.
  • readme_create_guideCreates a page in the Guides section of the company's ReadMe docs, in the category named (title from readme_list_categories).
  • readme_update_guideEdits an existing ReadMe guide page (by slug): title, text (replaces it), excerpt, category, state (current or deprecated) or visibility.
  • readme_delete_guidePermanently deletes one ReadMe guide page (by slug), removing it from the docs site for every reader.
  • readme_create_categoryCreates a new, empty category in the ReadMe docs sidebar (shown to docs readers once it has pages).
  • readme_update_categoryRenames a ReadMe docs category or moves it in the sidebar (position).

Connect it

First connect ReadMe on Dashboard → Connections, then add Memtro to your client once. The ReadMe 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 ReadMe 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

  • › What do our docs say about webhook retries?
  • › Which pages are in the Getting started category?
  • › What did we announce in the changelog this month?
  • › Show me the text of the authentication guide
  • › Post a changelog entry that the orders endpoint now returns tracking numbers

Questions

Is this an official ReadMe MCP server?
No. It is Memtro's MCP server with Memtro's ReadMe connector behind it: the connector reads ReadMe through its API with the credentials you connect on Dashboard → Connections, and ReadMe 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 ReadMe?
Only when you ask, and only what it has been granted: publish a changelog entry (public or link-only, as chosen); edit a changelog entry; delete a changelog entry (permanent); create a guide page in a category (public or link-only, as chosen); edit a guide page's title, text, category, state or visibility; delete a guide page (permanent); create a docs category; rename or move a docs category. 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.

Other MCP servers · Documents and wikis

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time