Fluent WordPress MCP Server & CLI

What is the Fluent WordPress MCP server & CLI?

It is one open source Node package with a local stdio MCP server and a task CLI. An MCP client discovers structured tools; a terminal or agent runs fluent-wp-cli commands. Both invoke the same handlers, schemas, selected site profile and approval guard.

The remote CLI calls your site's allowlisted REST routes over HTTPS. You do not need a local WordPress installation for these remote tasks. Native wp fluent_crm/wp fluentform commands run in a WordPress WP-CLI environment and offer different server-side operations.

What can you ask it?

Try asking
Read one page of contacts from the site profile I selected, keeping only the necessary fields.
Find the actual Community space slug and inspect its current feeds before editing anything.
Read the requested form's entries without changing their read status.
Review these exact CRM and Community changes in order, then apply only the batch I approve.
Save these selected native responses to a new private file, without displaying the records in chat.

Install and connect your client

# Install Fluent WordPress MCP Server & CLI

One package includes both binaries and 54 tools. Node22+ is required for CLI/manual MCP. Discovery works without private authentication; plugin operations need the exact intended HTTPS WordPress site, native capabilities and installed plugins.

Requirements

Install Node from nodejs.org, reopen a terminal and check node --version/npm --version. A GUI or remote runtime needs its own private settings and readable files. Use npm.cmd on Windows if your PowerShell policy blocks npm.ps1. No sudo or main-login-password workaround is required.

CLI

bash npm install -g @thenavidm/fluent-wp-mcp-cli@latest fluent-wp-cli --version fluent-wp-cli tools fluent-wp-cli login 

Node22+ for manual installation. INSTALL.md includes Codex, every declared client/OS and the versioned desktop bundle.

Make the shipped SKILL.md available in your agent's supported private skill location. npm does not register skills automatically. A single-command alternative is npx -y --package @thenavidm/fluent-wp-mcp-cli@latest fluent-wp-cli tools.

Private account setup

Create a dedicated WordPress Application Password

1. Sign into the intended HTTPS WordPress site. Confirm the site and user before connecting any client. Use a dedicated user with the native Fluent permissions needed for your requested work.
2. Open Users > Profile > Application Passwords. Give this connection a descriptive name, create an Application Password and save it privately. This is a separate credential, not your main WordPress login password. If the section is unavailable, check HTTPS, WordPress version, hosting/security policy and the user's capabilities with your site administrator.
3. Configure FLUENT_WP_SITE_URL, FLUENT_WP_USER and either FLUENT_WP_APP_PASSWORD or FLUENT_WP_PASSWORD_FILE. Use the HTTPS site root, optionally its WordPress install subdirectory. Do not append wp-json, put a password in the URL, or include a query/fragment. No redirects or HTTP fallback are followed.
4. Keep secrets in private client settings or a token-only file outside repositories. Password files must be absolute regular non-symlink files, at most 64 KiB. On macOS/Linux, use an owner-private 0600 file and private parent directory. On Windows, restrict the file and parent directory ACLs separately; POSIX modes do not prove Windows privacy.
5. Run fluent-wp-cli doctor for local configuration, then deliberately run doctor --network for one GET /wp/v2/users/me with context=view. Its output reports a positive user ID only. This verifies one authenticated WordPress read, not site ownership, all plugin permissions, Pro eligibility or a successful mutation.

WordPress Application Password authentication uses HTTP Basic with username:applicationPassword over HTTPS. The client constructs the header; do not supply a Bearer token or import browser cookies. The package does not log into WordPress, load .env files, create an Application Password, or enable plugins for you.

Plugins, permissions and costs

Install and activate the specific FluentCRM, FluentCommunity and Fluent Forms plugins you intend to use. A site's installed plugin versions and native user capabilities determine its routes and output. Discovery exposes the packaged catalogue before authentication; it does not prove every plugin is present. The package is free under AGPL-3.0. Hosting, paid Pro features, plugin licenses and email delivery services remain separate.

CRM contact/tag/list changes and double opt-in may trigger actual emails or automations. Community announcements, comments and reactions can notify real members. Native Forms reports can update stored metadata. Do not create a contact, publish a feed, or run a stateful report merely to test setup.

