MCP server for ElmapiCMS. Manage collections, fields, content, assets, and webhooks via AI agents. https://elmapicms.com. Runs locally from the @elmapicms/mcp-server npm package. Needs 3 environment variables to run.
Manages Elmapi assets — list, get, upload, delete, and bulk operations for files and media. Use when uploading images, managing file metadata, or working with the Elmapi asset library.
Canonical contract for integrating Elmapi project user auth in any frontend. Enforces correct login, refresh, logout, and session semantics. Use whenever implementing or reviewing auth flows (custom, NextAuth, Nuxt, Astro, mobile).
Manages Elmapi collections and fields — create, update, delete, and reorder collections and their field schemas. Use when programmatically managing content schemas, field types, or collection settings.
Works with Elmapi content entries — list, get, create, update, patch, delete, bulk operations, and optional translation linking. Use when building pages that display, filter, paginate, or mutate content from Elmapi collections.
Handles Elmapi SDK errors — error class hierarchy, properties, and try/catch patterns. Use when handling API errors, debugging failed requests, or implementing error boundaries with Elmapi.
Builds Elmapi-backed sites schema-first using the Elmapi/ElmapiCMS MCP — create collections, fields, and seed content before or while implementing pages. Use when the user builds a site, landing page, or CMS-driven UI with Elmapi (Next.js, Nuxt, Astro, or any @elmapicms/js-sdk app) and has the Elmapi MCP enabled…
Integrates Elmapi with Next.js — server components, SSG/ISR, server actions, route handlers, auth (password + social idtoken), and middleware. Use when building a Next.js app that fetches or mutates content from Elmapi.
Integrates Elmapi with Nuxt — server routes, composables, SSG/ISR, plugins, middleware, and Pinia stores. Use when building a Nuxt app that fetches or mutates content from Elmapi.
Sets up and configures the ElmapiCMS JS SDK client. Use when installing @elmapicms/js-sdk, creating a client, configuring baseUrl, project API tokens, environment variables, or troubleshooting SDK connectivity.
Implements Elmapi project end-user authentication — sign up, password sign-in, OIDC idtoken (social) sign-in, token refresh, sign out, email verification, user API keys, and auth state management. Use when building login/register flows or managing end-user sessions. Not for CMS staff user administration or OAuth…