A brief becomes a real page.Connect an entire workspace through the gateway
Connect sites to Cloud and target them through one hosted connection.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- A practice site and permission for the task.
- A Cloud plan that currently includes the gateway.
- Supported EMCP versions on connected sites; a client supporting remote OAuth.
Let’s do this, step by step.
Step 01
Connect each site with gateway access
Enable EMCP Cloud in Modules and save if needed. Open Connection → Cloud, leave Let EMCP Cloud manage this site through the gateway on, and Connect to EMCP Cloud. On an already connected site turn on Gateway access.
Connect each site to the same Cloud workspace and allow gateway access. If the site is already connected, use its Gateway access switch.
Step 02
Add the gateway URL
Add https://gateway.emcptools.com/mcp as a remote MCP server in your AI app and complete EMCP Cloud sign-in.
This time you sign in to Cloud, not separately to every WordPress site. The gateway URL is different from a site's direct endpoint.
Step 03
List and inspect sites
Call emcp_list_sites and describe the intended site before using its tools.
Use the returned site ID or URL. With multiple sites, target each call explicitly; the hosted gateway does not use the local proxy's active-site switch.
Step 04
Run a read-only task
Read pages from one explicit site and inspect the Gateway target line in the result.
That result tells you where the request ran. Tools still depend on the target site's plugins, license, permissions, and switches.
Step 05
Review broadcasts separately
Use site: all only for a deliberately scoped multi-site task. Keep broadcast writes off for the initial walkthrough.
Broadcast writes need both the workspace setting and explicit per-call confirmation. Check each site's result; success on one does not prove success on the others.
Step 06
End or repair gateway access
In Connection → Cloud, turn Gateway access off and confirm, or Sign out EMCP Gateway in the MCP section’s Connected apps. If access should continue but fails after a restore, try Re-issue credential in Cloud.
Turn Gateway access off to revoke it from the site. You can also sign out the gateway under Connected apps. If the connection needs repair after a restore, re-issue its credential and test a read again.
You’re done when…
The gateway targets the intended site explicitly and you know both revocation routes.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.