The source review covers CRM v2, Community v2 and Forms v1, with Forms plugin source 6.2.14 pinned in provenance. This is a reviewed subset of 47 routes, not every Fluent API. Community analytics/admin course routes require their native permissions and may require Pro. Read native permission notes and inspect your installed versions before account work.

Several isolated sites

FLUENT_WP_ACCOUNTS is a private JSON array of unique {name,site_url,username,app_password,password_file} entries. Choose one password method per profile. Each site requires its own URL, user and credential; a selected profile never falls back to global settings or another site after a missing password or 401/403. FLUENT_WP_DEFAULT_ACCOUNT and --account select an exact label.

list_accounts returns labels, the default and credential source only. It does not reveal site URLs, usernames, password paths or credentials, make requests, or prove provider ownership. Password files are cached until restart. Review hashes bind the selected label, normalized site URL, username, ordered inputs/requests and packaged schema; they do not bind a password fingerprint or validate server state.

Native and local limits

There is no universal vendor quota advertised here. The process spaces requests by 250 ms by default, with a 30-second timeout; hosting, security plugins and other clients can impose different limits. Local pacing is not shared quota enforcement. Requests cap JSON bodies at 1 MiB and responses at 5 MiB. No automatic retries, redirect following, polling or page walking occurs.

Native paginated operations accept only their actual arguments. Where page/per_page are exposed, this wrapper bounds them to 10000/100 locally; this is not a universal provider maximum. Course students and space members do not acquire invented pagination flags. Forms single-entry reads that mark entries as read are intentionally outside this subset.

Revoke and remove

Revoke the dedicated Application Password through the intended WordPress user's Profile. Replace or remove private client/file settings, then restart all server processes. Official plugin MCP credentials and WP-CLI access are separate connections. Uninstalling this package does not undo contact edits, messages, announcements, report migrations or saved private snapshots.

Codex

Codex is the current validation priority. Private password paths must exist in the process or remote environment where the server runs.

bash codex mcp add fluent-wp -- npx -y @thenavidm/fluent-wp-mcp-cli@latest codex mcp list 

Account credentials must reach the server through private environment settings. codex mcp add --env NAME=value stores values in your local config, so never commit that config or put secrets in a shared command. In TOML, the equivalent server is:

toml [mcp_servers.fluent-wp] command = "npx" args = ["-y", "@thenavidm/fluent-wp-mcp-cli@latest"] env_vars = ["FLUENT_WP_SITE_URL", "FLUENT_WP_USER", "FLUENT_WP_APP_PASSWORD", "FLUENT_WP_PASSWORD_FILE", "FLUENT_WP_ACCOUNTS", "FLUENT_WP_DEFAULT_ACCOUNT", "FLUENT_WP_READ_ONLY", "FLUENT_WP_ALLOW_DESTRUCTIVE"]

env_vars forwards those names from the environment available to Codex. If that environment does not contain them, configure private env settings locally. Codex can also call the CLI directly with SKILL.md and --agent output.

Claude Code

For a user-scoped connection, after privately configuring credentials:

bash claude mcp add --scope user fluent-wp -- npx -y @thenavidm/fluent-wp-mcp-cli@latest claude mcp list 

Use the client's private local environment settings for the account variable if they are not inherited. Claude's -e NAME=value registration option writes values into its config; only use it locally through your secret manager, with no shared command transcript. Never place credentials in a project .mcp.json. Reconnect and ask Claude to verify credentials.

Alternatively install the CLI, make SKILL.md available to Claude, and use shell commands. Registering both surfaces is optional.

Claude Desktop

Install the .mcpb extension

1. Download fluent-wp-2.0.0.mcpb from GitHub Releases.
2. In a supported Claude Desktop build, open Settings > Extensions > Advanced settings > Install Extension… and select it.
3. Enter the intended HTTPS site root and WordPress username. Enter a dedicated Application Password in the sensitive setting, or an absolute private password-file path, never both. Native requests use HTTP Basic username:applicationPassword. Named site profiles require private manual runtime settings.
4. Enable read-only if you want only the 41 read operations. Reconnect, discover tools, then deliberately verify one current-user read.

