Slab MCP integration for AI agents.
Connect AI agents to Slab through 17 structured actions, including get organization, add topic to post, and delete post. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 17
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Slab integration exposes
The Slab Agent App exposes 17 provider-backed actions for productivity work. Its current contract lets an authorized agent get the current slab organization visible to the api token, attach a slab topic to a post, and delete a slab post by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Slab account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Slab capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_organizationREADGet the current Slab organization visible to the API token.
add_topic_to_postWRITEAttach a Slab topic to a post.
INPUTS: postId / topicId
delete_postHIGH IMPACTDelete a Slab post by ID.
INPUTS: id
create_postWRITECreate a blank Slab post, optionally in a topic or from a template.
INPUTS: title / topicId / templateId
create_topicWRITECreate a Slab topic.
INPUTS: name / description / parentId / memberEditable / privacy
delete_topicHIGH IMPACTDelete a Slab topic by ID.
INPUTS: id
get_postREADGet one Slab post by ID.
INPUTS: id
get_postsREADGet multiple Slab posts by ID.
INPUTS: ids
get_topicREADGet one Slab topic by ID.
INPUTS: id
get_topicsREADGet multiple Slab topics by ID.
INPUTS: ids
get_userREADGet one Slab user by ID.
INPUTS: id
list_usersREADList users in the current Slab organization.
INPUTS: includeDeactivated
INPUT CONTRACTS
Know what the action needs before it runs.
add_topic_to_post
postIdOPTIONAL- A Slab GraphQL ID.
topicIdOPTIONAL- A Slab GraphQL ID.
delete_post
idOPTIONAL- A Slab GraphQL ID.
create_post
titleOPTIONAL- The new post title.
topicIdOPTIONAL- A Slab GraphQL ID.
templateIdOPTIONAL- A Slab GraphQL ID.
create_topic
nameREQUIRED- The topic name.
descriptionOPTIONAL- A JSON value returned by Slab.
parentIdOPTIONAL- A Slab GraphQL ID.
memberEditableOPTIONAL- The Slab topic member editability mode.
privacyOPTIONAL- The Slab topic privacy mode.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Organization
Get the current Slab organization visible to the API token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_organizationControl Add Topic To Post
Attach a Slab topic to a post. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_topic_to_postVerify with Get Post
Get one Slab post by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_postSAFETY BOUNDARY
Operate Slab with explicit limits
- Authorize Slab with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_post`, `delete_topic`, and `remove_topic_from_post` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Slab rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Slab task completed successfully.
CONNECTION MODEL
API key
Slab API token sent as an Authorization Bearer token. Copy the token from Team settings > Developer in Slab.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Slab.