@8ux-co/eelzap-mcp-server
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., "@@8ux-co/eelzap-mcp-servercreate a new blog post titled 'Hello World'"
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.
@8ux-co/eelzap-mcp-server
Connect your AI assistant to Eel Zap CMS. Create collections, manage content, upload media, and publish — all through natural language.
Works with Claude Code, Cursor, VS Code, Codex, and Claude Desktop.
Quick Start
With the CLI (recommended):
npx @8ux-co/eelzap-mcp-server installWith Claude Code:
claude mcp add --transport stdio eelzap \
--env EELZAP_API_KEY=secret_your_key_here \
-- npx -y @8ux-co/eelzap-mcp-serverFor other tools, see the Installation Guides below.
Related MCP server: Storyblok MCP Server
Installation Guides
Claude Code
CLI method:
npx @8ux-co/eelzap-mcp-server install --tool claude-codeManual method — Project scope (.mcp.json):
Create .mcp.json in your project root:
{
"mcpServers": {
"eelzap": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@8ux-co/eelzap-mcp-server"],
"env": {
"EELZAP_API_KEY": "secret_your_key_here"
}
}
}
}Manual method — User scope (~/.claude.json):
Add to the mcpServers section in ~/.claude.json:
{
"mcpServers": {
"eelzap": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@8ux-co/eelzap-mcp-server"],
"env": {
"EELZAP_API_KEY": "secret_your_key_here"
}
}
}
}Using claude mcp add:
claude mcp add --transport stdio eelzap \
--env EELZAP_API_KEY=secret_your_key_here \
-- npx -y @8ux-co/eelzap-mcp-serverCursor
CLI method:
npx @8ux-co/eelzap-mcp-server install --tool cursorManual method — Project scope:
Create .cursor/mcp.json in your project root:
{
"mcpServers": {
"eelzap": {
"command": "npx",
"args": ["-y", "@8ux-co/eelzap-mcp-server"],
"env": {
"EELZAP_API_KEY": "secret_your_key_here"
}
}
}
}Manual method — Global scope:
Create or edit ~/.cursor/mcp.json with the same structure.
VS Code
CLI method:
npx @8ux-co/eelzap-mcp-server install --tool vscodeManual method:
Create .vscode/mcp.json in your project root:
{
"servers": {
"eelzap": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@8ux-co/eelzap-mcp-server"],
"env": {
"EELZAP_API_KEY": "secret_your_key_here"
}
}
}
}Important: VS Code uses "servers" as the top-level key, not "mcpServers".
Codex
CLI method:
npx @8ux-co/eelzap-mcp-server install --tool codexManual method:
Add to ~/.codex/config.toml (or .codex/config.toml for project scope):
[mcp_servers.eelzap]
command = "npx"
args = ["-y", "@8ux-co/eelzap-mcp-server"]
enabled = true
[mcp_servers.eelzap.env]
EELZAP_API_KEY = "secret_your_key_here"Claude Desktop
CLI method:
npx @8ux-co/eelzap-mcp-server install --tool claude-desktopManual method:
Edit the config file at:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/claude/claude_desktop_config.json
Add to the mcpServers section:
{
"mcpServers": {
"eelzap": {
"command": "npx",
"args": ["-y", "@8ux-co/eelzap-mcp-server"],
"env": {
"EELZAP_API_KEY": "secret_your_key_here"
}
}
}
}Restart Claude Desktop after saving.
CLI Commands
Command | Description |
| Interactive setup for any supported tool |
| Change the API key for an existing installation |
| Remove the eelzap entry from a tool's config |
| Show all detected installations and their connection status |
| Diagnose common configuration issues |
Examples:
# Install with flags (non-interactive):
npx @8ux-co/eelzap-mcp-server install \
--tool claude-code \
--scope project \
--api-key secret_xxx
# Update the API key for a specific tool:
npx @8ux-co/eelzap-mcp-server switch-key --tool cursor
# Check what's configured and whether it's working:
npx @8ux-co/eelzap-mcp-server status
# Run diagnostics:
npx @8ux-co/eelzap-mcp-server doctorConfiguration
Environment Variables
Variable | Required | Default | Description |
| Yes | — | Your API key. Starts with |
| No |
| API base URL. Override for self-hosted or local development. |
| No |
| Path prefix. Set to |
API Key Types
Key prefix | Access level | Use case |
| Full read/write | Creating content, managing collections, uploading media, publishing |
| Read-only | Querying published content via the delivery API only |
For MCP server usage, you almost always want a secret key since the whole point is to manage content through your AI assistant.
Local Development
If you're running the CMS locally:
"env": {
"EELZAP_API_KEY": "secret_your_key",
"EELZAP_BASE_URL": "http://localhost:5041",
"EELZAP_PATH_PREFIX": "/api/public/v1"
}Available Tools
Sites (1 tool)
Tool | Description |
| Get the current site associated with your API key |
Collections (5 tools)
Tool | Description |
| List all collections in the site |
| Get a collection by ID |
| Create a new collection |
| Update a collection's name or key |
| Delete a collection and all its items |
Collection Fields (5 tools)
Tool | Description |
| List all fields in a collection |
| Add a new field to a collection |
| Update a field's configuration |
| Remove a field from a collection |
| Change the display order of fields |
Collection Sections (4 tools)
Tool | Description |
| List all sections in a collection |
| Create a new section to group fields |
| Update a section's name |
| Delete a section |
Items (7 tools + 7 versioning tools)
Tool | Description |
| List items in a collection (with pagination and search) |
| Get a single item by ID |
| Create a new item in a collection |
| Update an item's field values |
| Delete an item |
| Publish an item (makes it available via delivery API) |
| Unpublish an item |
Item Versioning (7 tools)
Tool | Description |
| List version history for an item |
| Get details of a specific version |
| Create a draft from the current published version |
| Update draft field values |
| Discard the current draft (non-destructive) |
| Publish the draft as the live version |
| Create a draft from a historical version |
Documents (5 tools + 7 versioning tools)
Tool | Description |
| List all documents (singletons like homepage, about page) |
| Get a document by ID |
| Create a new document |
| Update a document's name or key |
| Delete a document |
Document Fields (5 tools)
Tool | Description |
| List all fields in a document |
| Add a new field to a document |
| Update a field's configuration |
| Remove a field from a document |
| Change the display order of fields |
Document Sections (4 tools)
Tool | Description |
| List all sections in a document |
| Create a new section to group fields |
| Update a section's name |
| Delete a section |
Document Values (2 tools)
Tool | Description |
| Get all field values for a document |
| Set field values for a document |
Document Publishing (2 tools)
Tool | Description |
| Publish a document |
| Unpublish a document |
Document Versioning (7 tools)
Tool | Description |
| List version history for a document |
| Get details of a specific version |
| Create a draft from the current published version |
| Update draft field values |
| Discard the current draft (non-destructive) |
| Publish the draft as the live version |
| Create a draft from a historical version |
Media (7 tools)
Tool | Description |
| List all media assets |
| Get a media asset by ID |
| Upload media from a URL |
| Update media metadata (alt text, title) |
| Delete a media asset |
| Publish a media asset |
| Unpublish a media asset |
SEO (4 tools)
Tool | Description |
| Get SEO metadata for a collection item |
| Set SEO metadata for a collection item, including Schema.org structured data |
| Get SEO metadata for a document |
| Set SEO metadata for a document, including Schema.org structured data |
Delivery API (5 tools)
Tool | Description |
| List published collections (public API) |
| Get a published collection (public API) |
| List published items in a collection (public API) |
| Get a published item (public API) |
| Get a published document (public API) |
What Can You Do?
Once connected, try asking your AI assistant:
Content Creation
"Create a blog collection with title, content, author, and featured image fields"
"Add 5 blog posts about web development best practices"
"Create an About page document with hero title, description, and team section"
Content Management
"List all my collections and their field schemas"
"Update the hero title on my homepage to 'Build faster with AI'"
"Publish all draft items in the blog collection"
Media
"Upload this image from URL and set it as the featured image for my latest blog post"
"List all media assets and show me which ones are unpublished"
SEO
"Set SEO metadata for all blog posts — generate meta titles and descriptions based on the content"
"Check which items are missing SEO metadata"
Site Discovery
"Show me the structure of my site — all collections, documents, and their fields"
"What content types do I have? List everything."
Content Delivery
"Fetch my published blog posts and show me what the delivery API returns"
"Check if the homepage document is published and what data it serves"
Troubleshooting
"EELZAP_API_KEY is required"
The server can't find your API key. Make sure it's set in the env section of your MCP config (all tools, including Codex via [mcp_servers.eelzap.env]).
"Connection refused" or "ECONNREFUSED"
The server can't reach the API. Check:
Your
EELZAP_BASE_URLis correct (default:https://api.eelzap.com)If using local dev, ensure the CMS app is running on the expected port
"401 Unauthorized"
Your API key is invalid or expired. Generate a new one from the Eel Zap dashboard (Settings > API Keys) and run eelzap-mcp switch-key.
"403 Forbidden"
You're using a public key (public_) for a write operation. Switch to a secret key (secret_).
Server not appearing in your tool
Claude Code: Restart Claude Code or run
/mcpto check server statusCursor: Restart Cursor; check Settings > Tools & MCP for server status
VS Code: Check the MCP panel; try "MCP: List Servers" from the command palette
Codex: Restart Codex; ensure the TOML config is at
~/.codex/config.tomlClaude Desktop: Fully quit and reopen Claude Desktop (config changes require restart)
Tools not loading / "No tools available"
The server starts but tools aren't registered. Run eelzap-mcp doctor to diagnose, or check the server logs for errors during startup.
Development
git clone https://github.com/8ux-co/eelzap-mcp-server.git
cd eelzap-mcp-server
npm install
npm run build
npm testRun locally during development:
EELZAP_API_KEY=secret_... npx tsx src/index.tsTest with MCP Inspector:
EELZAP_API_KEY=secret_... npx @modelcontextprotocol/inspector npx tsx src/index.tsThis server cannot be installed
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
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/8ux-co/eelzap-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server