The bundle includes production dependencies and no credentials. Use a regular private application-password-only file if you prefer file-based credentials. The manifest requires Node 22 or newer from a compatible host. Organization policy may restrict custom extensions. Manual bundle updates require installing the new version; no automatic directory updates are promised. GUI installation remains unverified separately from archive/protocol checks.

Manual config

Open Settings > Developer > Edit Config, or use your platform's config file:

json { "mcpServers": { "fluent-wp": { "command": "npx", "args": [ "-y", "@thenavidm/fluent-wp-mcp-cli@latest" ], "env": { "FLUENT_WP_APP_PASSWORD": "YOUR_PRIVATE_APP_PASSWORD", "FLUENT_WP_PASSWORD_FILE": "", "FLUENT_WP_SITE_URL": "https://YOUR-PRIVATE-SITE.example", "FLUENT_WP_USER": "YOUR_PRIVATE_WORDPRESS_USERNAME" } } } } 

Replace the placeholders only in your private file. Merge the server entry into an existing mcpServers object instead of replacing other integrations. Fully quit and reopen Claude Desktop. Do not enable an extension and a manual entry with the same name; choose one route.

If a Windows launcher cannot execute npx directly, use "command": "cmd" with "args": ["/c", "npx", "-y", "@thenavidm/fluent-wp-mcp-cli@latest"]. An absolute node executable and installed dist/index.js path also avoids launcher/PATH problems.

Cursor

Use private user settings at ~/.cursor/mcp.json, or Settings > Tools & MCP. Cursor documents environment interpolation and envFile support.

json { "mcpServers": { "fluent-wp": { "type": "stdio", "command": "npx", "args": [ "-y", "@thenavidm/fluent-wp-mcp-cli@latest" ], "env": { "FLUENT_WP_APP_PASSWORD": "${env:FLUENT_WP_APP_PASSWORD}", "FLUENT_WP_PASSWORD_FILE": "${env:FLUENT_WP_PASSWORD_FILE}", "FLUENT_WP_SITE_URL": "${env:FLUENT_WP_SITE_URL}", "FLUENT_WP_USER": "${env:FLUENT_WP_USER}" } } } } 

The environment values must exist for the Cursor process. If you use envFile, keep that file private and outside version control. A project's .cursor/mcp.json must not contain actual credentials. Reconnect the server after saving.

VS Code and Copilot

Use MCP: Open User Configuration. VS Code uses servers and secure inputs, rather than a mcpServers root:

json { "inputs": [ { "type": "promptString", "id": "fluent-wp-app-password", "description": "Dedicated WordPress Application Password (leave empty for a private password file)", "password": true }, { "type": "promptString", "id": "fluent-wp-password-file", "description": "Optional private password-file path (leave empty for Application Password)" }, { "type": "promptString", "id": "fluent-wp-site-url", "description": "Trusted HTTPS WordPress site root" }, { "type": "promptString", "id": "fluent-wp-user", "description": "Intended WordPress username" } ], "servers": { "fluent-wp": { "type": "stdio", "command": "npx", "args": [ "-y", "@thenavidm/fluent-wp-mcp-cli@latest" ], "env": { "FLUENT_WP_APP_PASSWORD": "${input:fluent-wp-app-password}", "FLUENT_WP_PASSWORD_FILE": "${input:fluent-wp-password-file}", "FLUENT_WP_SITE_URL": "${input:fluent-wp-site-url}", "FLUENT_WP_USER": "${input:fluent-wp-user}" } } } } 

Start Fluent WordPress through the MCP controls, approve trust if prompted, and enter credentials in the private input prompts. Workspace .vscode/mcp.json may contain this placeholder-only structure, but never resolved secret values. Remote development runs the server in the selected remote environment, so local file paths refer to that environment.

Windsurf

Open Cascade's MCP settings or edit the private user file ~/.codeium/windsurf/mcp_config.json. Use the Claude Desktop manual mcpServers block above with your locally configured env values. See Windsurf's current MCP documentation. Restart or reconnect Fluent WordPress in Cascade; project files must not contain secrets.

