Skip to content

Claude Code Setup

How do I connect Claude Code to the right account?

Section titled “How do I connect Claude Code to the right account?”

Install the Controller AI plugin, then authenticate inside Claude Code. The plugin (version 0.4.0, from the GitHub repository Controller-AI/controllerai-claude-plugin) bundles the hosted MCP connector and eleven skills. Nothing else is installed locally. If you prefer, add the connector by URL instead. Verify the account before building Support helper.

In the app: open Settings → AI assistants → Connect an assistant and select Claude to copy the two commands below.

With an assistant: add the plugin marketplace from GitHub, then install the plugin:

Terminal window
claude plugin marketplace add Controller-AI/controllerai-claude-plugin
claude plugin install controllerai@controllerai-plugin-marketplace

Inside a Claude Code session, /plugin marketplace add Controller-AI/controllerai-claude-plugin followed by /plugin install controllerai@controllerai-plugin-marketplace does the same. The plugin installs at user scope by default. Claude documents plugin scopes and activation.

After a shell install, restart Claude Code or run /reload-plugins. If it warns and skips, run /reload-plugins --force. Activation details.

Run this in your project to add only the MCP server. It uses Claude’s default local scope, so another directory can show different configuration:

Terminal window
claude mcp add --transport http controllerai https://mcp.getcontroller.ai/mcp

Without the plugin, the assistant reads the same guidance through guide_list and guide_get instead of installed skills.

Open /mcp, select plugin:controllerai:controllerai for the plugin or controllerai for the direct connector, then select Authenticate. Allow full access appears only when controller:full was requested. Continue read-only appears only for controller:read. If the option you want is absent, change the host’s requested scope.

Sign in to your Controller AI account, or sign up for one, and verify the browser email before selecting Connect account.

Call account_status with {}, and check user, account.accessMode, and grantedScopes against the account and access you authorized. Unconfirmed email addresses are hidden, so a null user.email alone does not identify a different account. If the call reports that you are not signed in, authenticate again from /mcp with your own account.

Fetch guide_get with {"name":"controllerai-start"}. It returns instructions and references without installing files. The server stores no selected workflow, so supply workflowId on scoped tools and pass file and instruction text inline.

Verify an inventory without creating anything

Section titled “Verify an inventory without creating anything”

In the app: open Agents. You have no agents yet is a valid result, and search is hidden there. Otherwise search Support helper. All agents includes shared agents, while the query below returns only yours.

With an assistant: call account_status with {}, then agent_list with:

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

An empty list is a success. Read access is enough for an inventory, while building requires controller:full.

If tools are missing, check that the plugin is installed and enabled under /plugin, then run /reload-plugins. If the account is wrong, open /mcp, select the server above, select Clear authentication, then authenticate again. Claude authentication controls. If the browser shows the wrong email, open the Controller app’s user menu, select Log out, sign in correctly, and restart the host connection. If you see This connection request is no longer valid, start a fresh connection. Then rerun account_status.

Next: build Support helper or update skills.