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:

Claude MCP configjson

{
  : 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",
      : 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:

Quickstart scopes

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.

Production configjson

{
  : 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",
      : 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:

Production scopes

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

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

Read-only scopes

crm:read
tasks:read
activity:read

Hosted OAuth

For OAuth-capable Claude setups, use the workspace-scoped MCP server URL copied from the MCP Clients page:

Claude OAuth MCP URL

https://mcp.slab5.com/v1?workspace_id=wrk_...

The URL must keep the /v1 base path. Workspace owners and admins can add explicit OAuth workspace grants when Claude should receive narrower scopes than the signed-in user has in Slab5.

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.