acms

This MCP server provides access to a-blog cms via MCP (Model Context Protocol) to search and retrieve content, entry details, module information, and Twig template snippets. The server exposes tools such as acms_find_entries for keyword-based content search with pagination, acms_get_entry to fetch detailed information for a specific entry, acms_modules to list available modules, acms_get_module_detail to obtain details about a module, and acms_get_snippet to fetch Twig template snippets for modules (30+ V2 modules). To use it, configure the MCP server in your workspace (via .cursor/mcp.json or your MCP runner) and point ACMS_BASE to your a-blog cms instance while supplying a valid ACMS_X_API_KEY. The MCP package is intended to be run through npx (as shown in the example) so you can start the server without a local install if you prefer. Once running, you can call the available tools by their names and pass the required parameters as described in the README, enabling you to search, inspect, and generate templates or details for your content and modules.

Prerequisites:

• Node.js and npm installed on your machine (or use a container with Node.js).
• Access to a-blog cms with API (V2) enabled and a valid API key.

Installation steps:

1. Ensure you have Node.js and npm installed. Verify with: node -v npm -v
2. Use npx to run the MCP server without a local install, as shown in the configuration:
   • Create or update your MCP config (see mcp_config below) with ACMS_BASE and ACMS_X_API_KEY.
   • You can run the server directly via: npx -y acms-mcp-server@beta (or use the exact command from your mcp_config).
3. If you prefer to pin the configuration, place the mcp config in .cursor/mcp.json or your project’s MCP config location, matching the structure provided in the example: { "mcpServers": { "acms": { "command": "npx", "args": ["-y", "acms-mcp-server@beta"], "env": { "ACMS_BASE": "https://example.com/", "ACMS_X_API_KEY": "xxxxxxxxxxxxx" } } } }
4. Start the server through your MCP runner. The server will expose the tools listed in the README (acms_find_entries, acms_get_entry, acms_modules, acms_get_module_detail, acms_get_snippet).

Optional: If you’re using a workflow that requires explicit installation, you can install the package locally as a dev dependency and run it via a script, but using npx as shown is the recommended approach for quick setup.

Tips and common issues:

• Ensure the a-blog cms API (V2) is enabled in the ACMS settings and that you’ve generated an API key (ACMS_X_API_KEY).
• The MCP relies on modules provided by the a-blog cms MCP ecosystem; for module listing and details, you may need the McpModuleApi extension installed in ACMS.
• In the MCP config, ACMS_BASE must be the base URL of your a-blog cms site (including protocol and trailing slash).
• The acms_get_snippet tool surfaces Twig template snippets for many V2 modules; combine it with acms_get_module_detail for complete template generation.
• If you encounter network or authentication errors, verify that the API key is valid and that the ACMS_BASE URL is reachable from the environment where the MCP server runs.