Urbit通用的"模型上下文协议"接口.

□ 从源头构建

1. 建设和安装

• • 需要运行中的Urbit飞船,无论是真实的还是假的,运行在您可使用终端的机器上。 *
• *要求Zig 0.15或更新。 确保zig version工作。 *

在您的 Urbit 船上创建和挂载办公桌 :

在 [[T1] 文件夹中,运行 zig build。 默认情况下, 这将在此文件夹中安装依赖性 。 使用 [ [T4]/ [T5] 选择另一个输出目录, 并使用 [[T6] 选项, 将您的船台内容额外替换为源台.

2. 认证设置

从道场得到你的船的网络登录代码:

认证并获取会话 cookie :

从 [ [T7] 信头中取出饼干, 它看起来像:

{\fn黑体\fs22\bord1\shad0\3aHBE\4aH00\fscx67\fscy66\2cHFFFFFF\3cH808080}请说 {\fn黑体\fs22\bord1\shad0\3aHBE\4aH00\fscx67\fscy66\2cHFFFFFF\3cH808080}谢谢 使用编码器注册

把这个加入你的[T8]:

3个b 与 Claude 代码注册

使用 HTTP 传输方式将 MCP 服务器添加到 Claude :

□ 使用量

QQ 工具

只是问! 您可以在这里看到默认的工具 。

您可以请求您的 LLM 添加新工具 .

Urbit MCP

A general-purpose Model Context Protocol interface for Urbit.

Build from source

1. Build and Install

• Requires a running Urbit ship, real or fake, running on a machine you have terminal access to.
• Requires Zig 0.15 or newer. Make sure zig version works.

Create and mount the desk on your Urbit ship:

> |new-desk %mcp
> |mount %mcp

In the urbit-mcp folder, run zig build. By default this will install dependencies into /zig-out in this folder. Use --prefix/-p to choose another output directory, and use the -Ddesk option to additionally replace the contents of your ship’s desk with your source desk.

$ cd urbit-mcp
$ zig build -Ddesk=~/path/to/zod/mcp

> |commit %mcp
> |install our %mcp

2. Authentication Setup

Get your ship’s web login code from the Dojo:

> +code
lidlut-tabwed-pillex-ridrup
~zod:dojo>

Authenticate and get session cookie:

curl -i http://localhost:80/~/login -X POST -d "password=lidlut-tabwed-pillex-ridrup"

Extract the cookie from the set-cookie header, which will look like this:

urbauth-~your-ship=0v3.j2062.1prp1.qne4e.goq3h.ksudm

3a. Register with Codex

Simply add this to your ~/.codex/config.toml:

[mcp_servers.zod]
enabled = true
url = "http://localhost:80/mcp"
http_headers = { "Cookie" = "urbauth-~your-ship=0v3.j2062.1prp1.qne4e.goq3h.ksudm" }

3b. Register with Claude Code

Add the MCP server to Claude using HTTP transport:

claude mcp add --transport http zod http://localhost:80/mcp --header "Cookie: urbauth-~your-ship=0v3.j2062.1prp1.qne4e.goq3h.ksudm" --scope user

Usage

Tools

Just ask! You can see the default tools here.

You can ask your LLM to add new Tools. Give it a description (and ideally, examples) and it will do its best, or provide a Hoon thread for it to adapt to run in %mcp-server. Threads in %mcp-server must be of signature $-((map @t argument:tool:mcp) shed:khan).

Managed Aqua runs

aqua/start starts a Spider thread without waiting for it to finish. Pass desk, path (for example /ted/ph/add), and optionally arg as raw Hoon. The ship must have %aqua running with a pill loaded.

aqua/pill loads that pill. It builds a brass pill with prime and cache on, pokes it into %aqua, and returns Dojo’s output once %aqua has the pill. Pass desks to include desks besides the base desk, and base to name a base desk other than %base. The tool first checks that %aqua is running from the %base desk; if not, it returns an error that says how to start it. Building and priming a pill takes minutes.