Server URL
https://mcp.useswarm.co/mcpThe hosted server uses Streamable HTTP and is read-only. It cannot start tests, change data, or open a tunnel to your computer. To run tests against localhost, keep using the local CLI / MCP; its local process manages the tunnel.
Connect your assistant
Cursor
Add this to your project’s .cursor/mcp.json or your global ~/.cursor/mcp.json (merge it with any existing servers). Enable Swarm in Cursor’s MCP settings, then follow the sign-in prompt.
{
"mcpServers": {
"swarm": {
"url": "https://mcp.useswarm.co/mcp"
}
}
}Claude.ai and Claude Desktop
Open Settings → Connectors → Add custom connector. Name it Swarm, enter the server URL above as the remote MCP URL, and connect. Complete the Swarm OAuth sign-in in your browser. Custom connector availability depends on your Claude plan and organization’s policies; use a client version that supports remote MCP with OAuth.
Claude Code
claude mcp add --transport http swarm https://mcp.useswarm.co/mcpRun /mcp in Claude Code, select Swarm, and authenticate in the browser when prompted.
Devin
In Devin’s MCP marketplace, select Swarm if listed. Otherwise add a custom remote MCP server with the URL above. Choose OAuth authentication, connect your Swarm account, and complete the consent flow. Enable the connector for the sessions that should use it.
Sign-in and access
Your client opens Swarm sign-in in a browser. Choose the organization and role for this connection, review the requested access, and allow or deny it. You can grant only a role your account currently holds or a lower role. Organization membership, role, and consent are checked on API calls; a connection does not grant access to other organizations.
Hosted connections request swarm:read. OAuth also supports openid, profile, and email for identity, and offline_access to let your client refresh its connection. Dynamically registered connectors are limited to these read-only scopes, not swarm:test. Test and swarm reads include your personal data and the authorized organization’s data.
Read-only tools
- dev_list_swarms
- List saved persona swarms tied to your account (personal and active organization).
- dev_list_tests
- List previously run UX tests, newest first, with pagination and test IDs.
- dev_get_test
- Get one test’s current status and findings without waiting, including recommended actions, judge verdict, and persona results.
Try asking: “Show my recent UX tests” or “What did the latest test find?” If no tests or saved swarms exist yet, the list is empty. Run a test using the dashboard or local CLI / MCP first. If a test is still running, ask for its status again later.
Disconnect and revoke access
Remove or disconnect Swarm in your assistant’s connector settings to stop using it there. Swarm does not currently provide a Connected apps screen for revoking hosted MCP grants. Removing a connector or signing out of Swarm does not by itself guarantee server-side token revocation. To revoke the Swarm authorization, contact founders@useswarm.co and identify the connector and organization; never send tokens or credentials.
Data, privacy, and help
Your assistant receives the data returned by the tools you use: saved swarm metadata, test URLs and goals, status, UX scores, findings, judge verdicts, and persona results. Connect only assistants you trust with that data and review their privacy policies. Read-only access prevents changes; it does not make the returned information non-sensitive.
See Swarm’s Privacy Policy and Terms of Service. For connection problems, confirm your client supports Streamable HTTP with OAuth, retry sign-in for an expired connection, and check your organization access if permission is denied. Contact founders@useswarm.co for help.