russwyte/slabby
If you are the rightful owner of slabby and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
Slabby is an MCP server designed to integrate Slab knowledge bases with AI coding agents, enabling seamless interaction with documentation.
🧱 Slabby
MCP server for Slab knowledge base integration with AI coding agents
Slabby is a Model Context Protocol server that enables AI coding agents like Claude Code, Cline, and others to read and update your Slab documentation directly. Perfect for keeping RFCs, technical docs, and team wikis in sync with your development workflow.
Features
- 📖 Read Slab posts - Fetch post content by ID or URL
- ✏️ Update Slab posts - Edit posts with changes attributed to you
- 🔍 Search Slab - Find posts across your workspace
- 📋 List posts - Browse posts by topic or tag
- 🔐 Secure authentication - Uses your personal Slab API token
Installation
For Development
git clone https://github.com/russwyte/slabby.git
cd slabby
bun install
From npm
npm install -g @russwyte/slabby
# or
bun install -g @russwyte/slabby
Configuration
1. Get your Slab API token
- Go to your Slab workspace → Settings → API
- Generate a new API token
- Copy the token (you'll need it in the next step)
2. Set up environment variables
Create a .env file in the project root:
SLAB_API_TOKEN=your-api-token-here
SLAB_TEAM=your-team-domain # e.g., "acme" for acme.slab.com
Security Note: Never commit your .env file to git. It's already in .gitignore.
3. Configure Claude Code
Add Slabby to your Claude Code MCP settings:
macOS/Linux: ~/.config/claude-code/claude_desktop_config.json
Windows: %APPDATA%\claude-code\claude_desktop_config.json
{
"mcpServers": {
"slabby": {
"command": "bun",
"args": ["run", "/absolute/path/to/slabby/index.ts"],
"env": {
"SLAB_API_TOKEN": "your-token-here",
"SLAB_TEAM": "your-team-domain"
}
}
}
}
Tip: You can also use environment variables instead of hardcoding the token:
{
"mcpServers": {
"slabby": {
"command": "bun",
"args": ["run", "/absolute/path/to/slabby/index.ts"],
"env": {
"SLAB_API_TOKEN": "${SLAB_API_TOKEN}",
"SLAB_TEAM": "${SLAB_TEAM}"
}
}
}
}
Usage
Once configured, Claude Code will automatically have access to these tools:
slab__get_post
Fetch a Slab post by ID or URL:
Claude, read the Atlas RFC from https://myteam.slab.com/posts/atlas-rfc-xyz123
slab__update_post
Update a Slab post:
Claude, update the Atlas RFC to reflect the single goal change
slab__search
Search across your Slab workspace:
Claude, search Slab for all documents about "marketing automation"
slab__list_posts
List posts in a topic:
Claude, show me all RFCs in the Engineering topic
Development
Run in development mode (with auto-reload):
bun run dev
Run in production mode:
bun run start
Test the MCP server:
# Using the MCP inspector (install separately)
npx @modelcontextprotocol/inspector bun run index.ts
How It Works
Slabby implements the Model Context Protocol, which allows AI assistants like Claude to interact with external tools and services. When you ask Claude Code to read or update Slab content, it:
- Uses your Slab API token to authenticate (format:
Authorization: token YOUR_TOKEN) - Makes requests to the Slab GraphQL API at
https://api.slab.com/v1/graphql - Returns results to Claude Code
- All edits are attributed to your user account in Slab
Security
- API tokens are stored locally - Never sent to Anthropic's servers
- Edits show as you - All changes attributed to your Slab account
- Read-only by default - Update operations require explicit permission
- Environment-based config - Tokens stored in
.env(gitignored)
Slab API Reference
This project uses the Slab GraphQL API. The GraphQL schema is documented at: https://studio.apollographql.com/public/Slab/variant/current/schema/reference
Key operations:
query GetPost- Fetch post content by IDmutation UpdatePost- Update post contentquery SearchPosts- Search posts across workspacequery ListPosts- List posts, optionally filtered by topic
⚠️ Important: The GraphQL queries in this project are based on common GraphQL patterns and need to be verified against the actual Slab schema before use with production credentials. See for a detailed verification checklist.
Troubleshooting
"Authentication failed" error
- Check that your
SLAB_API_TOKENis correct - Verify the token has appropriate permissions in Slab settings
"Team not found" error
- Ensure
SLAB_TEAMmatches your Slab subdomain (e.g., "acme" for acme.slab.com)
Claude Code doesn't see the tools
- Restart Claude Code after updating MCP config
- Check that the absolute path to
index.tsis correct - Verify bun is in your PATH
Contributing
Contributions welcome! Please feel free to submit issues, fork the repository, and send pull requests.
When contributing, please:
- Add tests for any new functionality
- Ensure all tests pass with
bun test - Follow the existing code style
- Update documentation as needed
License
Copyright 2025 Russ White
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this project except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
See the file for the full license text.
Related Projects
- Model Context Protocol - MCP specification
- Claude Code - AI-powered development environment
- Slab API - Official Slab API documentation