Zed

Open Settings > AI > MCP Servers > Add Server > Add Local Server, or your user settings file. Zed uses context_servers:

json { "context_servers": { "fluent-wp": { "command": "npx", "args": [ "-y", "@thenavidm/fluent-wp-mcp-cli@latest" ], "env": { "FLUENT_WP_APP_PASSWORD": "YOUR_PRIVATE_APP_PASSWORD", "FLUENT_WP_PASSWORD_FILE": "", "FLUENT_WP_SITE_URL": "https://YOUR-PRIVATE-SITE.example", "FLUENT_WP_USER": "YOUR_PRIVATE_WORDPRESS_USERNAME" } } } } 

Enter actual values only in private user settings. Check the active-server indicator before prompting. Do not wrap command and args inside a nested command object from older Zed examples.

Gemini CLI

Merge the Claude Desktop manual mcpServers block into your private ~/.gemini/settings.json. Configure the private site/user/password values locally, then restart Gemini CLI and inspect /mcp. See Gemini CLI's MCP configuration. Its project settings must not contain real credentials. You can instead use the CLI from an agent shell.

Other local stdio clients use the same command and arguments, adapted to their config format. A client that only accepts a remote MCP URL cannot connect directly: this package does not ship a public HTTP listener. ChatGPT's remote connector setup is not a substitute for local stdio installation.

Docker

Build locally from the reviewed source; no prebuilt registry image is claimed:

bash git clone https://github.com/thenavidm/fluent-wp-mcp-cli.git cd fluent-wp-mcp-cli docker build -t fluent-wp-mcp-cli . docker run --rm -i -e FLUENT_WP_SITE_URL -e FLUENT_WP_USER -e FLUENT_WP_APP_PASSWORD fluent-wp-mcp-cli 

Cline and other local MCP clients

Use the client's Add MCP server flow with command npx, arguments -y and @thenavidm/fluent-wp-mcp-cli@latest, stdio transport, and private local FLUENT_WP_SITE_URL/FLUENT_WP_USER and FLUENT_WP_APP_PASSWORD or FLUENT_WP_PASSWORD_FILE settings. UI names depend on the installed client. Reconnect and discover tools before an account call. Browser-only clients need a remote HTTPS connector; use Fluent WordPress's official server rather than this local stdio command.

Verify

bash fluent-wp-cli --version fluent-wp-cli tools fluent-wp-cli list-accounts --agent fluent-wp-cli doctor fluent-wp-cli doctor --network fluent-wp-cli fcrm-list-contacts --per-page 1 --agent --select data.id 

Credential-free discovery, native request fixtures and direct full/read-only guard checks are separate from actual provider validation. A positive current-user read establishes neither ownership nor every Fluent permission. Authenticated plugin outcomes, desktop GUI installation and matched successful Codex task/token results remain unverified until independently exercised.

Multiple accounts

FLUENT_WP_ACCOUNTS is a private JSON array of unique {name,site_url,username,app_password,password_file} entries. Choose one password method per profile. Each site requires its own URL, user and credential; a selected profile never falls back to global settings or another site after a missing password or 401/403. FLUENT_WP_DEFAULT_ACCOUNT and --account select an exact label.

list_accounts returns labels, the default and credential source only. It does not reveal site URLs, usernames, password paths or credentials, make requests, or prove provider ownership. Password files are cached until restart. Review hashes bind the selected label, normalized site URL, username, ordered inputs/requests and packaged schema; they do not bind a password fingerprint or validate server state.

bash fluent-wp-cli list-accounts --agent fluent-wp-cli fcrm-list-contacts --account work --per-page 1 --agent 

Updates and removal

Use npx -y @thenavidm/fluent-wp-mcp-cli@latest for fresh client launches, then reconnect/restart. Global installs require npm update -g @thenavidm/fluent-wp-mcp-cli. Desktop extensions require installing the newly versioned archive. Read the major migration table before replacing old script arguments. Remove only the requested registration, skill, package or extension. Revoke Application Passwords separately; private snapshots and provider changes remain.

