urbit-mcp
Urbit MCP (%mcp) is a general-purpose Model Context Protocol interface for Urbit, documented in urbit.org's first-party public agent-skill snapshot (/.agents/skills/using-urbit-apps/references/urbit-mcp/). It is a userspace desk from gwbtc/urbit-mcp — community-built, surfaced and documented by urbit.org itself — that exposes a running ship's capabilities as MCP tools, prompts, and resources over HTTP at the ship's /mcp endpoint. Because every Urbit ship is a self-hosted personal server, there is no central hosted MCP URL: each ship serves its own endpoint, authenticated with the ship's web login cookie (urbauth-~ship) obtained via +code and POST /~/login. The running-urbit-os skill additionally documents an MCP-bootstrap flow for disposable ships that expose an MCP endpoint for agent tooling. Tool list captured verbatim from the published reference.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
build-file— Desk and file operations - build a filecommit-desk— Desk and file operations - commit a deskget-file— Desk and file operations - get a fileinsert-file— Desk and file operations - insert a filelist-files— Desk and file operations - list filesmount-desk— Desk and file operations - mount a desknew-desk— Desk and file operations - create a new deskrun-tests— Desk and file operations - run testsinstall-app— Desk and file operations - install an appget-our-id— Ship and agent operations - get the ship's identitypoke-our-agent— Ship and agent operations - poke an agentnuke-agent— Ship and agent operations - nuke an agentrevive-agent— Ship and agent operations - revive an agentscry— Ship and agent operations - scry (read namespace)toggle-permissions— Ship and agent operations - toggle permissionsadd-mcp-feature— MCP self-extension - add an MCP featureadd-mcp-prompt— MCP self-extension - add an MCP promptadd-mcp-resource— MCP self-extension - add an MCP resourceadd-mcp-tool— MCP self-extension - add an MCP tool
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.