Skip to content
View as Markdown

GET MCP Status

GET
/mcp/status

Report everything the Settings → MCP screen needs to decide what to render: whether an adapter is installed and active, which one is providing it, how many abilities are registered, and whether the kill-switch is on.

An adapter can come from two places — the standalone adapter plugin or a bundled adapter inside FluentHub — and adapter_provider tells you which one won (plugin, toolkit, or an empty string when neither is active).

tools_count is 0 whenever the WordPress Abilities API is missing, since there is nowhere to register abilities.

Required capability: fcrm_manage_settings

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

Authorizations

ApplicationPasswords

WordPress Application Passwords — use Basic auth with your WordPress username and an application password in the format: username:application_password

Type
API Key (header: Authorization)

Responses

Current MCP integration status.

application/json
JSON
{
"adapter_installed": true,
"adapter_active": true,
"adapter_provider": "string",
"standalone_adapter_installed": true,
"toolkit_installed": true,
"toolkit_active": true,
"toolkit_adapter_available": true,
"adapter_runtime_available": true,
"adapter_version": "string",
"toolkit_version": "string",
"abilities_api_loaded": true,
"endpoint_url": "string",
"tools_count": 0,
"mcp_enabled": true,
"pro_active": true,
"app_passwords_url": "string",
"plugins_url": "string",
"can_auto_install_adapter": true,
"toolkit_download_url": "string",
"current_user_login": "string",
"is_local_dev": true
}

Playground

Authorization

Samples

Powered by VitePress OpenAPI