Skip to content

Claude App Setup

How do I connect Claude web, Desktop or Cowork?

Section titled “How do I connect Claude web, Desktop or Cowork?”

Connect through a remote MCP connector, complete OAuth, then verify the account inside Claude. Custom connectors work on Free, Pro, Max, Team, and Enterprise. Free allows one. Anthropic documents connector availability. Paid plans can also install plugins in Claude web, Desktop’s Chat tab, and Cowork. See plugin availability. The Controller AI plugin (version 0.4.0, from Controller-AI/controllerai-claude-plugin) bundles the same endpoint and eleven skills.

In the Controller AI app: open Settings → AI assistants → Connect an assistant and select Claude. It points you to the plugin below and has the server URL for a custom connector. The app cannot install either in Claude for you. If you work in a terminal, follow Claude Code setup instead.

On an individual account, open Customize → Connectors → + → Add custom connector. Name it Controller AI, enter the URL below, select Add, then select Connect. Leave the optional OAuth Client ID and Client Secret blank. Follow Anthropic’s connector steps.

Setting Value Purpose
Server URL https://mcp.getcontroller.ai/mcp Controller AI’s remote endpoint.
Transport Streamable HTTP Carries remote tool calls.
Authentication OAuth Opens browser authorization.

On Team or Enterprise, an owner adds it under Organization settings → Connectors → Add → Custom → Web. Members then select Customize → Connectors → Connect. Enable it per conversation through + → Connectors. See organization and conversation controls. Sign in through the browser. Do not paste a Claude or Controller AI API key into these fields.

Open Customize → Plugins, search Controller AI, and select Add. It is listed as a community plugin from controller-ai/controllerai-claude-plugin. The same plugin controls serve Cowork, web chat and Desktop Chat. Anthropic documents these controls. If the search shows nothing, open Personal plugins → + → Add marketplace → Add from a repository, enter Controller-AI/controllerai-claude-plugin, and install controllerai.

Installing the plugin does not authorize the account on its own. Open Controller AI plugin details → Connectors, select Connect for controllerai, and complete OAuth. Then start a fresh Cowork task. If repository installation is unavailable, use the custom connector above. The remote guides below provide the instructions.

Allow full access appears only when Claude requested controller:full. Continue read-only appears only when Claude requested controller:read. If the choice you need is unavailable, change the host’s requested scope and reconnect. The consent screen cannot grant access that was not requested. See Assistant access and security.

Next sign in to your Controller AI account, or sign up for one. Connect your Controller account displays the signed-in email. Check it before selecting Connect account.

In the enabled conversation or Cowork task, call account_status with {}. Inspect user, account.accessMode, and grantedScopes. The value credentialKind: "host-managed-oauth" describes Claude’s grant.

Unconfirmed emails are hidden, so a null user.email alone does not prove the wrong account. Compare the user and organization details you can see with the account you signed in to during consent. If the call reports that you are not signed in, reconnect Controller AI and complete the authorization with your own account.

How do I fetch guidance and verify access?

Section titled “How do I fetch guidance and verify access?”

Ask Claude to call guide_list with {}, then guide_get with name: "controllerai-start". The list reports names, versions, and reference paths. Fetching a guide returns instructions and references from the server bundle, and installs no local files. The server stores no selected workflow. Scoped calls need an explicit workflowId, and you supply instruction and file content inline rather than as local paths.

In the app: open Agents. You have no agents yet is a valid empty inventory, and that screen has no search control. Otherwise, search for Support helper. All agents includes shared agents, while ownership: "mine" below returns only your own.

In Claude, call agent_list with:

{ "ownership": "mine", "search": "Support helper" }

Report names and IDs, and create nothing. An empty result is valid, because Support helper is a teaching example rather than an account default.

For web chat, check + → Connectors. If a Desktop connector has the wrong URL, remove it under Customize → Connectors and add it again, because custom connectors cannot be edited. To repeat authentication, disconnect it there. See Claude’s removal and permission controls. For Cowork, reconnect in the plugin details and start a fresh task.

If Controller’s account-link screen shows the wrong email, open the Controller app and choose user menu → Log out. Sign in to the intended account, then restart the connection from Claude. If it says This connection request is no longer valid, start a new connection from Claude. After a repair, repeat account_status and the inventory.

Next: build Support helper, then use Skills and updates for maintenance.