Agent Abilities
GitHubGet it free
Product
FeaturesSecurityAll abilitiesIntegrationsBridge overviewBridge plugin directory196

Guides

WordPress MCP serverAbilities API guideElementor MCP

WordPress core abilities

Browse all abilitiesContentTaxonomies & TermsCommentsUsersMediaSite settingsPluginsThemes & stylesBlocksMenusSearch

Integrations

All integrationsWooCommerce52Advanced Custom Fields7Rank Math SEO5Yoast SEO3All in One SEO3Slim SEO2The Events Calendar13Event Tickets3Avada2GeoDirectory4

Bridge, most installed

Elementor Website BuilderYoast SEOWooCommerceAkismet Anti-spamWPFormsRank Math SEOWP Mail SMTPWPCode
Connect
All clientsChatGPTClaude.aiClaude DesktopManusClaude CodeCursorVS CodeWindsurfGemini CLIGetting startedHow connecting works
Resources
Prompt LibraryPlaybooksBlogComparisonsChangelogSupport
DocsGitHubGet it free

Test that pausing a connection works before you need it

MaintenanceBeginner~3 min
AbilitiesGet site info

Before you start

Plugin version 1.10.1 or newer, which returns a clear paused message on each tool call (per-connection pause arrived in 1.10.0). An OAuth connection you can pause and resume from the Connection tab, and the Get site info tool switched on. Run the prompt from the connection you are going to pause.

If an agent ever does something you did not expect, you will want it stopped in seconds, and you will not want to be learning the pause screen at that moment. A few minutes now shows you what pausing looks like from the agent’s side.

Treat it as a fire drill: one harmless read, three times, before, during and after the pause.

The prompt
I want to test pausing this connection. Use only the site info read, and
make each call once.


1. Read the site info now and tell me the site name.
2. Then stop and say "Ready for pause". I will pause this connection in
   WordPress and reply "paused".
3. When I reply, read the site info again. Quote the exact error you get,
   word for word. Do not retry, and do not try any other tool.
4. Then stop and say "Ready for resume". I will resume it and reply
   "resumed".
5. Read the site info one last time.


Finish with a three-row table: before, paused, resumed, with what happened
each time.

Why this is safe to run

Get site info returns the site name, tagline, URL and language and changes nothing. The prompt makes one call at each stage and tells the agent not to retry or switch tools while paused, so the drill cannot turn into a burst of calls.

What you learn is what your own client shows when a connection is paused, in its exact words. If the paused call still worked, check that you paused the connection the agent is actually using: the Connection tab lists each one with when and from which address it was last used, and a paused connection’s last-used time does not move while it is paused.

Already connected? Ask your agent to run the pause drill with you, and keep the Connection tab open in another window.

How it works

  1. Try one read while the connection is active and report the result.
  2. Wait while you pause the connection on the Connection tab.
  3. Try the same read again and quote the exact error.
  4. Wait while you resume it, then try once more.
  5. Report the three results side by side.

Questions

What does the agent see while paused?
Since 1.10.1 a paused connection still signs in and lists its tools, and each tool call returns a tool error saying the connection is paused. Before that, Claude used to show a firewall or sign-in error instead.
Does pausing log the agent out?
No. Pause and resume work without signing in again, so you can stop one connection for a while and bring it back as it was. Other connections keep working.
How is this different from Pause all access?
Pause all access on the Connection tab stops every MCP request through the site, on this plugin's endpoint and the MCP Adapter's default server. A connection's own pause stops only that connection.

Related recipes