Do You Need the MCP Adapter Plugin?
No. Saddle speaks MCP on its own, with nothing else to install. If you happen to have the separate MCP Adapter plugin active, Saddle uses it — and nothing you can see changes either way.
Short answer: no. Saddle speaks MCP itself. There is nothing else to install, and installing something else will not give your AI app more to work with.
Why the question comes up
MCP is the shared language AI apps use to talk to tools. There is a separate WordPress plugin called MCP Adapter that does a similar translation job, and you may see it mentioned in developer documentation or find it while searching the plugin directory.
It is not a dependency. Saddle does not require it, does not bundle it, and does not prompt you to install it.
What happens if you have it anyway
If the MCP Adapter plugin is active on your site, Saddle notices and uses it instead of its own transport. That is the only difference, and it is deliberately invisible:
- Same address. Your MCP URL does not change.
- Same tools. Every tool your AI can call is the same, under the same names.
- Same access levels. Your chosen level, your per-tool switches and the pause switch all apply exactly as before.
- Same approvals. Destructive actions still stop and ask.
You do not need to reconnect your apps if you install or remove it. To see which one is in play, open Saddle → Connections → Connection details & health and look at the Transport line.
Which should I use?
Whichever you already have. If you have no opinion, do nothing — Saddle on its own is the normal setup and the one most sites run.
There is one reason to prefer having only one: two plugins doing the same translation cannot both load, so if you install the adapter, Saddle steps aside for it. That is handled automatically, but it does mean a problem in one can look like a problem in the other. If you are troubleshooting a connection, knowing which line the Transport row shows is a useful first fact.