bash npm update -g @thenavidm/fluent-wp-mcp-cli fluent-wp-cli --version # Removal only when requested codex mcp remove fluent-wp npm uninstall -g @thenavidm/fluent-wp-mcp-cli

Troubleshooting

Development

bash git clone https://github.com/thenavidm/fluent-wp-mcp-cli.git cd fluent-wp-mcp-cli npm ci npm run typecheck npm run build npm test npm run check:counts npm run check:discovery npm run sync:api -- --check npm run build:mcpb 

Source mode registers node /absolute/path/fluent-wp-mcp-cli/dist/index.js after a build. Credentials remain outside the checkout and archive. CONTRIBUTING.md, SECURITY.md and THIRD_PARTY_NOTICES.md cover reports, development and licensing.

CLI output and scripting

Native JSON is preserved after recognized credential redaction; ordinary records remain private. --select keeps only requested output fields. Repeated primitive array flags serialize to native PHP [] query fields. Nested subscriber/note objects use JSON values, and --payload or a private absolute --payload-file provides a complete native body. Do not mix body flags with payload/payload_file. A 202 means acceptance, not completed downstream work. HTTP200 JSON success:false/status:false/native error objects refuse.

MCP or CLI and measured token cost

Both surfaces call the same MCP handlers and guard. MCP clients choose their own tool discovery/loading strategy. The CLI supports selected command help/schema and compact results; it also consumes command/help/output/reasoning tokens. Fresh matched successful Codex task/token measurements remain pending. No percentage, character estimate, other-client figure or fixture is represented as a measured Codex saving. Record actual API usage, client/model/version/date, discovery settings, caching, latency, provider calls and equivalent successful outputs before publishing a comparison.

CRM, Community and Forms workflows

Read CRM before an approved change

Discover real contacts, tags and lists first. An approved status/list/tag update can trigger automations; read the current profile and choose only the requested fields. A successful native receipt does not prove all downstream emails or hooks completed.

bash fluent-wp-cli fcrm-list-contacts --per-page 5 --agent fluent-wp-cli fcrm-list-tags --per-page 5 --agent fluent-wp-cli schema fcrm-update-contact fluent-wp-cli fcrm-update-contact --help 

Read Community and edit the intended content

Get a real space slug and feed ID. Feeds use native space/content_type/message, comments use comment, and content edits use POST. Announcement email is a separate effect: approve it explicitly if requested. Scheduled-post discovery is not a scheduling action.

bash fluent-wp-cli fc-list-spaces --agent fluent-wp-cli fc-list-feeds --per-page 5 --agent fluent-wp-cli schema fc-create-feed fluent-wp-cli schema fc-update-comment 

Read Forms submissions without marking an entry

Discover form IDs and request a selected submissions page. entry_type controls native status/favourites filters, sort_by is a direction, and date_range is a two-element array. The package does not silently call a single-entry endpoint that marks entries read. ff_form_report is a confirmed stateful report, separate from ordinary entry/stat reads.

bash fluent-wp-cli ff-list-forms --per-page 5 --agent fluent-wp-cli ff-list-submissions --form-id 123 --per-page 5 --agent fluent-wp-cli schema ff-form-stats fluent-wp-cli ff-form-report --help 

123 is an example ID; replace it with a real ID read from the intended site before making that request.

Reviewed batches and private snapshots

Preview one to twenty exact ordered CRM/Community writes. Every native schema/body is validated before the first request. Preview is local and does not read a password, query provider state, lock a cohort or issue a native official confirmation token. Select the same exact site and unchanged task order when submitting.

bash fluent-wp-cli preview-site-batch --help fluent-wp-cli schema submit-site-batch fluent-wp-cli read-site-snapshot --help fluent-wp-cli schema save-site-snapshot 

Each --tasks flag is one JSON object with tool and arguments. Task arguments cannot override account/confirm or refer to payload_file/output_file. Use a complete immutable payload value when needed. submit-site-batch requires --confirm and the exact --review-sha256 hash; --agent and --yes never supply approval. Execution stops on the first failure and returns knownResults, failedIndex and unattemptedIndices. No retry, rollback or automatic continuation occurs. A failed request can have an unknown result, and a receipt can precede hook/announcement completion.

