tr Skip to content
New in 6.0 FlowMattic also ships an MCP Server — expose WordPress to AI →

Connect to any MCP server
from your WordPress site

FlowMattic's MCP Client lets your workflows and AI Agents execute tools on any MCP-compatible server — GitHub, Slack, Stripe, or your own — directly, with no custom code required.

MCP servers to connect
0Usage contexts
0Auth methods
0Lines of code needed
How it connects

One client,
any MCP server

Trigger a workflow from your favorite AI-powered editor, then let FlowMattic's MCP Client take it the rest of the way — calling any MCP-compatible service you connect.

Your AI client
Claude Cursor VS Code Windsurf
FlowMattic Workflows & AI Agents — your MCP Client
Any MCP server
GitHub Slack Stripe Your own server

Want it the other way around — AI assistants calling directly into your WordPress data? That's FlowMattic's MCP Server →

Setup

Three steps to your
first tool call

Connect to any MCP server in minutes — no custom code required.

1

Get the endpoint URL

Grab the Streamable HTTP endpoint of any MCP server — GitHub, Slack, another FlowMattic site, or any MCP-compatible service.

2

Add it to your MCP client

Paste the URL into a workflow step or an AI Agent's tool settings. FlowMattic auto-discovers every tool the server exposes — search, filter, and pick which ones to allow.

3

Call it from your workflow

Use the tool as a regular workflow step, or hand it to an AI Agent — it calls the remote server and chains the result into what happens next.

Two ways to use it

One client,
however you build

Use MCP tools as autonomous AI Agent actions or as configurable workflow steps — your choice, on every connection.

AI Agent tool

Add an MCP server as a tool inside an AI Agent, alongside FlowMattic's 783+ native integrations. The AI discovers available tools automatically and calls them based on its own reasoning — chaining calls to complete multi-step tasks.

Explore AI Agents

Workflow step

Use an MCP tool as a regular workflow action. Pick a specific tool, configure parameters with dynamic tags from earlier steps, and chain the response into what happens next.

Flexible authentication

Connect to secured MCP servers with whichever auth method they require.

  • No auth — public servers
  • Bearer token — OAuth2, JWT, API tokens
  • API key — custom header + value
  • Custom headers — multiple key/value pairs

Built for WordPress. Works with the entire MCP ecosystem.

FlowMattic's MCP Client uses the Streamable HTTP transport with automatic session management, schema optimization for AI token efficiency, and full JSON-RPC 2.0 compliance.

Auto tool discovery

Automatically fetches and displays all tools from any MCP server. Search and filter by name or description.

Schema optimization

Automatically strips non-essential metadata from tool schemas to minimize AI token usage without losing functionality.

Session management

Handles Mcp-Session-Id headers automatically for stateful connections, with transparent reconnection on session expiry.

Tool filtering

Choose All Tools, Selected Only, or All Except to control exactly which tools an AI Agent can access.

Dynamic tags

Use data from previous workflow steps as tool parameters. Dynamic tags work in auth fields and tool parameters alike.

Configurable timeout

Set connection timeouts from 5 to 300 seconds. The 60s default works for most servers; increase it for slower endpoints.

Compatible servers

Connect to
any MCP server

The MCP ecosystem is growing fast. FlowMattic connects to any server that implements the protocol — from major platforms to your own custom tools.

GitHubIssues, PRs, repos, code search
SlackMessages, channels, reactions
StripePayments, invoices, subscriptions
CloudflareDNS, Workers, KV store
GoogleDrive, Sheets, Calendar, Maps
AtlassianJira, Confluence, Bitbucket
DockerContainers, images, volumes
FlowMatticSite-to-site automation
SentryError tracking, monitoring
Brave SearchWeb search, local search
FigmaDesign files, components
DatabasesPostgres, Supabase, Neon
Thousands moreAny MCP-compatible server

Don't see your service? If it has an MCP server, FlowMattic can connect to it. Learn how to connect →

FAQ

Questions about
the MCP Client

Everything you need to know before you connect your first server.

It turns your FlowMattic workflows and AI Agents into an MCP client — they can call tools on any external MCP server (GitHub, Slack, Stripe, another FlowMattic site, or your own) directly from an automation, with no custom code required.

The Client calls out — your workflows and AI Agents reach external MCP servers. The Server does the opposite: it exposes your own WordPress workflows, database and PHP functions as tools that AI assistants like Claude, Cursor or VS Code can call. FlowMattic ships both. See the MCP Server →

No. Paste the server's Streamable HTTP endpoint URL, FlowMattic auto-discovers its tools, and you pick which ones to use in a workflow step or hand to an AI Agent.

No Auth, Bearer Token (OAuth2, JWT or API tokens), API Key with a custom header, and Custom Headers for more complex setups — pull credentials from your Connect settings or a dynamic tag from a previous step.

Yes. Add an MCP server as a tool source inside an AI Agent, and it discovers the available tools and calls them autonomously as it reasons through a task, chaining multiple calls together.

It's included with FlowMattic 6.0 at no additional cost. View pricing plans →

Start connecting to
MCP servers today

Turn your WordPress workflows into a universal MCP client — connect to GitHub, Slack, Stripe or any MCP-compatible service, without writing custom code.

Included with FlowMattic 6.0 9,530+ active sites Self-hosted & private