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.
LABSCO SUMMARY
Saving never publishes — the live version changes only when you say so.
Both write paths state it outright: an update or a patch leaves the published snapshot serving the public API until a publish call mints a new immutable version. That makes the version list the real history, revertible and relabellable without the payload changing. Three sharp edges are named in the tools themselves, and each one costs an afternoon if you find it the hard way: a URL or permalink field has to be of type slug rather than text, a relation is written as the related entry's UUID and never as the nested object a read gave you, and a translation group can be linked through the API but only split in the dashboard.
What it is
A headless CMS client covering a project's schema, its content entries and their published versions, its assets and its webhooks. Everything is scoped to one ElmapiCMS project, addressed by its UUID.
What you get
- Project information and locales, with the default locale set and new locale codes added — removing a locale is deliberately left to the dashboard (get_project, add_project_locale, set_default_project_locale).
- Collections listed, fetched with their full field schema, created together with their fields in one request, renamed and reordered; fields added, updated and reordered (list_collections, get_collection, create_collection, update_collection, reorder_collections, create_field, update_field, reorder_fields).
- Entries queried with a where clause carrying 13 operators, OR groups and relation filtering, alongside sorting, pagination, count and first (list_entries, get_entry).
- Writes in the shape the change actually is: a full replace by PUT, a partial merge by PATCH that touches only the fields you send, and a soft delete to trash that the admin panel can restore (create_entry, update_entry, patch_entry, delete_entry).
- Publishing as its own act: publishing mints an immutable version and makes it live, unpublishing clears the live pointer while keeping every historical version, and a dirty draft can be thrown away back to the published state (publish_entry, unpublish_entry, discard_entry_draft).
- Version history as a first-class record — listed newest first with number, label, description and publisher, fetched as a raw snapshot, reverted to and republished, or relabelled while the payload itself stays immutable (list_entry_versions, get_entry_version, revert_entry_version, update_entry_version_label).
- Atomic bulk operations where one failure rolls the whole batch back rather than leaving a half-finished import (bulk_create_entries, bulk_update_entries, bulk_delete_entries).
- Two entries in different locales merged into one translation group (link_entry_translation).
- Assets listed, fetched by UUID or filename, uploaded singly or in atomic batches from absolute local paths, updated in bulk and deleted (list_assets, get_asset, upload_asset, bulk_upload_assets, bulk_update_asset_metadata, delete_asset).
- Webhooks for content and auth events, with their delivery logs (list_webhooks, get_webhook, create_webhook, update_webhook, delete_webhook, list_webhook_logs).
Requirements
Three values: ELMAPI_BASE_URL pointing at your instance's API root, a project Sanctum token from Project Settings, API Tokens in ELMAPI_API_KEY, and the project UUID in ELMAPI_PROJECT_ID. Launch with npx -y @elmapicms/mcp-server over stdio. Abilities on the token decide what works — adding or changing a locale needs admin, and publishing, unpublishing, discarding a draft, reverting a version and linking translations all need update. Against a local instance with a self-signed certificate, fix the CA trust rather than turning TLS verification off in a config you might ship.
Setup effort
One command plus a key — npx -y @elmapicms/mcp-server, then supply credentials
USE CASES
01
Setting up a collection and its whole schema at once
Declare the fields with the collection in one request, so there is no half-built content type in between.
02
Editing live content without changing what visitors see
A patch touches the draft only; the published snapshot keeps serving until you publish.
03
Rolling back a change that went out wrong
Read the version history, then restore the draft from an earlier snapshot and publish it as a new version.
04
Importing a batch of content
Create them atomically so one malformed item does not leave the collection half-populated.
05
Launching a site in a second language
Add the locale, create the translated entry, then link it to its counterpart.
06
Notifying another system when content changes
Point a webhook at it and read the delivery logs when something does not arrive.
40 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
bulk_create_entries
Create multiple content entries atomically. If one item fails, the whole request is rolled back.
bulk_delete_entries
Delete multiple content entries atomically by UUID. If one delete fails, no entries are deleted.
bulk_update_asset_metadata
Update metadata for multiple assets atomically by UUID. If one item fails, all updates are 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_upload_assets
Upload multiple local files as assets atomically. If one upload fails, all uploads are rolled back.
create_collection
Create a new collection. Optionally include field definitions to create the collection with its full schema in a single request.
create_entry
Create a new content entry in a collection
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.
create_webhook
Create a webhook for content and auth events
delete_asset
Delete an asset by UUID
delete_entry
Soft-delete a content entry (moves to trash). Can be restored from the admin panel.
delete_webhook
Delete a webhook by UUID
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.
get_asset
Get an asset by its UUID or by filename.
get_collection
Get a single collection with its full field schema by slug
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.
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'.
get_project
Get information about the current Elmapi project (name, uuid, default_locale, locales, etc.)
get_webhook
Get a webhook by UUID
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.
list_assets
List assets in the project with optional pagination.
list_collections
List all collections in the project
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.
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.
list_webhook_logs
List delivery logs for a webhook
list_webhooks
List all webhooks configured for the current project
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.
reorder_collections
Update the display order of collections
reorder_fields
Update the display order of fields within a collection
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.
set_default_project_locale
Set the project's default locale. Adds the locale to the list if it was missing. Requires admin API ability.
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.
update_collection
Update the name and slug of an existing 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.
update_entry_version_label
Update a version's editable label and/or description. The snapshot payload itself is immutable.
update_field
Update an existing field on a collection
update_webhook
Update a webhook by UUID
upload_asset
Upload a local file as an asset. Provide the absolute file path.
BEFORE YOU INSTALL
What to know first
Tools you get
40 tools when we connected. Token abilities decide what works: a read-only token leaves every tool listed but most failing, while create, update, delete and admin abilities unlock the rest. Removing a locale is intentionally not exposed.
Requires
- npx on PATH
- ELMAPI_API_KEY in your environment
- ELMAPI_PROJECT_ID in your environment
- ELMAPI_BASE_URL in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 40 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @elmapicms/mcp-serverMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"elmapicms": {
"command": "npx",
"args": [
"-y",
"@elmapicms/mcp-server"
],
"env": {
"ELMAPI_BASE_URL": "<YOUR_SERVER_URL>/api",
"ELMAPI_API_KEY": "<YOUR_ELMAPI_API_KEY>",
"ELMAPI_PROJECT_ID": "<YOUR_ELMAPI_PROJECT_ID>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add elmapicms -e ELMAPI_BASE_URL=<YOUR_SERVER_URL>/api -e ELMAPI_API_KEY=<YOUR_ELMAPI_API_KEY> -e ELMAPI_PROJECT_ID=<YOUR_ELMAPI_PROJECT_ID> -- npx -y @elmapicms/mcp-server
