[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Slab API and MCP server: Let your AI agent keep your Slab wiki current.

> Slab has a GraphQL API on the Business and Enterprise plans only, no REST API and no official MCP server (checked 28 Oct 2026). On those plans the API searches, reads, creates and archives posts; we found no route for verification or Post Insights. Cotlet runs 10 Slab tools hosted on any plan, over MCP for agents and REST for scripts.

Search, read, create and verify posts in your Slab wiki. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

[MCP setup](https://cotlet.dev/integrations/slab-api-mcp-server.md#connect)
[REST API guide](https://cotlet.dev/integrations/slab-api-mcp-server.md#rest-api)

- Free 7-day trial, no card
- Unofficial, not affiliated with Slab
- Page: https://cotlet.dev/integrations/slab-api-mcp-server

## What can you automate in Slab?

- List posts with expired verification
- Re-verify posts you reviewed
- See views and readers of a post
- Answer questions from the wiki
- Turn meeting notes into a post
- Archive posts nobody reads

## Does Slab have an MCP server or an API?

- Slab's help center: "API & webhooks are only available to customers on the Business or Enterprise plan." Business is $12.50 a user a month billed yearly, $15 monthly. Free and Startup get no API.
- The token belongs to the Slab Bot user and has no scopes. "The content you receive from Slab's GraphQL Slab API depends on what the Slab Bot user has access to."
- Zapier and n8n have no Slab app. Pipedream wraps the GraphQL API in 10 actions, none for verification.

| What you need | GraphQL API | GitHub server | Cotlet |
|---|---|---|---|
| Works on Free and Startup | Business and Enterprise | Needs the API token | Yes, any plan |
| Search, read, create and archive posts | Yes, on Business | Yes, on Business | Yes |
| Expired posts, verify, request verification | Not found | No | Yes, after your OK |
| Post Insights: views and readers | Not found | No | Yes, where Slab shows them to you |
| Whose access it uses | The Slab Bot user | The Slab Bot user | Yours, with your role |
| Allowed by Slab's terms | Yes, official | Yes, official API | Uses the web app |

Checked 28 Oct 2026. Sources: [Slab Help: Developer Tools: API & Webhooks](https://help.slab.com/en/articles/6545629-developer-tools-api-webhooks), [Slab pricing](https://slab.com/pricing/), [Slab Help: Post verification](https://help.slab.com/en/articles/4136379-post-verification), [Slab Help: Advanced searching](https://help.slab.com/en/articles/3936161-advanced-searching), [Pipedream: Slab actions](https://pipedream.com/apps/slab)

## How does Cotlet connect to Slab?

1. **Sign in to Slab.** Use your own account in its Cotlet Cloud Browser.
2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key.
3. **Run your workflow.** Ask your agent or send an HTTP request.

We never keep your Slab password, and nothing your team gets notified about happens until you approve it.

## Connect Slab to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

1. **Sign in to Slab in a Cloud Browser.** Create a Cotlet account, open Slab in its Cloud Browser, sign in to your team's Slab as you always do and press Enable for agents.
2. **Add the Cotlet address.** Put https://cotlet.dev/mcp/v1 in the MCP server or connector field of your agent.
3. **Approve the connection.** Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts take an API key from the console.

The same address, `https://cotlet.dev/mcp/v1`, carries Slab and every other app you enable. If the Slab tools do not show after you enable it, refresh the connector in your agent.

Claude:

```
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-slab \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-slab": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet-slab]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: slab_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: slab_write
```

## How to use the Slab REST API

### Create your Cotlet API key

Create a Cotlet API key with access to Slab and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store.

Connect Slab in Cotlet and enable it for agents. Account access: Your own Slab account on any plan (what the agent can read and edit is what your role and topics allow).

### Make your first Slab API request

REST:

```
curl https://cotlet.dev/api/v1/slab/topics \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

### Read topics and apply the operation limits

A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

```
{
  "status": "success",
  "app": "slab",
  "tool": "list_topics",
  "result": {
    "topics": [
      {
        "topic_id": "t_support1",
        "name": "Support",
        "sub_topics": [
          "Macros",
          "Escalations"
        ]
      },
      {
        "topic_id": "t_eng0042",
        "name": "Engineering",
        "sub_topics": [
          "Runbooks"
        ]
      },
      {
        "topic_id": "t_meet007",
        "name": "Meetings",
        "sub_topics": []
      }
    ]
  }
}
```

Returns each topic you can open with its id, name and the sub-topics under it. Private topics appear only if you are a member.

Use the id or name as the topic parameter of other tools.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

### Slab workflows for agents and automations

| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Search the wiki with the same filters as Slab search. Use `search_posts` in your configured workspace report. |
| Make | HTTP > Make a request | Read one post as Markdown with its metadata. Use `get_post` in your configured workspace report. |
| Python or Node.js | REST API | Views and readers of one post over a period. Use `get_post_insights` in your configured workspace report. |

Send `Authorization: Bearer <your Cotlet API key>` in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Slab; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The [API and MCP reference](https://cotlet.dev/integrations/slab-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals.

## Slab API endpoints and MCP tools

### Search, posts and topics

Results stop where your role stops: private topics only if you are a member. New posts are drafts unless you say publish.

- **Search posts** (`search_posts`, read): Search the wiki with the same filters as Slab search.
- **List topics** (`list_topics`, read): Topics you can open, with their sub-topics.
- **Get post** (`get_post`, read): Read one post as Markdown with its metadata.
- **Create post** (`create_post`, write, asks first): Create a post from Markdown, as a draft or published.
- **Add post to topic** (`add_post_topic`, write): Add a post to a topic.

### Verification

Slab lets only people with edit access verify a published post, and a verifier cannot request verification of their own post.

- **List expired posts** (`list_expired_posts`, read): Posts whose verification has expired, optionally in one topic.
- **Verify post** (`verify_post`, write, asks first): Mark a published post as verified, with a review frequency.
- **Request verification** (`request_verification`, write, asks first): Ask the verifiers of a post to verify it.

### Insights and archiving

Slab keeps usage data 30 days on Free, 90 on Startup and 365 on Business, so insights reach back that far at most.

- **Get post insights** (`get_post_insights`, read): Views and readers of one post over a period.
- **Archive post** (`archive_post`, write, asks first): Archive a post so it leaves topics and default search.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/slab-api-mcp-server#tools

## Who can see my Slab session, and how do I revoke it?

- **What we store.** Your signed-in Slab profile, encrypted with AES-256-GCM, in Finland. No password.
- **What your agent gets.** The 10 Slab tools. No cookie and no Slab Bot token.
- **What the session sees.** The topics and posts your Slab role opens, drafts included.
- **What no tool touches.** Team settings, members, billing, SSO and the Developer page.
- **If Slab signs you out.** Your agent gets a link and you sign in again. We never sign in for you.
- **How to cut access.** Disable Slab for agents, reset the browser or delete the API key.

Your Slab admin can see how and when your account is used, as Slab's terms say, so agent work shows under your name. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)); no SOC 2 report or third-party pentest yet.

## Is it against Slab's terms? Account safety

> Use any robot, spider or other automatic device, process or means to access the Website or any mobile application used to access the Services for any purpose, including monitoring or copying any of the material on the Website
>
> [Slab Terms of Use, section 6, Prohibited Uses, updated 12 Oct 2023](https://slab.com/terms/)

Section 8 lets Slab end an account "for any or no reason". The GraphQL API is the only route the terms leave clear, and only on Business and Enterprise. An agent in the web app is automation in Slab's eyes, so a team that cares should ask Slab first. We found no public case of a Slab account closed for automation (checked 28 Oct 2026).

How we keep your account looking like you:

- Your own Slab login, signed in by you
- One Cloud Browser with its own IP and cookies
- Publishing, verifying, requests and archiving wait for your OK
- No tool deletes a post or changes team settings
- If Slab objects, we pause the Slab tools for everyone within 24 h

> Section 6 also bans use that could "overburden" the site. Run a big archive pass over a few days, not in one go.

## What happens when Slab changes?

- **12 h** between tests of the Slab reads and drafts
- **24 h** between tests of writes your team would notice
- **$0** for a call to a Slab tool paused for repair

When Slab moves the verification banner or renames a menu, we change the tool and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Lists expired posts.** Oldest expiry first, in the topic you named.
2. **Reads each post.** Checks it against your source and says what changed.
3. **Waits for your OK.** Each verify shows up in your Cotlet console.
4. **Reports back.** Verified, left expired, and new expiry dates.

| Action | Undo |
|---|---|
| Create a draft | Delete it; nobody saw it |
| Publish a post | Archive it; topic followers were already notified |
| Add a post to a topic | Yes, remove the topic |
| Verify a post | Change verification on the post in Slab |
| Request verification | No, the verifier is notified |
| Archive a post | Yes, the archived filter finds it again |

4 of 10 tools ask first: create_post, verify_post, request_verification and archive_post. Reads and add_post_topic run at once. Turn the wait off per tool for a scheduled run.

> Verify only what you checked: the green banner tells your team the post is right, with your name on it.

MCP call:

```
{
  "name": "create_post",
  "arguments": {
    "title": "Weekly sync notes",
    "body": "## Decisions\n- Ship the billing fix Thursday\n\n## Actions\n- Ana: update the runbook",
    "topic": "Meetings",
    "publish": false
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/slab/posts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Weekly sync notes","body":"## Decisions\n- Ship the billing fix Thursday\n\n## Actions\n- Ana: update the runbook","topic":"Meetings","publish":false}'
```

Response:

```
{
  "post_id": "m5q1y8tc",
  "title": "Weekly sync notes",
  "state": "draft",
  "topics": [
    "Meetings"
  ],
  "url": "https://yourteam.slab.com/posts/weekly-sync-notes-m5q1y8tc"
}
```

Cron jobs and scripts call the same tools over REST at `/api/v1/slab`, with one key and one price. A verify on a post you cannot edit fails with a permission error and costs nothing. The tools table lists the REST path of each tool.

## How much does the Slab MCP server cost?

**About $27 a month** for a Slab team of about 40 people, 4,700 credits. Slab bills your seats as before.

| Job | Calls | Credits |
|---|---|---|
| Expired posts report with views, weekly | 13 × 4 | 520 |
| Re-verify 6 reviewed posts, weekly | 13 × 4 | 520 |
| Answer 4 questions from the wiki, each workday | 2 × 88 | 1,760 |
| Meeting notes saved as drafts | 3 × 8 | 240 |
| Archive unread expired posts, monthly | 16 × 1 | 160 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 4,700 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Business plan needed in Slab

The month is our example. Slab's average contract is about $3K a year (Getlatka, Oct 2024), some 20 to 40 seats. Moving that team from Startup to Business for the API alone would add $5.83 a seat a month. Dollars at the $29 pack rate.

## Slab MCP server on GitHub, Pipedream or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| [russwyte/slabby](https://github.com/russwyte/slabby) | The most starred Slab MCP server (18 stars), Bun, 4 tools: get, update, search and list posts. Apache-2.0. | Slab Bot token, last commit 12 Mar 2026, nothing for verification. |
| [DeNoronha/slab-knowledge-mcp](https://github.com/DeNoronha/slab-knowledge-mcp) | 16 tools: upsert posts from Markdown, archive, topics, users, comments. | Edits only posts it created; Slab's API cannot edit posts made in the editor. |
| [mostafa/slab-cli](https://github.com/mostafa/slab-cli) | Rust CLI: pull the wiki as Markdown, diff and push back, comments. | A CLI on your machine, not a hosted server. |
| [Pipedream](https://pipedream.com/apps/slab) | Hosted MCP on 10 GraphQL actions. | API plans only, no verification or insights. |
| [Dust](https://docs.dust.tt/docs/user-documentation/agents/tools/slab), Even | Slab search and reading inside their own agent apps. | Read-heavy, inside one product, on the Bot token. |

On Business or Enterprise, a GitHub server or Pipedream covers search, reading and new posts, and you look after the token. None of them sees expired posts, verifies or reads Post Insights, and none works on Free or Startup. Cotlet does that upkeep in your own login.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet, a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Slab tools go to contact@cotlet.dev.

## Slab API and MCP: questions

### How do I get access?

Create a free account at https://cotlet.dev, open Slab under Integrations in the console and sign in to Slab in its Cloud Browser. The trial starts with your first app, and no card is asked.

### How do I connect Slab to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Slab once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Slab account through Cotlet, in their phone apps too.

### What can ChatGPT do in Slab?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Slab: weekly report of outdated wiki posts; re-verify posts you reviewed; answer questions from the wiki. You ask in plain words, and anything that reaches other people waits for your OK first.

### Do I need a Slab Business plan?

No. Slab's own GraphQL API needs Business or Enterprise, but Cotlet works in your signed-in Slab account on any plan. What the agent can do still follows your role: only people with edit access to a post can verify or archive it (Slab Help: Post verification).

### Can my agent see private topics and drafts?

It sees what your own account sees. Private topics, a feature of Startup and higher plans, show up only if you are a member (Slab pricing). Nothing is shared with a bot user.

### Does Slab have webhooks?

Only on Business and Enterprise, and they fire when a post is published. Nothing tells an agent that a verification expired, so run it on a schedule, for example a weekly list_expired_posts.

### Can the agent rewrite an existing post?

No. No tool edits the body of a post; the agent creates new posts and drafts, sets topics, verifies and archives. Rewrites stay with your team in the Slab editor.

### Is the MCP server different from the REST API?

Only the way in differs. Both carry the same 10 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

### Is Cotlet affiliated with Slab?

No. Cotlet is independent and not affiliated with Slab Inc.

### Can I use the Slab API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
