Marvin MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Marvin MCPlist entries in the blog collection"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Marvin MCP
Official Model Context Protocol server for Marvin CMS.
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.
MCP Client
↓ stdio
marvin-mcp
↓
@inneropen/marvin-sdk
↓ HTTPS
Marvin APIProject Relationship
marvin-cli ──┐
├──> marvin-sdk ──> Marvin API
marvin-mcp ──┘marvin-cli is for humans and shells. marvin-mcp is for MCP-compatible AI clients. marvin-sdk remains the canonical programmatic Marvin client.
Related MCP server: Directus MCP Server
Installation
After publication:
npx -y @inneropen/marvin-mcpFor local development:
npm install
npm run devConfiguration
Required:
MARVIN_API_URL
MARVIN_SITE_CLIENT_TOKEN
MARVIN_WORKSPACE_SLUGOptional:
MARVIN_MCP_LOG_LEVEL=silent|error|warn|info|debug
MARVIN_MCP_READ_ONLY=true|falseDefault: MARVIN_MCP_READ_ONLY is true. Current SDK-backed mutation tools are not implemented, so write tools are absent either way in this first release.
Logs go to stderr. Tokens are never printed intentionally and are redacted from structured logs/errors.
Tools
Self-description:
Tool | Purpose |
| Describe Marvin MCP capabilities and SDK capability support |
Read tools:
Tool | Purpose |
| Get workspace info and site settings |
| List entries with |
| Get one entry by slug |
| List collections |
| Get one collection by slug |
| Get entries in a collection |
| List asset metadata |
| List reusable resources |
| Get one resource by slug |
No destructive or generic API proxy tools are exposed.
Resources
URI | Purpose |
| Capability and SDK inventory |
| Workspace info |
| Public site settings |
| Entry types inferred from listed entries |
| Collection summaries |
| Resource summaries |
| Entry details |
| Collection details |
| Resource details |
Prompts
Prompt | Purpose |
| Inspect structure and recommend non-destructive improvements |
| Guide drafting a page without automatic publishing |
| Draft a release/update content item |
| Audit entries, collections, resources, and site settings |
| Review collection organization |
| Review asset metadata quality |
| Review reusable resources |
Capabilities
Marvin MCP is organized by Marvin capability under src/capabilities/*. Each capability owns its tools, resources, and prompts.
Capability | MCP Surface |
Workspace |
|
Entries |
|
Entry Types |
|
Collections | collection tools, |
Assets |
|
Resources | resource tools, |
Capability |
|
The SDK capability inventory and architecture review are documented in docs/CAPABILITY_INVENTORY.md.
Client Examples
Generic stdio MCP client:
{
"mcpServers": {
"marvin": {
"command": "npx",
"args": ["-y", "@inneropen/marvin-mcp"],
"env": {
"MARVIN_API_URL": "https://marvin.example.com",
"MARVIN_SITE_CLIENT_TOKEN": "${MARVIN_SITE_CLIENT_TOKEN}",
"MARVIN_WORKSPACE_SLUG": "example-workspace",
"MARVIN_MCP_READ_ONLY": "true"
}
}
}
}Claude Code and other clients use the same command/env shape, though exact config file locations differ by client.
Development
npm run dev
npm run build
npm run typecheck
npm run lint
npm testMCP Inspector:
npm run inspectIntegration tests are opt-in and read-only:
MARVIN_MCP_INTEGRATION_TESTS=true npm testThey also require MARVIN_API_URL, MARVIN_SITE_CLIENT_TOKEN, and MARVIN_WORKSPACE_SLUG.
Capability Matrix
Capability | SDK support | Authentication | MCP mapping | Read/write | Implemented | Limitations |
Workspace info/site settings |
| Site token | Tool and resources | Read | Yes | API credentials enforce access |
List/get entries | Publishing | Site token | Tools and | Read | Yes | SDK source does not send |
Collections | Publishing | Site token | Tools and resources | Read | Yes | Missing collections return |
Assets | Publishing | Site token |
| Read | Yes | Metadata only; no binary payloads |
Resources | Publishing | Site token | Tools and resources | Read | Yes | Resource entries method exists but is not a first-release tool |
Entry types | Platform SDK has | Platform user auth |
| Read | Partial | Inferred from entries in first release |
Platform entries/assets/forms/etc. |
| User token/session | Future editor capabilities | Read/write | No | Requires auth, permission-aware registration, and mutation safety design |
Administration | Platform admin/user/workspace/API client/webhook/task modules | User token/session | Future admin capabilities | Read/write | No | High-impact/destructive and secret-adjacent operations are intentionally excluded |
SDK Capability Gaps
Current @inneropen/marvin-sdk 2.0.0-next.17 publishing client is read-focused. The installed declarations expose no create, update, add-to-collection, or publish entry methods, so this MCP server does not implement write tools and does not bypass the SDK with direct fetch() calls.
This prerelease returns null for missing entries and collections. The MCP server translates those results into structured not-found errors.
The SDK does not expose permission metadata for permission-aware discovery. First release behavior relies on MARVIN_MCP_READ_ONLY and Marvin API authorization failures.
Security
Security decisions:
Read-only mode defaults to
true.No arbitrary HTTP request, shell, SQL, migration, plugin, or secret-management tools.
No generic
marvin_api_request.Inputs are validated with Zod.
Outputs are normalized into JSON-safe structures.
Asset storage internals and tokens are not exposed.
Prompts never instruct automatic publishing.
Final authorization is enforced by Marvin API credentials.
Planned Streamable HTTP
The first transport is stdio. Server creation, capability registration, and transport connection are separated so Streamable HTTP can be added later without rewriting the tool/resource/prompt layer.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/InnerOpen/marvin-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server