4,500+ servers built on MCP Fusion
Vinkius

Slab MCP. Manage your entire knowledge base from chat.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Slab MCP on Cursor AI Code Editor MCP Client Slab MCP on Claude Desktop App MCP Integration Slab MCP on OpenAI Agents SDK MCP Compatible Slab MCP on Visual Studio Code MCP Extension Client Slab MCP on GitHub Copilot AI Agent MCP Integration Slab MCP on Google Gemini AI MCP Integration Slab MCP on Lovable AI Development MCP Client Slab MCP on Mistral AI Agents MCP Compatible Slab MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Slab MCP Server connects your AI agent directly to your company wiki. Use it to search internal documentation, draft new articles in Markdown, or update existing posts—all without leaving your chat window.

It gives agents full read and write access across all topics, making your team's knowledge base actionable.

What your AI agents can do

Archive post

Removes an existing Slab post. Note: this action is irreversible via API.

Create post

Creates a brand new wiki article in Slab using Markdown content provided by the user.

Create topic

Establishes a new organizational container (folder) within Slab to group related posts.

+ 9 more capabilities included
Search and retrieve specific articles

The agent performs full-text searches across all posts in your Slab workspace, returning relevant snippets.

Create new documentation topics

You tell the agent to create a new organizational topic (folder) to group related wiki articles.

Write and publish new posts

The agent creates an entirely new post within Slab using Markdown content you provide.

Modify existing documentation

You ask the agent to update either the title or the body content of a specific, pre-existing wiki article.

Get structured topic details

The agent pulls metadata and lists all contained posts for a specific organizational topic.

List all users in the organization

The system retrieves a list of all registered team members associated with your Slab workspace.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Slab MCP Server: 12 Tools for Knowledge Management

These tools let your agent interact with the full Slab API to read, write, search, archive, or list every piece of documentation in your organization.

archive019d7609

archive post

Removes an existing Slab post. Note: this action is irreversible via API.

create019d7609

create post

Creates a brand new wiki article in Slab using Markdown content provided by the user.

create019d7609

create topic

Establishes a new organizational container (folder) within Slab to group related posts.

get019d7609

get organization

Retrieves the core profile and metadata for your entire Slab organization workspace.

get019d7609

get post details

Fetches the full, complete content and all metadata for one specific Slab post ID.

get019d7609

get topic details

Retrieves details about a topic, including a list of all posts contained within that organized folder.

list019d7609

list posts

Lists the IDs and titles of every single wiki article in your Slab workspace.

list019d7609

list recent posts

Returns a list of posts that have been updated most recently across the entire organization.

list019d7609

list topics

Lists all available topics (folders) currently organizing content in Slab.

list019d7609

list users

Retrieves a list of every user account registered within the Slab organization.

search019d7609

search posts

Runs a full-text search across all content in Slab, matching keywords against post titles and bodies.

update019d7609

update post

Changes the title or body content of an existing Slab article using its unique ID.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Slab, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

You connect your AI agent straight into your Slab workspace. This isn't just a read-only connection; you give your agent full write access, letting it search, draft, update, and organize documentation across your entire company knowledge base without you ever having to switch apps or copy/paste anything.

What Your Agent Can Do

When you need an answer fast, your agent runs a full-text search against every single article in Slab. You just drop keywords—say, 'Q3 budget approval process'—and the agent pulls back relevant snippets and post IDs from anywhere in the system so you can get answers immediately.

You gotta build out or fix docs sometimes. The agent handles that too. If you need to write a brand new wiki article, it uses create_post; you just give it the Markdown content, and boom—a new post is live in Slab. Need to revise something? You tell it which post ID to hit, and it runs update_post, changing either the title or the body content of that existing article right away.

For structure, your agent manages topics. If a bunch of posts are related—say, all things 'HR Onboarding'—the agent can create an organizing container using create_topic. You don't wanna lose track of stuff, so it also runs list_topics to show you what folders you already got set up. When you need to know the full scope of one folder, the agent uses get_topic_details; this pulls all the metadata for that topic and lists every single post tucked inside it.

