The Minicor MCP

Minicor exposes a Model Context Protocol server. Point Cursor, Claude Code, or any MCP-capable agent at it and the agent can teach jobs, run samples, inspect failures, drive desktops, and take jobs live, the same surface the dashboard and the co-pilot use.

Hosted server (recommended)

The easiest way to connect: no install, no local process. The server runs at

https://mcp.minicor.com/mcp

Cursor
Claude Code
Claude (web and desktop)

Add a URL entry to ~/.cursor/mcp.json; Cursor prompts for the sign-in on first use:

{
  "mcpServers": {
    "minicor": {
      "url": "https://mcp.minicor.com/mcp"
    }
  }
}

claude mcp add --transport http minicor https://mcp.minicor.com/mcp

Then run /mcp inside Claude Code to trigger the sign-in.

Go to Settings > Connectors > Add custom connector, paste https://mcp.minicor.com/mcp, and save. OAuth is auto-discovered; no client ID or secret.

Authentication is an OAuth flow: your client opens the Minicor sign-in page, you enter your email, password, and region (US or Canada), and the connection acts as your account. No API keys, no local tokens. Access tokens expire within an hour and refresh automatically for up to 30 days; after that you sign in again. The hosted tool set matches the local server except for the tools that read and write your local disk (workspace clones, sessions, sync). If you need those, install locally.

Local install

Cursor
Claude Code

Add the server to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "minicor": {
      "command": "npx",
      "args": ["-y", "@minicor/mcp-server"]
    }
  }
}

claude mcp add minicor -- npx -y @minicor/mcp-server

Then authenticate:

npx -y -p @minicor/mcp-server minicor-mcp-setup

This opens a browser to sign in with your Minicor account. Tokens are stored at ~/.minicor/tokens.json and refresh automatically. On a headless machine or over SSH, add --cli to sign in from the terminal.

What the surface covers

Area	What an agent can do
Jobs	Teach with samples, group scenarios, run samples, read run reports, inspect failures, go live.
Automations	Create and edit the steps underneath a job, run them against a desktop.
Executions	List runs, read step outputs, fetch replays and screenshots, diagnose failures.
Desktops	Connect, screenshot, inspect UI elements, execute scripts, control runs.
Configurations	Create and update key-value configurations, including two-factor channels and secrets.
Workspace	Issues for shared context, skills for reusable automation patterns, agents on watch.

Where to go next

The job build loop is the canonical way an agent should work on a job. Read it first. The zero-to-live path is short: connect, pick a workspace, make sure a desktop is attached, teach samples, run them until green, go live.
Sessions covers long-running work and handoffs between agents.
Tools is the one-page overview of the tool families.

These docs are written to be read by agents as much as by people. If you are an agent connected to the MCP: samples define done. Start every job task by making sure the job has samples that encode what correct means.

Getting started

Teaching jobs

Running jobs

Safety and operations

For agents

The Minicor MCP

Hosted server (recommended)

Local install

What the surface covers

Where to go next

​Hosted server (recommended)

​Local install

​What the surface covers

​Where to go next

Hosted server (recommended)

Local install

What the surface covers

Where to go next