Claude MCP setup

Claude setup uses a Slab5 MCP endpoint and a workspace-scoped bearer token. Use your personal workspace endpoint while developing; use production only after the workflow is ready for real workspace data.

When to use Claude

Use Claude when the agent is doing business operations from a conversational workflow: lead capture, follow-up planning, CRM hygiene, account notes, or task creation.

Personal workspace configuration

Create an MCP token in your Slab5 personal workspace, then configure Slab5 as a remote MCP server:

{
  : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"mcpServers": {
    : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"slab5": {
      : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"url": : var(--shiki-token-string)">"https://mcp.slab5.com/v1/w/your-workspace-slug",
      : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"headers": {
        : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"Authorization": : var(--shiki-token-string)">"Bearer YOUR_SLAB5_WORKSPACE_MCP_TOKEN"
      }
    }
  }
}

For the first workflow, use:

crm:read
crm:write
tasks:write
activity:write

Hosted configuration

Use a dedicated workspace token for Claude instead of a personal API token. Keep the token in a local secret manager and configure only the workspace Claude should operate in.

{
  : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"mcpServers": {
    : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"slab5-prod": {
      : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"url": : var(--shiki-token-string)">"https://mcp.slab5.com/v1/w/your-workspace-slug",
      : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"headers": {
        : var(--shiki-token-string)">"color: var(--shiki-token-parameter)">: var(--shiki-token-string)">"Authorization": : var(--shiki-token-string)">"Bearer ${SLAB5_WORKSPACE_TOKEN}"
      }
    }
  }
}

Recommended production scopes for a CRM follow-up agent:

crm:read
crm:write
tasks:read
tasks:write
activity:read
activity:write

Use a narrower token for read-only research or reporting workflows:

crm:read
tasks:read
activity:read

Hosted OAuth

Add Slab5 as a connector using the workspace MCP server URL copied from the MCP Clients page, then complete the sign-in Claude prompts you for:

https://mcp.slab5.com/v1/w/your-workspace-slug

The URL must keep the /v1 base path and must name a workspace — a connector pointed at the bare /v1 address is refused, because an OAuth token identifies a person rather than a workspace and Slab5 will not guess which of their workspaces you meant.

This is also the same address a static token uses. There is no separate OAuth URL to look up.

Workspace owners and admins can add explicit OAuth workspace grants when Claude should receive narrower scopes than the signed-in user has in Slab5.

Connecting more than one workspace

Add one connector per workspace. Each is a distinct address, so Claude treats them as separate servers with separate sign-ins:

https://mcp.slab5.com/v1/w/acme
https://mcp.slab5.com/v1/w/acme-eu

Both connections can be signed in at once, and neither can see the other's data. If you have workspaces in both a personal account and an organization, that works too — the connector address decides which workspace you reach, not which account you happened to sign in through.

First prompt

Using Slab5, create a contact named Jane Doe at Acme Corp with email jane@acme.com. Use an idempotency key based on jane-doe-acme-demo. Create a follow-up task for next Friday and log that this came from a demo request.

Claude should call create_contact, create_task, and log_activity.

Verify

In Slab5, confirm:

• The contact exists in CRM.
• The task is open.
• The activity log includes the source note.
• Each write has an audit event and request ID.