cc-profiles Documentation PyPI GitHub Install

Guides

Skills and MCP servers

Two tabs manage, for one profile at a time, the skills in its skills/ folder (Skills) and the MCP servers in its .claude.json (MCP). Pick the profile at the top of either tab: the choice carries over when you switch between the two. You can also click Skills or MCP on a profile in the Profiles tab. The line next to the selector shows the account the profile is signed in with.

The Skills tab: the skills of the Default profile, with release-notes open in the editor

Every change goes to a backup first, like any other operation, and applies from the next Claude Code session in that profile.

Skills

A skill is a folder skills/<name>/ with a SKILL.md file: a frontmatter with name and description, then the instructions. Claude reads the description to decide when to use the skill.

If the profile shares skills with others, the header says so: editing, adding or deleting a skill changes it for all of them.

Skills that come from plugins are not listed here: manage them with /plugin in Claude Code.

MCP servers

The MCP tab: the MCP servers of the Default profile, for all projects and for one project, with their type and command or URL, and below them the Browser for Claude section

The tab lists the servers configured in the profile’s .claude.json (for the default profile, ~/.claude.json):

Each row shows the type (stdio, http or sse), the command or URL, and the names of its environment variables and headers. Their values are not shown in the list, because they often hold tokens; Edit… shows them.

Not listed here, because they are configured elsewhere:

Claude Code keeps .claude.json in memory while it runs. Close open sessions in the profile before changing its MCP servers, or restart them afterwards.

Browser for Claude

Under the MCP servers, Browser for Claude says how Claude Code opens web pages in the profile, and lets you choose:

The Browser for Claude section of the MCP tab: the local browser, not added yet, with Add and Add to all, and Claude in Chrome at start, on, with Turn off and Turn off in all, under a warning that Chrome connects at start in profiles of two claude.ai accounts

The extension is signed in to one claude.ai account at a time. When Chrome connects at start in profiles of two or more accounts, the section warns that the profiles of the other accounts find no browser, and suggests the local one for them.

Every change goes to a backup, with Undo in the message.

claude.ai connectors

Connectors (Gmail, Google Drive, Canva…) belong to your claude.ai account, not to the profile: every profile signed in with the same account gets the same ones, and you connect or remove them on claude.ai. What a profile can do is keep some of them out, and the claude.ai connectors section under the MCP servers does that with a switch:

The list shows the connectors Claude Code has connected in the profile at least once (it records them in .claude.json), plus any connector a deny rule names.

Claude Code only ever adds to that list, so a connector you removed or renamed on claude.ai would stay there. cc-profiles keeps it in step with your account by itself: when you open the MCP tab it runs claude mcp list in the profile, which asks claude.ai for the account’s connectors with the profile’s own sign-in (cc-profiles never reads the token). Then:

claude mcp list also starts every MCP server of the profile to check it, so the check runs at most once an hour per profile; Check now runs it again. It is skipped when Claude Code is not installed, when the profile is not signed in, or when all connectors are off. If claude.ai lists no connectors at all, nothing is taken off, because that is also what a failed answer looks like.

Forget takes a connector off the profile’s list by hand, when the check cannot run (the switch must be on, so no deny rule is left behind). If the connector still exists, Claude Code adds it back at its next session, so forgetting one by mistake loses nothing.

The connector itself stays connected on your account, and other profiles keep using it. To give two profiles different connectors, for example a work Google Drive and a personal one, sign them in with two different accounts.

Every change goes to the backup, and an open session picks it up when it restarts.