MCP for agents

SolutionDesk exposes a staff-facing MCP server (Model Context Protocol). Agents act with your staff identity — same tenant isolation and visibility rules as the dashboard.

You configure this under Account (not Settings): connect clients and review authorized apps.

Where it lives

1. Open the workspace switcher / user menu → Account (or go to /{workspace}/account).
2. Connected apps — MCP clients you already authorized (revoke anytime).
3. Connect an MCP client — install commands for Claude Code, Cursor, Codex, and Grok Build.

The server URL is always:

https://<your-api-host>/v1/mcp

Example (local portless): https://api.solutiondesk.localhost/v1/mcp
Example (dev cloud): https://api.dev.solutiondesk.io/v1/mcp

Connect a client

Claude Code

claude mcp add --transport http solutiondesk https://<api-host>/v1/mcp

Then in Claude run /mcp, sign in, and approve access.

Cursor

Merge into ~/.cursor/mcp.json (or project .cursor/mcp.json):

{
  "mcpServers": {
    "solutiondesk": {
      "url": "https://<api-host>/v1/mcp"
    }
  }
}

Reload MCP in Cursor settings.

Codex

codex mcp add solutiondesk --url https://<api-host>/v1/mcp
codex mcp login solutiondesk

Login opens a browser to authorize with your SolutionDesk account.

Grok Build

grok mcp add --transport http solutiondesk https://<api-host>/v1/mcp

Authorize from /mcps if the client does not open a browser automatically.

What agents can do

Tools take a workspace slug (from list_workspaces) on every call.

Reads

Writes

Writes show up live on the dashboard the same way UI mutations do.

Boards

Ticket, settings, status, label and group tools take an optional board (its name in the address, e.g. development). Without one they act on the customer board (“Support”) — list_tickets too, so ask for a board to see its tickets. list_boards shows the boards; owners and admins can create, rename and archive boards (create_board, update_board, archive_board). move_ticket_to_board moves a ticket with its subtasks: run it with dryRun first to see how values carry over, and confirm explicitly when customers gain or lose access — see Boards.

CRM

While the CRM is switched on, agents get the CRM too. All of it is staff-only: nothing an agent writes here reaches customers, except the tickets it deliberately creates from a meeting.

A typical use: hand an agent a meeting transcript, let it record notes, decisions and next steps with create_crm_meeting, then review the steps in the dashboard before turning them into tickets.

While the CRM is off, the CRM tools answer that the module isn't enabled.

Events

Agents can run events the way the team does in the dashboard: plan an event and its programme, publish it, answer registrations and send invitations.

Cancelling an event doesn't mail the people who registered — tell them yourself. While the events module is off, every tool except the settings ones answers that events aren't enabled.

Newsletter

Agents can work on the newsletter the way the team does in the dashboard: write campaigns, look after lists and subscribers, and — if their role allows it — send.

Roles work exactly as in the dashboard. The Agent role only drafts: it may create and edit campaigns and upload images, but never sends, deletes a campaign or adds people to a list. Members may also send, delete drafts, add and edit subscribers and block addresses; lists, settings, lifting a block and erasing a subscriber are for owners and admins. While the newsletter is off, every tool except the settings ones answers that it isn't turned on. The newsletter mail account, importing and exporting subscribers, and the data export for an access request stay in the app.

Member invites, host API keys, SMTP passwords, and logo/avatar uploads stay in the app (session cookies, secrets, or binary uploads).

Golden rules for agents (and humans who prompt them)

1. Never leak internal notes. list_comments returns both public replies and internal: true notes. Only quote internal content in another add_comment that is also internal.
2. Tenant isolation. Every tool is scoped to workspaces you belong to — no cross-tenant shortcuts.
3. Visibility. Prefer internal tickets until you intentionally share with the customer company.

Revoke access

On Account → Connected apps, revoke a client. That drops its OAuth grant; the agent must re-authorize to work again.

Related

• Settings → API keys — host SaaS server-to-server (not the same as MCP)
• Staff vs portal end-user