Elmapicms Mcp Server
About
An MCP server that connects AI agents like Cursor and Claude Code to your ElmapiCMS instance. Manage collections, fields, content entries, and assets programmatically through natural language.
Details
- Author
- elmapicms
- Downloads
- 233
- Categories
- Developer Tools, Other, Automation
Jump to
- Connects AI agents to ElmapiCMS
- Manage collections programmatically
- Manage fields programmatically
- Manage content entries programmatically
- Manage assets programmatically
- Natural language interaction
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Elmapicms Mcp ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
—
get_project
Get information about the current Elmapi project (name, uuid, default_locale, locales, etc.)
add_project_locale
Add a locale code (e.g. tr, es) to the project. Requires admin API ability. Codes are lowercased. Call when setting up a multilingual site before creating translated content.
set_default_project_locale
Set the project's default locale. Adds the locale to the list if it was missing. Requires admin API ability.
list_collections
List all collections in the project
get_collection
Get a single collection with its full field schema by slug
create_collection
Create a new collection. Optionally include field definitions to create the collection with its full schema in a single request.
update_collection
Update the name and slug of an existing collection
reorder_collections
Update the display order of collections
create_field
Add a new field to a collection. URL/permalink fields MUST use type "slug" (never "text"). Attach with options.slug.field to the source text field name (e.g. "title"), and set required + unique validations. See elmapicms://field-types for options and patterns.
update_field
Update an existing field on a collection
reorder_fields
Update the display order of fields within a collection
list_entries
List content entries for a collection with advanced filtering, sorting, and pagination. Use the 'where' parameter for powerful queries. Read the 'query-reference' resource for full documentation on operators and examples. state='published' (default) returns each entry's published snapshot fields (not live draft edits). state='draft' returns entries whose state is draft.
get_entry
Get a single content entry by UUID. Response includes uuid, locale, published_at, and a `fields` object (custom field values — not a nested `data` key). Relation fields appear as nested entry objects (one-to-one) or arrays of entries (one-to-many), not as bare UUIDs. state='published' (default) returns the published snapshot; state='draft' returns live draft fields for draft entries. A published entry with unpublished draft edits still serves its last snapshot under state='published' until publish_entry.
create_entry
Create a new content entry in a collection
update_entry
Replace an existing content entry (HTTP PUT). Sends the full `data` payload; required fields (e.g. title, slug) must be included. Saves NEVER change the publish state — if the entry has a published version, the public API keeps serving that snapshot under state=published until you explicitly call `publish_entry`. Use `patch_entry` for partial updates and `publish_entry`/`unpublish_entry` to control visibility.
patch_entry
Partially update a content entry (HTTP PATCH). Only include fields you want to change (e.g. relations, one field). Saves NEVER change the publish state — call `publish_entry` explicitly to mint a new version. Prefer this over `update_entry` when you are not replacing the entire entry.
publish_entry
Mint a new immutable version from the entry's current draft and make it the live published version. After this call, state=published reads from the public API will return the new snapshot and `is_draft_dirty` is reset to false.
unpublish_entry
Clear the live published pointer for an entry. The entry becomes invisible under state=published in the public API, but all historical versions are retained and still accessible via `list_entry_versions` / `get_entry_version`.
discard_entry_draft
Discard unpublished draft changes and restore the draft from the current published version (or clear draft when unpublished). Does not delete the entry or remove historical versions. Requires **update** ability.
delete_entry
Soft-delete a content entry (moves to trash). Can be restored from the admin panel.
link_entry_translation
Merge two entries in the same collection into one translation group (same as dashboard “link translation”). Both entries must exist, belong to this collection, and have **different** locales. There is no unlink via API — use the dashboard if you need to split a group. Requires an API key with **update** ability.
bulk_create_entries
Create multiple content entries atomically. If one item fails, the whole request is rolled back.
bulk_update_entries
Update multiple content entries atomically by UUID. If one item fails, all updates are rolled back. Saves never change publish state — call `publish_entry` per UUID to mint new versions after bulk updates.
bulk_delete_entries
Delete multiple content entries atomically by UUID. If one delete fails, no entries are deleted.
list_entry_versions
List all published versions for a content entry (newest first). Each version is an immutable snapshot taken at publish time. Response includes version_number, label, description, published_at, created_by, and is_current_published for each version.
get_entry_version
Fetch a single version's metadata and raw snapshot payload. The snapshot contains the saved field values in restoration format; for API-rendered content use `get_entry` with state='published'.
revert_entry_version
Restore the draft to a previous version's snapshot and publish it as a new version. The current unpublished draft is replaced. Returns the new version number.
update_entry_version_label
Update a version's editable label and/or description. The snapshot payload itself is immutable.
list_assets
List assets in the project with optional pagination.
get_asset
Get an asset by its UUID or by filename.
upload_asset
Upload a local file as an asset. Provide the absolute file path.
bulk_upload_assets
Upload multiple local files as assets atomically. If one upload fails, all uploads are rolled back.
bulk_update_asset_metadata
Update metadata for multiple assets atomically by UUID. If one item fails, all updates are rolled back.
delete_asset
Delete an asset by UUID
list_webhooks
List all webhooks configured for the current project
get_webhook
Get a webhook by UUID
create_webhook
Create a webhook for content and auth events
update_webhook
Update a webhook by UUID
delete_webhook
Delete a webhook by UUID
list_webhook_logs
List delivery logs for a webhook
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"elmapicms mcp server": {
"elmapicms": {
"command": "npx",
"args": [
"@elmapicms/mcp-server"
],
"env": {
"ELMAPI_API_URL": "https://your-domain.com/api",
"ELMAPI_API_KEY": "your-api-key",
"ELMAPI_PROJECT_ID": "your-project-uuid"
}
}
}
}
}
McpServers
{
"elmapicms": {
"command": "npx",
"args": [
"@elmapicms/mcp-server"
],
"env": {
"ELMAPI_API_URL": "https://your-domain.com/api",
"ELMAPI_API_KEY": "your-api-key",
"ELMAPI_PROJECT_ID": "your-project-uuid"
}
}
}
Connect Cursor, Claude Code, or any MCP-compatible tool directly to your ElmapiCMS instance. Manage collections, content, and assets through natural language.
An MCP (Model Context Protocol) server that connects AI agents likeCursorandClaude Codeto yourElmapiCMSinstance. Manage collections, fields, content entries, assets, and webhooks programmatically through natural language.
Add this to your Cursor MCP settings (~/.cursor/mcp.json):
{ "mcpServers": { "elmapicms": { "command": "npx", "args": ["-y", "@elmapicms/mcp-server"], "env": { "ELMAPI_BASE_URL": "https://your-domain.com/api", "ELMAPI_API_KEY": "your-project-api-token", "ELMAPI_PROJECT_ID": "your-project-uuid" } } } }
claude mcp add elmapicms \ -e ELMAPI_BASE_URL=https://your-domain.com/api \ -e ELMAPI_API_KEY=your-project-api-token \ -e ELMAPI_PROJECT_ID=your-project-uuid \ -- npx -y @elmapicms/mcp-server
Local Development (Laravel Herd /.testdomains)
If your instance uses a self-signed certificate (e.g. Laravel Herd), you may need:
"env": { "ELMAPI_BASE_URL": "https://myproject.test/api", "ELMAPI_API_KEY": "your-project-api-token", "ELMAPI_PROJECT_ID": "your-project-uuid", "NODE_TLS_REJECT_UNAUTHORIZED": "0" }
Prefer fixing local CA trust (e.g.node --use-system-ca) over disabling TLS verification in production configs.
- get_project— Get project information (default_locale,locales, etc.)
- add_project_locale— Add a locale code to the project (requiresadmin)
- set_default_project_locale— Set the default locale (requiresadmin)
Removing locales is intentionallynotexposed here (useProject settings → Localizationin the dashboard, or the REST/SDK APIs).
- list_collections— List all collections
- get_collection— Get a collection with its full field schema
- create_collection— Create a collection (with optional batch field creation)
- update_collection— Update a collection's name and slug
- reorder_collections— Reorder collections
- create_field— Add a field to a collection
- update_field— Update a field
- reorder_fields— Reorder fields within a collection
- list_entries— List entries with advanced filtering (wherewith 13 operators, OR groups, relation filtering), sorting, pagination, count, and first
- get_entry— Get a single content entry
- create_entry— Create a content entry
- update_entry— Update a content entry
- patch_entry— Partially update an entry (HTTP PATCH; merge only the fields you send)
- publish_entry— Publish the draft as a new immutable version (update)
- unpublish_entry— Clear the live published pointer; versions retained (update)
- discard_entry_draft— Discard unpublished draft changes (update)
- delete_entry— Soft-delete a content entry (moves to trash)
- bulk_create_entries— Create multiple entries atomically
- bulk_update_entries— Update multiple entries atomically by UUID
- bulk_delete_entries— Delete multiple entries atomically by UUID
- link_entry_translation— Link two entries (different locales) into the same translation group (POST …/link-translation; requiresupdate)
- list_entry_versions— List version history for an entry
- get_entry_version— Fetch one version by number (includes snapshot payload)
- revert_entry_version— Restore draft from a prior snapshot and publish (update)
- update_entry_version_label— Edit label/description on a version; snapshot unchanged (update)
Content API shape:Each entry hasuuid,locale,published_at, andfields(custom field values). Field names arekebab-case.Richtextwrite format followseditor.mode: HTML string or{ html, json }for lexical; markdown string whenmodeismarkdown. MCPcreate_field/create_collection(and richtextupdate_field) default omittededitor.modetomarkdown. Passmode: 'lexical'for Lexical. Never write markdown into a lexical field. Read shape followseditor.outputFormat.Relation fieldsreturn nested entry objects (or arrays for one-to-many) on read; on write send only the related entry’sUUIDornumeric id(never the full nested object from a previousget_entry).get_entrysupportstranslation_locale,exclude,timestamps, andstatequery parameters.
Save ≠ publish:create_entry/update_entry/patch_entrysave the draft only.state=publishedlist/get keep serving the last snapshot until you callpublish_entry.
Asset URLs:The API returnsurl,thumbnail_url, andoriginal_urlas stable links (optional?variant=thumbnailor?variant=original).
- list_assets— List assets with pagination
- get_asset— Get an asset by UUID or filename
- upload_asset— Upload a file as an asset
- bulk_upload_assets— Upload multiple files atomically
- bulk_update_asset_metadata— Update metadata for multiple assets atomically
- delete_asset— Delete an asset
- list_webhooks— List all webhooks for the project
- get_webhook— Get a webhook by UUID
- create_webhook— Create a webhook for content and auth events (name,url,events,sources; optionaldescription,secret,payload,status,collection_ids)
- update_webhook— Update a webhook by UUID (same fields as create)
- delete_webhook— Delete a webhook by UUID
- list_webhook_logs— List delivery logs for a webhook (uuid; optionalpaginate,page)
The server exposes three reference resources that AI agents can read for context:
- Field Types Reference(elmapicms://field-types) — Complete reference of all 16 field types, their options, validations, and common patterns.
- Collections Guide(elmapicms://collections-guide) — Guide for working with collections, singletons, reserved slugs, and best practices.
- Query Reference(elmapicms://query-reference) — Full documentation for content queries:wherefilters with 13 operators, OR groups, relation filtering, sorting, pagination, and examples.
YourprojectAPI token needs the appropriate abilities for the tools you want to use:
Create the token in the ElmapiCMS dashboard underProject settings → API Tokens. Copy theProject IDfrom the project home page orProject settings → API Accesswhen you configure this server.
Each MCP entry connects to a single ElmapiCMS project. To work with multiple projects, add separate entries in your MCP config with different env values.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
MCP server for NomaCMS. Manage collections, fields, content, and assets via AI agents.
Manage your Storyblok CMS using natural language through AI tools.
MCP server for WordPress: connect Claude, ChatGPT, Cursor, and other AI clients to manage content, edit themes, run WP-CLI, and automate self-hosted WordPress sites.
Manage and utilize website content within the DevHub CMS platform
A server for integrating with WordPress sites, enabling content management and interaction via the Model Context Protocol.
Extract, govern, and ship structured content from your codebase.
This server enables AI assistants and other MCP clients to interact with Directus instances programmatically.
Agency-grade MCP server for WordPress Elementor — multi-site fleet management, safe page/widget-level editing, template export/import, version tracking with snapshot/rollback.
An MCP server for WordPress and Elementor, enabling AI assistants to manage content and build pages.
Localization as code — 7 MCP tools to push, pull, translate, extract strings, and search translations. AI-powered, type-safe, 182 languages.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.


