Tool cap exceeded
If your client connects fine but reports zero tools, or stops loading the EMCP Tools server entirely, you’ve likely hit a tool-count cap.
Which clients have caps
Section titled “Which clients have caps”| Client | Cap | Behavior when exceeded |
|---|---|---|
| Antigravity | 100 tools | Silently drops the server. No error in UI. |
| Gemini API | varies | Depends on model; usually rejects function set. |
| Claude Code | no hard cap | Works fine; just costs more context tokens. |
| Claude Desktop | no hard cap | Same. |
| Cursor | no hard cap | Same. |
| VS Code MCP ext | no hard cap | Same. |
EMCP Tools registers up to 207 tools depending on environment (Elementor Pro adds ~10 tools including add-pro-widget, Elementor 4.0 adds 14; WooCommerce adds none). On a full Pro + E4.0 install, you’re at 130, over the Antigravity cap.
The fix: Compact tool mode
Section titled “The fix: Compact tool mode”- WordPress admin → EMCP Tools → Tools
- Toggle on Compact tool mode
- Click Save Changes
- Reconnect your MCP client.
This collapses the whole surface to just 3 dispatcher meta-tools (list-tools, get-tool-schema, call-tool), well under any client cap. The agent discovers a tool with list-tools, fetches its inputs with get-tool-schema, and runs it with call-tool. Re-test your client. The server should now appear with three tools.
Full details in the Compact tool mode docs.
Your per-tool toggles still apply
Section titled “Your per-tool toggles still apply”Compact tool mode doesn’t bypass your settings: call-tool refuses any tool you’ve disabled on the Tools tab (and any tool your account lacks the capability for). So you can still curate exactly which tools the agent is allowed to run through the dispatcher.
How to know if it’s a cap issue vs. something else
Section titled “How to know if it’s a cap issue vs. something else”If curl (see No tools appearing) returns a non-empty tools array but your specific client shows zero, that’s a cap issue or a client-side bug. Cap issues are silent in Antigravity; the client just acts like the server doesn’t exist.
If the same client works with Compact tool mode on, you’ve confirmed the cap was the cause.
Why the default-disabled Pro widgets
Section titled “Why the default-disabled Pro widgets”On fresh installs, the opt-in tool groups (anything that writes, deletes, or renders site-wide: SEO & Accessibility, Widget Builder, PHP Snippets, WP-CLI, the Plugins & Themes and Users write tools, delete-media, the Filesystem and Database write tools, and the write dispatcher of every plugin integration, 98 in all) are disabled by default. This keeps the active surface smaller out of the box; enable any of them from the Tools screen when you need them.