Keeping track of everything is key. The agent can list every article ID and its title across your workspace with list_posts. If you just want to know what got changed lately, it hits list_recent_posts for a rundown of the most recently updated documentation so you don't miss a policy change.

When you need specific info on one article, the agent uses get_post_details. You give it a post ID, and it retrieves the full, complete content and all the metadata attached to that single Slab entry. If you wanna see what your whole company setup looks like, the agent pulls the core profile and metadata for your entire organization using get_organization.

For personnel info, the system can run list_users, giving you a complete roster of every registered team member in your Slab workspace. If you need to clean up old content or retire an article, the agent runs archive_post, which permanently removes an existing post from Slab; just remember that action's irreversible through the API.

Basically, it covers the whole lifecycle: finding what exists using search_posts and list_posts, building out structure with create_topic and get_topic_details, writing new stuff with create_post and updating old docs with update_post, pulling user lists via list_users, or just getting the full scoop on a single post using get_post_details. It’s your whole knowledge base, fully accessible through your chat window.

How Slab MCP Works

  1. 1 Subscribe to this server and provide your Slab Access Token.
  2. 2 Instruct your AI client (e.g., 'Search the wiki for X' or 'Create a post about Y').
  3. 3 The agent executes the appropriate tool call, retrieving the requested data or committing the new content back into Slab.

The bottom line is that your agent acts as an extension of the Slab API, letting you manage documentation without ever leaving your chat client.

Who Is Slab MCP For?

Anyone who gets annoyed by context switching. If you're a developer constantly jumping between IDEs and Confluence, or a PM clicking through five different tabs to find one spec sheet—this is for you. It hands your AI agent the keys to your company brain.

Product Manager

Drafting feature specs or release notes and publishing them directly to the correct Slab topic.

Software Developer

Pulling API documentation details into the chat while coding, then using those details for reference in their IDE.

Technical Writer/Editor

Creating new articles or modifying old meeting notes and ensuring they land in the right place without manual steps.

What Changes When You Connect

  • Search Deeply: Skip the keyword guessing games. Use search_posts to run full-text queries across all documentation, giving you instant answers without manually checking every folder.
  • Build Structure Fast: Need a new section for 'Q4 Planning'? Use create_topic first, then funnel related notes into it using create_post. You build your wiki structure in the chat, not through clicks.
  • Keep Everything Fresh: The list_recent_posts tool keeps you current. Instead of digging through archives, you see exactly what broke or changed 10 minutes ago.
  • Write and Edit on the Fly: Don't draft notes elsewhere. Use create_post or update_post to write meeting summaries or spec changes directly into Slab, maintaining version control and context.
  • Know Who You're Talking To: The list_users tool instantly pulls organization metadata, letting you get names and roles without having to navigate the directory tree.

Real-World Use Cases

01

Finding a specific API protocol

A developer needs the 'v3 rate limit' details. Instead of knowing which topic that lives in, they ask their agent: 'Search Slab for v3 rate limits.' The agent runs search_posts and returns the exact post title and snippet instantly.

02

Onboarding a new hire

An HR manager needs to gather all policies related to remote work. They ask their agent: 'List all topics tagged with policy.' The agent runs list_topics and provides the structure, which the manager can then use to guide the new employee.

03

Updating a broken process document

The engineering lead finds an old post about deployment that needs fixing. They ask their agent: 'Update the post ID p-1234 with the new steps.' The agent uses update_post to commit the fix immediately.

04

Creating a whole new knowledge area

The PM realizes they need a dedicated section for product feedback. They ask their agent: 'Create a topic called Product Feedback.' The agent runs create_topic, giving them the ID to start funneling future notes.

The Tradeoffs

Manually listing everything

Trying to figure out if an article exists by running list_posts and scrolling through hundreds of results. You miss the one you need.

Use search_posts. It runs a targeted, full-text search across every post, returning only what matches your query.