read_site_snapshot prevalidates one to twenty selected native reads for one site and returns at most 5 MiB combined native responses. Each list is one requested page, not an all-pages backup or atomic provider snapshot. save_site_snapshot requires confirmation and an absolute new file in an existing private directory. It reserves the file exclusively with mode0600, never overwrites, and returns only path/bytes/SHA-256 metadata. Failure removes only its newly created file and reports indices without native records. Keep Windows ACLs and parent-directory privacy separately restricted. Stateful Forms reports are excluded from these read helpers.

Every shared tool and argument

fcrm_dashboard_stats

Retrieve overall dashboard statistics including active contacts count, campaigns count, emails sent, active automations, onboarding progress, quick links, recent contacts, recent campaigns, active automations list, and system recommendations.

Required capability: fcrm_view_dashboard

Enforced by `ReportPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-dashboard-stats --help fluent-wp-cli schema fcrm-dashboard-stats 

fcrm_list_contacts

Retrieve a paginated list of contacts. Supports both simple filtering (by tags, lists, statuses) and advanced filtering with complex filter groups. Optionally includes custom field values.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-list-contacts --help fluent-wp-cli schema fcrm-list-contacts 

fcrm_get_contact

Retrieve a single contact by ID or email. Supports eager-loading related data like stats, custom values, custom field definitions, and commerce stats via the with[] parameter.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-get-contact --help fluent-wp-cli schema fcrm-get-contact 

fcrm_search_contacts

Search contacts by name or email. Returns a lightweight object of contacts keyed by ID, suitable for dropdowns and autocomplete widgets. Optionally loads default contacts when no search term is provided.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-search-contacts --help fluent-wp-cli schema fcrm-search-contacts 

fcrm_create_contact

Create a new contact. If __force_update is set to yes, it will update an existing contact with the same email instead of returning an error. Optionally sends a double opt-in email.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group. Explicit local confirmation is required; hooks, announcements and automations may affect other people. No retries.

Kind: Confirmed operation. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-create-contact --help fluent-wp-cli schema fcrm-create-contact 

fcrm_update_contact

Update an existing contact's fields, custom values, tags, and lists. Supports attaching and detaching tags/lists in a single request. The subscriber object or individual fields can be passed in the request body.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group. Explicit local confirmation is required; hooks, announcements and automations may affect other people. No retries.

Kind: Confirmed operation. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-update-contact --help fluent-wp-cli schema fcrm-update-contact 

fcrm_contact_notes

Retrieve a paginated list of notes for a contact. Supports searching notes by title. Each note includes the user who created it.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-contact-notes --help fluent-wp-cli schema fcrm-contact-notes 

fcrm_add_contact_note

Add a new note to a contact. The note description supports SmartCode/merge tags which are parsed before saving. If created_at is not provided, it defaults to the current WordPress time.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group. Explicit local confirmation is required; hooks, announcements and automations may affect other people. No retries.

Kind: Confirmed operation. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-add-contact-note --help fluent-wp-cli schema fcrm-add-contact-note 

fcrm_list_tags

Retrieve a paginated list of tags. Optionally includes subscriber counts and a separate array of all tags for dropdown/select usage.

Required capability: fcrm_manage_contact_cats

Enforced by `TagPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-list-tags --help fluent-wp-cli schema fcrm-list-tags 

fcrm_list_lists

Retrieve a paginated list of contact lists. Optionally includes subscriber counts and a separate array of all lists for dropdown/select usage.

Required capability: fcrm_manage_contact_cats

Enforced by `ListPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-list-lists --help fluent-wp-cli schema fcrm-list-lists 

fcrm_list_campaigns

Retrieve a paginated list of email campaigns. Supports filtering by status, search term, labels, and sorting. Optionally includes campaign statistics.

Required capability: fcrm_read_emails or fcrm_manage_emails : which one applies depends on the action being performed.

Enforced by `CampaignPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-list-campaigns --help fluent-wp-cli schema fcrm-list-campaigns 

fcrm_get_campaign

