Marvin MCP Server

Marvin MCP server exists for a simple reason — assistants are far more useful when they can act on Marvin directly instead of describing what you should do. Official Model Context Protocol server for Marvin CMS.

What you get

marvin-mcp is the LLM-facing adapter for Marvin. It talks directly to @inneropen/marvin-sdk; it does not shell out to marvin-cli and it does not recreate Marvin API behavior.

What the assistant can call

Once Marvin is connected, these are the calls the assistant has available:

• marvin_describe_capabilities — Describe Marvin MCP capabilities and SDK capability support
• marvin_get_workspace — Get workspace info and site settings
• marvin_list_entries — List entries with entryType, collection, limit, offset
• marvin_get_entry — Get one entry by slug
• marvin_list_collections — List collections
• marvin_get_collection — Get one collection by slug
• marvin_get_collection_entries — Get entries in a collection
• marvin_list_assets — List asset metadata
• marvin_list_resources — List reusable resources
• marvin_get_resource — Get one resource by slug

Configuration and credentials

You will need 4 environment variables: MARVIN_API_URL, MARVIN_SITE_CLIENT_TOKEN, MARVIN_WORKSPACE_SLUG, MARVIN_MCP_READ_ONLY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

@inneropen/marvin-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Marvin's toolset — marvin_describe_capabilities, marvin_get_workspace, marvin_list_entries and 7 more — is a fair guide to whether it matches your workflow. It is maintained by jmashburn; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Marvin.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the marvin mcp server does with a few real requests.