MCP server

Connect any MCP client to your vvd worlds.

vvd runs a Model Context Protocol server at https://vvd.world/api/mcp. Any MCP client can connect to it, and every vvd operation is available as an MCP tool (worlds_list, worlds_create, documents_create, content_apply, worlds_search, …). A connection works as your account and respects your world permissions.

Plans. Building tools and apps is free on every plan. Reading or editing a world's content over MCP, the REST API, or the CLI needs the world to be on the Pro or Studio plan. On other plans those tools reply with an upgrade message instead of your data. See pricing.

Add vvd as a connector

Most MCP clients let you add a remote server from their settings:

Open your client's connectors (or MCP servers) settings and add a custom one.
Name it vvd and set the URL to https://vvd.world/api/mcp.
Choose OAuth sign-in. If there is a client-registration option, leave it on automatic.
Connect. The vvd approval page opens: sign in, then Approve.

The client registers itself, runs a standard OAuth 2.1 sign-in (PKCE), and keeps the connection refreshed. You approve once and stay connected until you revoke it.

Connect with an API key

For a client that takes a header instead of running a sign-in (a headless server, a script), create a key in Settings → API keys and send it as a bearer token:

Authorization: Bearer vvd_live_…

Local stdio (optional)

If your client prefers a local process, the CLI serves MCP over stdio:

vvd login      # once
vvd mcp        # point your client's command at this

This proxies to the same remote endpoint using your stored login.

What a connection can do

The MCP tools mirror the REST operations one to one: list and create worlds, list, create and read documents, apply typed content edits (for example, add a timeline event), manage eras and projects, and search. Creating API keys is intentionally not available over MCP — do that in the app.