An agent can list and audit the site's custom code snippets, detect snippet errors, read WPCode's error log, and search its snippet library, all without the raw snippet code ever being exposed.
REST API Route Tester abilities, governed through the Bridge
An agent can list every registered WordPress REST route with its supported HTTP methods, and dispatch a test request against a chosen route (with an optional execution trace of hooks, SQL and HTTP calls) to see what it returns.
- Abilities
- 21 read1 write
- Active installs
- 40+
- Rating
- 0% (0 ratings)
- Version
- 1.6.0
- Requires
- WP 5.0+, PHP 8.0+
- Last updated
- 2026-09-20 7:35am GMT
View REST API Route Tester on WordPress.org
What has to be true first
Needs WordPress 6.9 or later for the Abilities API to exist (the plugin itself supports WordPress 5.0+) and the plugin active. Both abilities require manage_options, so only an administrator-level connected user can list or test a REST route.
The 2 REST API Route Tester abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 1
- Read
List REST API routes
Returns registered WordPress REST routes with their supported HTTP methods.
Write 1
- Write
Test a REST API route
Dispatches a REST request against a chosen route in the admin context and returns the status, headers and data.
How to switch these on
Four steps from two active plugins to a governed connection.
Install REST API Route Tester and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. REST API Route Tester registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from REST API Route Tester starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does REST API Route Tester work with the Bridge?
Yes. It registers two abilities directly in the core Abilities API with no MCP server of its own, so the Bridge is the only way an agent reaches them.
Do REST API Route Tester's abilities register automatically?
Yes, unconditionally, once REST API Route Tester is active. Nothing else has to be configured for the Bridge to discover them.
Does REST API Route Tester need anything special to work with the Bridge?
Needs WordPress 6.9 or later for the Abilities API to exist (the plugin itself supports WordPress 5.0+) and the plugin active. Both abilities require manage_options, so only an administrator-level connected user can list or test a REST route.
More Developer plugins
An agent can look up the expected value format for a field type, then read, write, or delete a specific custom field's value on a post, term, user, comment, or settings page.
An agent can list, read, create, update, duplicate, export, import, trash, and restore SCF field groups, individual fields, custom post types, taxonomies, and options pages, and, once the site turns on AI Access, list and register field groups, post types, and taxonomies under a second acf/* ability set plus create, read, update, and delete records of any post type or taxonomy the site opts in.
Verified from REST API Route Tester's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Nowshad Jawad or REST API Route Tester. Back to the full directory.
Bridge REST API Route Tester, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.