CONNECTED TOOLS · CLI AND MCP

Use a persona’s tools from your CLI

Connect a supported command-line assistant to PersonaStack through MCP. The setup opens a sign-in flow where you choose the persona whose tools the client should use.

Prepare the persona and client

Configure the persona’s integrations first. The client connection uses that persona’s available tools. It does not grant access to every connection in the workspace.

Install your chosen CLI and complete its own provider sign-in. PersonaStack’s Use with CLI dialog shows the current prerequisite for each client. Follow that link when the client needs installation or an update.

Copy the setup for your system

1. Open the persona’s settings.
2. Choose Use with CLI below Open Chat.
3. Select your client in Use with CLI Tools.
4. Choose your operating system. Use Windows PowerShell for the PowerShell command.
5. Read the prerequisite, copy the generated command, and run it in your terminal.

The dialog provides choices for Codex, Claude Code, OpenCode v2, Gemini, and Pi. Use the generated command for the selected client and system. The commands differ, so do not reuse one client’s setup for another.

Sign in and choose the persona

Follow the sign-in flow opened by the client. MCP authorization uses your PersonaStack account email and password. If you normally use Google or organization SSO and have no password, set one in Profile first.

Check the workspace and choose the intended persona before approving access. This is a separate authorization from signing into the PersonaStack website. Being signed into the website alone does not finish the CLI connection.

Try a small read

Return to the CLI and ask it to inspect the tools available through the new connection. Start with a read, such as listing the selected persona’s assigned integrations. Check that the persona and account are the ones you intended before asking for changes to an external service.

If your persona has Desktop Control assigned, its MCP tools can run commands on the selected computer and return output. They can also supply input to an interactive command. This is separate from commands your CLI runs on its own machine. Name the target computer and directory in your request.

Use selected skills in your MCP client

1. Open the authorized persona’s settings and select the catalog or custom skills it needs in Skills.
2. Check that your client supports the MCP Skills extension. Ordinary MCP tool support alone does not confirm skill support.
3. Refresh the client’s available skills using its own controls. Check that the expected skills appear from PersonaStack.
4. Read the instructions and supporting files. Follow the client’s approval steps before asking it to use the skill.
5. Try a small task and review the result.

Clients connected to the same persona receive the same selections. A client connected to another persona receives only that persona’s selected skills. Selecting a private custom skill allows clients authorized for that persona to read its files.

The client chooses when to load a skill and how to run its commands. MCP delivery does not install programs, connect service accounts or grant local permissions. Supply required dependencies and service access separately. Reading a skill file does not confirm that the client activated it.

Refresh the skill list after editing or removing a selection. Subsequent reads of removed selections and superseded versions fail. Files already downloaded may remain on the client. Remove those copies through the client when needed.

Give your assistant the PersonaStack skill

The public PersonaStack SKILL.md explains the product, links to these guides, and describes how to use an authorized persona connection. Give its URL to an assistant that can read web pages, or download the file and use your client’s supported skill import flow.

Reading or importing the skill does not connect your account or grant access to tools. Complete the authorization above when your assistant needs to act through a persona.

A public skill discovery index is also available. It follows a draft discovery convention. Automatic discovery and installation depend on your client.

If connection fails

• The command is not found: follow the installation prerequisite shown for your client.
• Sign-in fails: check your email and password. Set a password in Profile if needed.
• The wrong tools appear: check which persona you authorized and review its assignments.
• A connected tool fails: open that integration’s settings and read its status.

If selected skills do not appear, confirm the authorized persona and saved selections first. Then check the client’s MCP Skills support and refresh its skill list. Reconnecting tool access alone does not add skill support to the client.

See integration and tool troubleshooting before reconnecting every service.

Need a hand? Contact the PersonaStack team.