Skip to content

MCP Server (direct access)

SMBcrm runs a Model Context Protocol (MCP) server, so an AI agent — Claude, Cursor, a custom agent, or an automation tool like n8n — can read and act on your account through one connection. The tools map to the same resources as the REST API, and your token’s scopes decide what an agent can do.

URL https://services.smbcrm.com/mcp/
Transport Streamable HTTP
Auth Authorization: Bearer <pit-token> (a Private Integration Token)
Account/location Provide your <location_id> (see below)

Authenticate with a Private Integration Token. It’s built for server-to-server use and is already scoped to your account/location, which makes it the most reliable way to connect an agent.

MCP tools act on one SMBcrm account/location. Provide your <location_id> in whichever way your client supports:

  • as a header on the connection, for example locationId: <location_id>, or
  • in the agent’s prompt or tool arguments when it calls a tool.

If your token is already bound to one account/location, some tools can infer it, but passing it explicitly is the most reliable.

Most MCP clients take an HTTP server URL plus headers. The config shape varies by client; the values are always the same — the URL, your bearer token, and your location id.

{
"mcpServers": {
"smbcrm": {
"type": "http",
"url": "https://services.smbcrm.com/mcp/",
"headers": {
"Authorization": "Bearer <pit-token>",
"locationId": "<location_id>"
}
}
}
}

An MCP tool call succeeds only if your token carries the matching REST scope. To let an agent create contacts, the token needs contacts.write; to read the calendar, calendars/events.readonly. Grant the smallest set of scopes for what the agent should do, and issue a separate token per agent so you can revoke one without affecting the others.