Drafting notes outside Slab

Writing meeting minutes in Notion and then having to copy/paste them into the correct wiki article. Data gets lost or outdated.

Use create_post or update_post. Draft your content with your agent, and let it commit directly into Slab.

When It Fits, When It Doesn't

Use this server if your primary pain point is context switching when working with company documentation. If you need to read, write, search, or map out a wiki structure without leaving the chat window, this is for you. You're doing knowledge work; let the agent handle the API calls.

Don't use this server if your goal is simply to view a few posts in a read-only capacity. In that case, standard client viewing might be enough. Also, don't rely on it for complex user permission management—it handles content flow, not role assignments. If you need to manage who can see what, look into dedicated Identity Access Management (IAM) systems instead.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Slab. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 12 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

archive_post create_post create_topic get_organization get_post_details get_topic_details list_posts list_recent_posts list_topics list_users search_posts update_post

Finding the right document shouldn't feel like detective work.

Right now, finding a specific protocol or guideline means opening Slab, navigating to the correct top-level topic, then drilling down through subfolders until you find the exact post ID. If that folder is moved or renamed, you're stuck clicking and guessing.

With this MCP server, your agent runs `search_posts`. You just ask it what you need—say, 'What are the rules for client data retention?'—and it pulls the answer directly from the content across the whole wiki. No clicks. Just answers.

Slab MCP Server: Control your documentation flow.

Manual updates involve remembering which post ID is correct, fetching the old content into a local editor, making changes, and then manually committing them back. This process breaks workflow instantly.

Now, use `update_post`. You tell your agent to change the title or body of a specific article ID. The whole cycle—read, modify, commit—happens in one command. It's reliable.

Common Questions About Slab MCP

Can I find any documentation using search_posts? +

Yes. search_posts performs a full-text search across all posts, titles, and bodies in Slab. This is how you pull answers when you don't know the exact post ID.

How do I create new documentation with create_post? +

You provide the content in Markdown format to create_post. The agent handles the API call and publishes it as a brand-new wiki article within Slab.

What is the difference between list_topics and get_topic_details? +

list_topics just gives you a names/IDs of all available folders. get_topic_details digs deeper, giving you metadata and listing every post inside that specific topic.

Can I list the users with list_users? +

Yes. The list_users tool retrieves all registered team members and their organizational metadata from Slab for reference.

What is the difference between running `list_posts` and calling `get_post_details`? +

list_posts returns only post IDs and titles for quick browsing. You must use get_post_details when you need the full content, metadata, or specific article body.

When I run `create_topic`, what information do I get back? +

It returns a unique Topic ID and the name of your new topic. You must save this ID immediately; it's required when you want to save posts or articles to that specific container.

How do I change content on an existing article using `update_post`? +

You run update_post, providing the post ID and the new Markdown content. This tool modifies text; you cannot use it to create a brand-new document.

What happens when I use the irreversible `archive_post` tool? +

It removes an existing Slab post from active view immediately. Because this action is permanent, always verify the content and intended deletion before running the command.

Can my AI use existing wiki guidelines to write new code or copy? +

Absolutely. You can request your agent to 'search the Slab wiki for our Frontend Coding Standards' or 'find our Brand Voice Guidelines'. The agent will retrieve the exact Markdown content of those articles and use them as system instructions for the rest of your conversation.

How do I easily publish my AI chat output back to Slab? +

When your AI agent generates a good technical specification or summary, simply tell it: 'Create a new post in Slab called [Name], using this entire response as the content, and place it in the Engineering topic.' The agent will format the Markdown and publish it immediately through the create_post tool.

Can my agent clean up outdated company documentation? +

Yes. If an article is deprecated, you can tell your AI: 'Archive the post with ID XYZ' or 'Find the old setup guide and archive it.' The agent can execute the archive_post command to hide outdated information and keep your knowledge base pristine.

You might also like

Built & Managed by Vinkius 30s setup 12 tools

We've already built the connector for Slab. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.