Skills, MCP and tools

Plugins, skills, connectors and MCP servers, the CLI tools on your computer, and the skills Mirasim ships with.

Plugins

Settings › Plugins is where all of this lives: Plugins, Connectors, CLI and Skills along the top, plus Computer Use (chapter 19). A plugin bundles skills and connectors that belong together, so one install brings both.

Skills

A skill is a named, reusable set of instructions, such as how to run your tests or how your deploy works. An agent loads it when the task calls for it.

Type / in the composer to list your skills alongside the agent's built-in commands. Skills installed under Settings › Plugins › Skills work in every session on this computer; a skill kept in a workspace's .mirasim folder works only there.

Managing skills

mirasim ui-cli --port 4970 skill list                       # workspace + global
mirasim ui-cli --port 4970 skill install --source https://github.com/o/r --scope global
mirasim ui-cli --port 4970 skill create --name run-our-tests --scope workspace
mirasim ui-cli --port 4970 skill update --name run-our-tests
mirasim ui-cli --port 4970 skill remove --name run-our-tests

MCP servers

Your own MCP server — a local command or a URL, with its environment variables — goes in under Settings › Plugins › Connectors › Add custom. Its tools then sit next to the built-in ones. From a terminal:

Add, toggle and health-check a server

mirasim ui-cli --port 4970 mcp list
mirasim ui-cli --port 4970 mcp add --name gh \
  --command npx --arg -y --arg @some/mcp-server --scope global
mirasim ui-cli --port 4970 mcp toggle --name gh --enabled false
mirasim ui-cli --port 4970 mcp health --name gh     # live handshake probe

Connectors

Connectors are a curated catalog on top of MCP. Install one, give it its secrets or run it remotely, and enable it per agent. You can validate a connector against the live service and re-run its OAuth grant when a token expires.

Connector lifecycle

mirasim ui-cli --port 4970 connectors list
mirasim ui-cli --port 4970 connectors install SOME_ID --mode remote --secret KEY=value
mirasim ui-cli --port 4970 connectors enable SOME_ID --agent claude
mirasim ui-cli --port 4970 connectors validate SOME_ID    # records tool count / error
mirasim ui-cli --port 4970 connectors auth SOME_ID        # (re)start OAuth, prints the URL
mirasim ui-cli --port 4970 connectors search "issue tracker"   # the official registry

Connector search also queries the official MCP registry.

The CLI tools already on your computer

Mirasim lists the common developer CLIs on your PATH, such as git, gh and docker, and shows whether each is signed in.

What's installed, and what's signed in

mirasim ui-cli --port 4970 cli-tools    # dev CLIs on PATH + auth state
mirasim ui-cli --port 4970 clis         # agent CLIs: version / latest / update available

Computer Use

Letting agents operate browsers and desktop apps now has its own chapter.

Chapter 19: Computer Use →

Skills that come with Mirasim

Every install carries six skills, and a new Mirasim updates them unless you edited them.

mirasim-guide: Answers questions about how Mirasim, Claude Code, Codex and Kimi Code work, from the official docs.
mirasim-operate: Does things in Mirasim for you: settings, sessions, schedules, other spaces, inviting people.
mirasim-publish: Publishes what you built to people outside the space.
mirasim-doc: Writes documents into the space's Docs.
mirasim-needs-you: When you have to sign in or approve something first, stops and hands you the link.
eval: Runs only when you ask for it by name ($eval): tries what you built through its real entry point and keeps screenshots and a record of each step, on this computer.

Something wrong or missing on this page? Tell us