Documentation sections

Hosted MCP

Connect Claude to SolidActions

SolidActions hosts the MCP service at https://app.solidactions.com/mcp. Add that URL to Claude, authorize access in your browser, then verify the connection. You do not install or run a SolidActions MCP server on your computer.

Last reviewed July 14, 2026

This guide covers Claude Desktop and Claude Code.

Do not use the CLI instructions on the workflow page as a substitute for connecting MCP; they set up a different path.

Before you connect

  1. Create a SolidActions account and finish email verification.
  2. Create or join the workspace you want Claude to use.
  3. Keep the browser where you signed in available for the authorization step.

Claude Desktop

  1. Open Settings → Connectors in Claude Desktop.
  2. Select Add custom connector.
  3. Enter a name such as SolidActions.
  4. Paste the hosted MCP URL into Remote MCP server URL and save.
https://app.solidactions.com/mcp

Claude Code

Run this command in a terminal:

claude mcp add --transport http solidactions https://app.solidactions.com/mcp

When Claude Code asks whether to trust the connection, review the URL and approve it.

Authorize the connection

Claude opens a SolidActions page in your browser. Complete each step before returning to the client:

  1. Sign in if SolidActions asks you to.
  2. Choose the workspace Claude should access.
  3. Review the available product areas and select the ones Claude needs.
  4. Review the consent screen, then authorize the connection.
  5. Return to Claude. If the browser does not return automatically, switch back to Claude yourself.

Authorization is workspace-specific. If you have more than one workspace, confirm its name before approving.

Verify without changing your workspace

Paste this prompt into Claude:

Use the SolidActions workflows_guide tool with topic "setup". Do not create or change anything. Reply with only the SolidActions app URL named in the guide.

Expected result: https://app.solidactions.com. The workflows_guide tool is available even in a brand-new workspace, so this check does not depend on existing docs, tasks, dashboards, or integrations.

What this connection can do

  • Read and update workspace Docs that hold business context.
  • Work with Crews and their reusable roles and routines.
  • Track durable work on Pegboards.
  • Read and maintain Dashboards.

The exact tools Claude sees depend on the product areas and workspace access you approved. Deployed workflows are a separate CLI path; see Build workflows.

Match the connection to your permissions

Read
Use the app to view that product area. Read alone cannot authorize its hosted MCP tools.
Use
Authorize the product area in an MCP client and use the tools your role permits.
Build
Create or change Docs and Crews, author Dashboards, and perform other management actions.

Use is the minimum level for selecting a product area during MCP authorization. Some actions still require Build; for example, Work Build is required to change Docs or Crews and Measure Build is required to author or publish Dashboards. Track Use operates pegs, while Track Build creates and deletes whole Pegboards.

Disconnect or change access

Remove the SolidActions connector in Claude to remove it from that client. Also open Settings → MCP Connections in SolidActions and revoke the matching connection so its server-side credential can no longer be used. Always revoke there when a device is lost or access should end immediately.

To change the workspace, board, or approved product areas, revoke the old connection, remove it from the client, then connect again so the browser authorization flow can ask you to choose.

If the verification prompt fails, follow MCP troubleshooting or email [email protected].

Next: set up CLI skills and build a workflow.