machine-mcp

A laptop-side MCP server. An AI agent talks to it over stdio and runs tools on the human's own machine (the one already signed into Copilot CLI and the rest of the local toolchain).

This is a local command process. It does not wrap Cursor or Grok Bot pairing. It does not replace Grok Bot Computers or Local execution.

Install

Python 3.10 or newer.

cd machine-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e .

Dev tests:

pip install -e ".[dev]"
pytest tests/

Related MCP server: remotessh-mcp

Run

machine-mcp

stdio servers block on stdin. The client starts the process and owns the pipes.

Smoke test (prints status JSON, exits 0):

machine-mcp --check

On start, if MACHINE_MCP_TOKEN is unset, a random bearer token is generated and printed once to stderr:

machine-mcp token: ...

Keep that token for HTTP v2. stdio v1 does not check it: the client already spawned this process as you.

Cursor / Grok Bot connector

Add a local MCP server whose command is the venv entry point. No pairing protocol.

{
  "mcpServers": {
    "machine-mcp": {
      "command": "path/to/.venv/bin/machine-mcp"
    }
  }
}

See examples/mcp.json. Point command at the absolute path of .venv/bin/machine-mcp on this laptop.

Optional env:

• MACHINE_MCP_WORKSPACE file-tool root. Default: ~/machine-mcp-workspace (created on start).

• MACHINE_MCP_TOKEN bearer token for a future HTTP listener. Generated if unset.

Tools

Local only

stdio is local to this process. There is no listen socket in v1. HTTP is optional later and must require MACHINE_MCP_TOKEN. Do not expose this server on a network.

License

MIT. Copyright Andrea Griffiths 2026.