zo-mcp
Allows sending emails to the user and managing Gmail inbox.
Provides tools for interacting with Google Calendar, such as creating and managing events.
Enables management of issues, projects, and teams on Linear.
Allows controlling Spotify playback and managing playlists.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
zo-mcp
Internal MCP for terminal agents on your Zo Computer.
Claude Code, Cursor, Codex, and other stdio MCP clients running inside your Zo get the same tools Zo chat has — files, shell, web, calendar, SMS, email, images, agents, the lot. No /zo/ask session. No access token from Settings. Just direct tool calls over the in-box identity token you already have.
This is the stdio counterpart to Zo's official HTTP MCP. Same tool names, same schemas, same backend. Different transport, and only works on your Zo.
Why this exists
Zo chat can text you, read your files, hit Gmail, run bash. Terminal agents on the same box couldn't — they're stuck in a TTY with no bridge to Zo's tool layer.
Official Zo MCP fixes that from outside the box (HTTP + zo_sk_ access token). zo-mcp fixes it from inside the box (stdio + ZO_CLIENT_IDENTITY_TOKEN).
Related MCP server: Terminal Session Manager
Requirements
You must be on a Zo Computer (SSH session, Cursor on the box, Claude Code in the workspace, etc.)
ZO_CLIENT_IDENTITY_TOKENmust be set — it is automatically on every Zo
If that env var isn't there, zo-mcp exits. It does not work from your laptop, CI, or anywhere off-box.
Install on your Zo
Clone into your workspace (or anywhere on the box):
git clone https://github.com/vihaanshahh/zo-mcp.git
cd zo-mcp
npm installOr one-shot via npx (still runs on the Zo — npx just fetches the package):
npx github:vihaanshahh/zo-mcpMCP setup
Cursor / Claude Code (.mcp.json)
{
"mcpServers": {
"zo": {
"type": "stdio",
"command": "node",
"args": ["/home/workspace/zo-mcp/dist/index.js"]
}
}
}Adjust the path to wherever you cloned it. After npm install, dist/ is built automatically.
Claude Code CLI
claude mcp add zo -- node /home/workspace/zo-mcp/dist/index.jsReload MCP. You should see ~80 tools — same catalog as GET /zo/tools.
Tools
The server mirrors Zo's live tool catalog:
GET https://api.zo.computer/zo/tools
POST https://api.zo.computer/zo/tools/{name}/runCategories include:
Files —
read_file,write_file,edit_file,grep_search, …Shell —
bash, …Web —
web_search,read_webpage, …Comms —
send_sms_to_user,send_email_to_userApps — Google Calendar, Gmail, Linear, Spotify, …
Media —
generate_image,transcribe_audio, …Automation —
create_agent,list_agents, …
Tool list refreshes on each tools/list call. Per-tool docs: zo.computer/docs/tools.
CLI shortcut
Text yourself from a shell script without MCP:
zo-text "build finished on branch feature-x"Wraps send_sms_to_user on the same internal route.
vs official Zo MCP
zo-mcp (this) | Official Zo MCP | |
Where it runs | On your Zo only | Anywhere with network |
Transport | stdio | HTTP |
Auth |
|
|
Tool set | Full catalog via | Full catalog via |
Use case | Terminal agents on the box | External clients, mcporter, OpenClaw bridge |
Use both if you want. They hit the same tools.
Development
npm install
npm run build
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | node dist/index.js 2>/dev/null | head -c 500License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Related MCP Servers
- FlicenseAqualityDmaintenanceA simple MCP server that exposes a terminal tool, allowing AI agents to execute shell commands.1-
- FlicenseBqualityCmaintenanceEnables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.15-
- AlicenseNot gradedqualityBmaintenanceEnables secure cross-system identity and token exchange for autonomous agents, including on-behalf-of token exchange, scoped permission delegation, token lifetime refresh, and zero-leakage ephemeral credentials. It integrates with MCP-compatible clients via standard JSON-RPC stdio without external runtime dependencies.7MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables agents to perform inter-agent mutual handshakes and route messages through HMAC-authenticated envelopes with replay-attack prevention. It also provides deterministic, zero-dependency execution of telemetry inputs and quantitative analysis, returning JSON tool results over STDIO.7MIT