Connect Claude and Other MCP Clients to Your Super Agent

What This Connects

Agentic Workers exposes your Super Agent workspace through a remote Model Context Protocol (MCP) endpoint at https://www.agenticworkers.com/api/agw-mcp. MCP is the standard that lets AI apps discover and call tools from another product. External clients use that endpoint to discover and call Agentic Workers tools such as listing agents, creating agents, managing memories, scheduling jobs, attaching tools, adding tool connections, and deploying agents.

Use this when you want Claude Desktop, Claude Code, Cursor, or another MCP-capable client to operate your Agentic Workers workspace with the same organization token used by the Operator CLI.

Before You Start

Sign in to Agentic Workers and open the organization that owns the Super Agent you want to control. You need permission to generate an organization token from the Operator CLI page.

Use an MCP client that supports remote HTTP JSON-RPC connections and custom request headers. If your client only supports local stdio MCP connections, use that client's documented remote MCP bridge and pass the same connector URL and Authorization header through the bridge.

Treat the token like a password. It can act on your behalf in the organization, so do not paste it into public chats, commit it to a repository, or share it with clients you do not trust.

Get the Connector URL and Token

Open the Operator CLI page for your organization and generate a token. Copy it immediately because Agentic Workers only shows the full token once.

Use this connector URL for production: https://www.agenticworkers.com/api/agw-mcp. In local development, replace the host with your local Agentic Workers origin, for example http://localhost:3000/api/agw-mcp.

Configure your MCP client to send Authorization: Bearer <your-token> on every request to the connector URL.

Claude Desktop

In Claude Desktop, add a connection named agentic-workers to your MCP configuration. Use the Agentic Workers connector URL as the server URL and add an Authorization header with Bearer followed by your token.

For Claude Desktop, configure mcpServers -> agentic-workers with url https://www.agenticworkers.com/api/agw-mcp and an Authorization header containing your organization bearer credential.

Restart Claude Desktop after saving the configuration. Then ask Claude to list available Agentic Workers tools or list your agents before asking it to create, update, deploy, or schedule anything.

Claude Code and Generic MCP Clients

For Claude Code or another MCP client, add Agentic Workers as a remote HTTP MCP connection. Set the server URL to https://www.agenticworkers.com/api/agw-mcp and set the Authorization header to Bearer <your-token>.

If the client asks for transport or protocol details, choose HTTP JSON-RPC MCP. The Agentic Workers endpoint supports initialize, notifications/initialized, ping, tools/list, and tools/call.

If the client stores MCP connections in JSON, use this structure: mcpServers -> agentic-workers -> url plus headers -> Authorization. Keep the token in the client's secret store or local private config when possible.

Verify the Connection

First ask the client to list tools. A working connection should return Agentic Workers tools such as agw_list_agents, agw_create_agent, agw_list_available_tools, agw_add_mcp_server, and agw_create_scheduled_job.

Then run a low-risk read check such as listing agents. Confirm the returned agents belong to the expected Agentic Workers organization before approving write actions.

For the first write test, make a reversible change such as creating a small test agent or adding a short memory to a test agent. Open Agentic Workers afterward and review the latest trace, the step-by-step run log, or agent state so you can confirm the action landed in the right workspace.

Troubleshooting

If the client receives 401 or unauthorized, generate a fresh organization token, confirm the Authorization header starts with Bearer, and make sure there are no extra spaces before or after the token.

If the client cannot find tools, confirm it is using POST requests to /api/agw-mcp for MCP JSON-RPC and that it supports remote HTTP MCP connections with custom headers. A plain GET request only returns the discovery shape used by Agentic Workers documentation.

If the client connects to the wrong organization, revoke the token, switch to the intended Agentic Workers organization, generate a new token there, and update the MCP client configuration.

If a tool call fails because a connected app is missing, connect that app from Integrations first, then rerun a small read-only prompt. The external MCP connector can manage Agentic Workers agents and tools, but provider access still depends on the integrations connected inside Agentic Workers.

If Claude or another client tries to take a sensitive action too early, update your prompt to require approval before sending messages, changing customer records, deploying agents, or attaching new MCP tool connections.