acf-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACF_MCP_WP_ROOT | Yes | Absolute path to the WordPress root directory. | |
| ACF_MCP_ACF_JSON_DIR | Yes | Absolute path to the ACF Local JSON directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| acf_pingA | Check server health and return non-secret configuration details. |
| acf_list_field_groupsA | Read all ACF field groups from Local JSON without touching the WordPress database. |
| acf_get_field_groupB | Read one ACF field group by key from Local JSON. |
| acf_create_field_groupB | Create a field group Local JSON file. Backs up an existing file if the key already exists. |
| acf_update_field_groupC | Update a field group Local JSON file by writing the supplied full field group object. |
| acf_delete_field_groupC | Delete a field group Local JSON file by key after creating a backup when possible. |
| acf_validate_field_groupB | Validate a field group payload against the server ACF Local JSON schema without writing files. |
| acf_export_jsonC | Run the whitelisted |
| acf_import_jsonC | Run the whitelisted |
| acf_sync_jsonB | Explicitly sync Local JSON changes to WordPress using |
| acf_list_post_typesA | Read ACF-managed custom post type Local JSON files. |
| acf_create_post_typeC | Create or update an ACF-managed custom post type Local JSON file. |
| acf_list_taxonomiesA | Read ACF-managed custom taxonomy Local JSON files. |
| acf_create_taxonomyC | Create or update an ACF-managed taxonomy Local JSON file. |
| acf_list_options_pagesA | Read ACF Pro options page Local JSON files. Options pages require ACF Pro in WordPress. |
| acf_create_options_pageC | Create or update an ACF Pro options page Local JSON file. Options pages require ACF Pro in WordPress. |
| acf_apply_content_modelA | Apply a declarative content model to Local JSON in dependency-safe order: post types, taxonomies, options pages, field groups. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| acf-content-model-review | Ask an AI client to review a proposed ACF content model before applying it. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| acf-mcp-config | Non-secret server configuration summary. |
TDQS
Scored across 17 tools
Each tool targets a distinct ACF entity (post type, taxonomy, field group, options page) with clear actions, so no ambiguity exists.
All tools follow the verb_noun pattern (e.g., acf_create_field_group, acf_list_post_types) with consistent prefix 'acf_'.
17 tools are well-scoped for managing ACF entities, covering create, read, update, delete, import, export, sync, validation, and health checks.
Covers CRUD for field groups, post types, taxonomies, options pages, plus import/export/sync/validation. Minor gap: no separate tool for managing individual fields within a group, but that is covered via field group updates.