Cursor MCP setup

Cursor can connect to Slab5 through the same remote MCP configuration used by other MCP-capable clients.

When to use Cursor

Use Cursor when a developer wants an agent to create test CRM data, inspect tool schemas, validate API behavior, or drive operational examples while building against Slab5.

Configuration

Configure Slab5 as a personal workspace remote MCP server:

Cursor 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"
      }
    }
  }
}

Use a token created from the personal workspace while developing. Avoid using production workspace tokens from an editor unless the workflow intentionally operates on production data.

Project config

For a repo-specific setup, add a project-level MCP configuration and keep the token out of source control:

Project 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-sandbox": {
      : 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_SANDBOX_TOKEN}"
      }
    }
  }
}

Recommended .env.local shape:

.env.localbash

SLAB5_SANDBOX_TOKEN=slab5_workspace_token_with_sandbox_scopes
SLAB5_MCP_URL=https://mcp.slab5.com/v1

Recommended editor scopes for implementation and docs testing:

Editor scopes

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

Developer workflow

Ask Cursor:

Schema prompt

List the available Slab5 tools and show me the required input schema for create_contact and create_task.

Then test the first write:

Write prompt

Create a sandbox contact for Jane Doe at Acme Corp and create a follow-up task for next Friday.

Guardrails

Use personal workspace tokens for development.
Use the MCP endpoint shown in the workspace by default.
Prefer idempotency keys in write examples.
Keep settings:admin off editor tokens unless the workflow specifically requires settings access.
Use request IDs to compare MCP behavior with REST API docs.