MCP server · Documents and wikis

Slab MCP server

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

Slab knowledge base: full-text search of posts and topics, a post's text with its owner, topics and dates, the list of posts and topics. Can create a blank, titled draft post, publish or unpublish, archive, share by link, file under or remove from a topic, or delete a post, and create, change or delete a topic.

Reads

  • slab_searchFull-text search of Slab posts (and optionally topics): each hit's id, title, the matching passage, and when the post was updated.
  • slab_get_postOne Slab post by id: title, owner, topics, created, updated and published dates, version, and its text (long posts are cut).
  • slab_list_postsSlab posts the token can see, by title: id, title, published and archived dates and topic ids.
  • slab_list_topicsSlab topics (the folders posts are organised in) the token can see: id and name.
  • slab_get_topicOne Slab topic: name, description, privacy, parent and child topics, and its posts with when each was updated (up to 100).

Acts, when you ask

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

  • slab_create_postCreates a new, blank Slab post with a title, optionally in a topic, for somebody to write in Slab.
  • slab_publish_postPublishes a Slab post (published true), which makes it visible to everyone in the organisation who can see its topics…
  • slab_archive_postArchives a Slab post (archived true), taking it out of the active knowledge base, or unarchives it (archived false).
  • slab_set_post_link_accessChanges who can open a Slab post by its link: INTERNAL (the organisation can view and edit), INTERNAL_VIEW (the organisation can view), PUBLIC…
  • slab_add_topic_to_postFiles a Slab post under a topic (a post can be in several), so the topic's members see it there.
  • slab_remove_topic_from_postTakes a Slab post out of one topic; the post itself is kept.
  • slab_delete_postDeletes a Slab post for everyone.
  • slab_create_topicCreates a Slab topic (a folder for posts), at the top level or under a parent topic, with the privacy given: OPEN…
  • slab_update_topicChanges a Slab topic: its name, parent (moves it), who may edit, whether it inherits its parent's members, or its privacy (OPEN, PRIVATE, SECRET…
  • slab_delete_topicDeletes a Slab topic for everyone.

Connect it

First connect Slab on Dashboard → Connections, then add Memtro to your client once. The Slab 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 Slab 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 does our handbook say about working abroad?
  • › Who owns the incident review post, and when was it updated?
  • › Which posts are in the Engineering topic?
  • › Is there a post about the expenses policy?
  • › Publish the Acme onboarding plan draft and file it under Clients

Questions

Is this an official Slab MCP server?
No. It is Memtro's MCP server with Memtro's Slab connector behind it: the connector reads Slab through its API with the credentials you connect on Dashboard → Connections, and Slab 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 Slab?
Only when you ask, and only what it has been granted: create a blank draft post with a title, optionally in a topic; publish a draft post to the organisation, or unpublish it; archive or unarchive a post; change who can open a post by link, including a public link; file a post under a topic; take a post out of a topic; delete a post; create a topic, optionally under a parent, with a privacy level; rename, move or change the privacy of a topic; delete a topic. 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