TroubleshootingLesson 1 of 7 · 6 steps

Connected, but no tools appear

Find whether the problem is connection, discovery, or one unavailable integration.

Video coming soon

Your next step is ready.

Follow the complete written guide below.
The video will join it here when it’s ready.

Start the written lesson

Before you start

  • Access to the affected site and AI connection.
  • A redacted copy of the exact error.

Let’s do this, step by step.

Step 01

Name the symptom

Record whether the server is unreachable, authentication fails, zero tools appear, three tools appear, or one action fails.

These are different problems. Three dispatcher tools may be normal Compact mode; zero tools alone does not prove a tool limit.

Step 02

Check the exact site and server

Open Connection → MCP. Under Advanced settings check Abilities API, then Save. Copy the endpoint from Server status and inspect its adapter state.

Check the address your app uses. Turn on Abilities API if needed and save. Server status also tells you whether the bundled adapter is available.

Step 03

Inspect dependencies and switches

Check installed versions, selected builder, module state, license, and the required tool's dependency badge. Save only intended switches.

Do not enable everything as a test. A missing integration may simply need its plugin active or its supported version installed.

Step 04

Reconnect and compare logs

Reconnect the app, reproduce once, and compare the timestamp with EMCP Tools → MCP Log.

If the request does not appear, check whether it reached WordPress. Absence from this log does not tell you exactly where the request stopped.

Step 05

Test discovery independently

If needed, use local MCP Inspector with the same endpoint and identity to list tools without writing.

A separate successful test helps narrow the problem, but a different account or connection route is not an identical comparison.

Step 06

Verify the first read

Ask the app for real page titles, IDs, and statuses. If still blocked, prepare the support details from the lesson below.

A tool list proves discovery; a real read tests execution. Keep those two checks separate.

You’re done when…

You have isolated the failing stage or captured enough evidence for a focused support report.

Keep the reference handy.

The docs cover tool details and requirements for this lesson.