Retrieve a single campaign by ID. Optionally include related data (template, subjects) via the with parameter. When viewCampaign is set, returns the campaign with its paginated emails. Also returns available email templates and the server's current time.

Required capability: fcrm_read_emails or fcrm_manage_emails : which one applies depends on the action being performed.

Enforced by `CampaignPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-get-campaign --help fluent-wp-cli schema fcrm-get-campaign 

fcrm_campaign_stats

Get overview statistics for a campaign including sent count, email status breakdown, and open/click analytics. This is a lighter-weight alternative to the full campaign status endpoint, suitable for dashboard widgets or summary views.

Required capability: fcrm_read_emails or fcrm_manage_emails : which one applies depends on the action being performed.

Enforced by `CampaignPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-campaign-stats --help fluent-wp-cli schema fcrm-campaign-stats 

fcrm_list_sequences

Retrieve a paginated list of email sequences. Optionally include statistics (email count, subscriber count, revenue) for each sequence. Requires FluentCampaign Pro.

Required capability: fcrm_read_emails or fcrm_manage_emails : which one applies depends on the action being performed.

Enforced by `SequencePolicy::verifyRequest()`, the policy default for this route group.

Requires: FluentCampaign Pro. Without it the route does not exist.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-list-sequences --help fluent-wp-cli schema fcrm-list-sequences 

fcrm_list_automations

Retrieve a paginated list of automation funnels. Supports sorting, searching by title, and filtering by label IDs. Optionally includes trigger definitions.

Required capability: fcrm_read_funnels or fcrm_write_funnels : which one applies depends on the action being performed.

Enforced by `FunnelPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-list-automations --help fluent-wp-cli schema fcrm-list-automations 

fcrm_automation_report

Retrieve statistical reporting data for a specific automation funnel. Returns aggregated stats generated by the Reporting service.

Required capability: fcrm_read_funnels or fcrm_write_funnels : which one applies depends on the action being performed.

Enforced by `FunnelPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-automation-report --help fluent-wp-cli schema fcrm-automation-report 

fcrm_contact_emails

Retrieve a paginated list of emails sent to a contact. Supports filtering by open/click status. Can also show FluentSMTP logs when the tab parameter is set to fluentsmtp.

Required capability: fcrm_read_contacts or fcrm_manage_contacts : which one applies depends on the action being performed.

Enforced by `SubscriberPolicy::verifyRequest()`, the policy default for this route group.

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fcrm-contact-emails --help fluent-wp-cli schema fcrm-contact-emails 

fc_list_spaces

Returns the paginated list of spaces with each one formatted for display, including the current user permissions and membership within it.

Controller: SpaceController@getAllSpaces Route source: fluent-community/app/Http/Routes/api.php:34

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fc-list-spaces --help fluent-wp-cli schema fc-list-spaces 

fc_get_space

Returns one space with its settings, topics, the current user membership and the permissions they hold inside it.

Controller: SpaceController@getBySlug Route source: fluent-community/app/Http/Routes/api.php:10

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fc-get-space --help fluent-wp-cli schema fc-get-space 

fc_list_feeds

Returns a page of posts the current user is allowed to read, transformed for display, with the pinned post of a space returned separately on the first page.

Controller: FeedsController@get Route source: fluent-community/app/Http/Routes/api.php:45

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fc-list-feeds --help fluent-wp-cli schema fc-list-feeds 

fc_get_feed

Returns a single post by numeric id; the id is resolved to a slug and then handled exactly as the by-slug endpoint.

Controller: FeedsController@getFeedById Route source: fluent-community/app/Http/Routes/api.php:53

Kind: Read. Native plugin/user permissions apply.

bash fluent-wp-cli fc-get-feed --help fluent-wp-cli schema fc-get-feed 

fc_create_feed

Creates a post, renders its Markdown, attaches media and topics, and returns the transformed post ready to prepend to the feed.

Controller: FeedsController@store Route source: fluent-community/app/Http/Routes/api.php:46 Explicit local confirmation is required; hooks, announcements and automations may affect other people. No retries.

Kind: Confirmed operation. Native plugin/user permissions apply.