The Zurvo field guide

Step 1

Connect your client

Choose your MCP client. Zurvo gives you the exact configuration it expects—no tool names to memorize.

CodexShared by Codex CLI, IDE, and desktop

1
Open MCP servers in Codex settings or ~/.codex/config.toml.
2
Add the Zurvo entry below and save.
3
Restart Codex, then open /mcp to confirm the connection.

Zurvo asks you to sign in only when an account-owned action needs approval.

config.toml

[mcp_servers.zurvo]
enabled = true
url = "https://zurvo.sh/mcp"

Step 2

Ask naturally

Talk to your AI client normally. It decides which Zurvo tool fits the job and asks for authorization if needed.

Share an output

“Publish this as a Zurvo artifact and give me the link.”

Make it public

“Publish this as a public Zurvo capability link for 24 hours.”

Move the work

“Create a Zurvo resume link with the current state and next steps.”

Continue elsewhere

“Import this Zurvo handoff, verify the workspace, and continue.”

Step 3

Use the result

Zurvo returns something designed for the next person—or the next agent—to use immediately.

For delivery

Artifact

A browser-ready result someone can preview or download: reports, Markdown, JSON, HTML, PDFs, and images.

https://zurvo.sh/artifact/…

For continuation

Handoff

Structured working state another person or agent can import: goal, decisions, workspace facts, and next steps.

https://zurvo.sh/handoff/…#password=…

One tool result, one link. Clients render the returned URL directly. A receiving agent should treat a handoff as context, verify the workspace and assumptions, then continue.

Keep nearby

Reference, when you need it

The setup above is enough for normal use. These details explain the boundaries.

Access and expiry

PublicAnyone with the active link can open it.

PasswordRecipients need the password or an intentionally embedded fragment.

Email allowlistOnly verified recipients on the list can open it.

Expiry and revocationAccess ends automatically or when the owner revokes it.

MCP tools

publish_artifact

Encrypt an output server-side and return one password-protected link by default on Pro.

get_artifact

Read artifact metadata and current URLs.

list_recent_artifacts

List active artifacts owned by the account.

revoke_artifact

End access before an artifact expires.

create_handoff

Send title, goal, currentState, and nextStep; receive a password-protected resume URL by default on Pro.

import_handoff

Import a handoff from its HTTPS resume link.

list_handoffs

List handoffs owned by the account.

revoke_handoff

End access to an active handoff.

Authorization

OAuth protects account-owned actions. Publishing, listing, and revoking require approval. Anonymous MCP access is limited to initialization, tool discovery, and supported public handoff imports.

Server encryption

MCP artifacts and handoffs are encrypted inside Zurvo before object storage. On Pro, they are password-protected by default; Zurvo generates the password when one is not supplied, and only an explicit public request opts out. This protects stored objects and recipient access, but it is not end-to-end encryption: treat the complete embedded-password link as a secret.