WPGetAPI alternative
WPGetAPI Alternative for AI Clients Calling In
WPGetAPI sends requests from WordPress out to other APIs, and shows the answers with a shortcode, a template tag, or a block. It has more than 10,000 installs and a free core. WordPress MCP Connector faces the other direction: it lets ChatGPT, Claude, Cursor, or Windsurf call in, with OAuth sign-in and profiles that decide which tools each connection can use.
What makes it different
- Opens WordPress to your AI client
- Free, no Pro tier
- OAuth 2.0 with PKCE
- Profiles per connection
- Reaches any plugin's Abilities
- Your server, no middleman
Cascadia vs WPGetAPI at a Glance
Three Questions That Decide It
Which Way Does the Data Travel?
Do Pages Need Live Remote Data?
Should an Agent Edit Posts and Settings?
Side by Side
| WPGetAPI | Cascadia | |
|---|---|---|
| Direction | –Outbound calls to external APIs (October 2026) | Inbound calls from AI clients |
| Price | Free core, PRO from $65 a year (October 2026) | $0, GPL v3 |
| Remote data on pages | Shortcode, template tag, or block (October 2026) | ×Not its job |
| AI and MCP | ×Not mentioned on the pricing page (October 2026) | MCP endpoint, ChatGPT and Claude via OAuth |
| Authentication | –Keys, tokens, basic auth; OAuth is an add-on (October 2026) | OAuth 2.0 with PKCE built in |
| Access limits | ×Not applicable to inbound calls | Profiles plus the WordPress role cap |
| Editing site content | ×Imports via a paid add-on (October 2026) | Core tools for posts, pages, media, and more |
| Support | Included on every plan (October 2026) | –Setup guide and documentation |
Direction
Price
Remote Data on Pages
AI and MCP
Authentication
Access Limits
Editing Site Content
Support
What Ships in the Free Plugin
WPGetAPI keeps its core free and sells Pro at $65 a year for one site and Pro Plus at $125 for unlimited sites (October 2026). The Connector has no Pro tier, so the list below is the whole product.
- An inbound MCP endpoint, the reverse of an API client
- Tools to read and edit posts, pages, media, and comments
- Tools for users, menus, taxonomies, plugins, themes, and settings
- Abilities from any plugin, each switched off until you enable it
- Profiles from read-only upward
- OAuth 2.0 with PKCE, with no key to paste
- Application Passwords for Cursor and Windsurf
- A capability check on every call
- Encrypted secrets and tokens that expire and refresh
- Client setup guidance inside Settings, MCP Connector
What the Connector Adds for AI Work
An API client plugin fetches data for a page. An MCP server lets an agent act on the site.
Calls in, Not Out
WPGetAPI lists GET, POST, PUT, PATCH, and DELETE requests to an external API (October 2026). The Connector accepts requests from an AI client to WordPress itself.
Agent Sign-In That Is Not a Pasted Key
WPGetAPI supports API keys, bearer tokens, basic auth, and username and password, with OAuth 2.0 as a separate add-on (October 2026). ChatGPT and Claude sign in here with OAuth 2.0 and PKCE.
Tools for Editing, Not Just Display
WPGetAPI output goes to a shortcode, template tag, or block. The Connector's tools create and edit posts, pages, and media, and can duplicate any page, post, or product as a draft.
A Permission Layer
Profiles pick the tools per connection, and the WordPress role of the signed-in user caps every call.
Who Should Read This Comparison
Sites Using WPGetAPI for Content
You display remote data on pages. If you also want an assistant to help manage that content, the Connector is a separate add-on for you.
Teams Hoping an API Plugin Fits AI
WPGetAPI's pricing page does not mention MCP or AI (October 2026). Connecting an agent to WordPress needs an MCP server of its own.
Agencies on the Pro Plus License
The $125 unlimited-site license covers outbound API work. The Connector can sit on every client site free, covering the inbound side.
Choose WPGetAPI if
- Pages need live data from outside APIs
- You want caching and chaining of API calls
- No AI client has to reach the site
Choose Cascadia if
- An assistant should edit or audit the site
- You want ChatGPT and Claude to sign in with OAuth
- You want a read-only research connection
How to Add the Connector Beside WPGetAPI
- 1
Leave Your Endpoints Alone
Nothing in WPGetAPI changes. Its setup, endpoints, and shortcodes keep working.
- 2
Install and Choose a Profile
Add the Connector from the WordPress directory, open Settings, MCP Connector, and begin with a read-only or content profile.
- 3
Connect an AI Client
ChatGPT and Claude take your site address as a custom connector. Cursor and Windsurf use an Application Password.
- 4
Let the Agent Audit What You Display
Ask the assistant to check pages that use your WPGetAPI shortcodes. A read-only profile lets it look without changing anything.
How WPGetAPI Works
WPGetAPI Plans and Limits
WPGetAPI connects WordPress to outside REST APIs. These details come from its pricing page and plugin listing, read in October 2026.
Taken from WPGetAPI pricing, WPGetAPI plugin listing. Checked October 2026.
What Clients Say About Working with Cascadia
“I’ve always dreaded website management, but Cascadia has done an incredible job with my WordPress site, making it one less thing for me to worry about.”
“I’ve worked with Cascadia for several years now. They are always ready to help in any way I ask and can implement my ideas with ease. A company that values their clients!”
“Cascadia has been great to work with! We recently needed some updates, and Cascadia was quick to get them completed! We highly recommend Cascadia Web Services.”
“Cascadia is very responsive and we’re happy with them as our primary IT vendor.”
“They do great work, been using for years. Prompt responses to requests.”
Weighing WPGetAPI Against the Connector?
Talk to us about your setupAsk us
WPGetAPI Alternative Questions
What WPGetAPI does, what it does not, and how the Connector fits beside it.
See WordPress MCP ConnectorStill have a question?
What is WPGetAPI?
A plugin that connects WordPress to external REST APIs without code. You define an API and its endpoints, then show results with a shortcode, a template tag, or a Gutenberg block. It lists 10,000+ active installations (October 2026).
What does WPGetAPI cost?
The core plugin is free. PRO is $65 a year for one site and PRO Plus is $125 a year for unlimited sites, both billed annually until cancelled and listed excluding VAT (October 2026).
What does WPGetAPI Pro add?
Actions, Tokens, dynamic variables, chaining API calls, caching, HTML formatting, nested data retrieval, Base64 encoded auth, and XML format. OAuth 2.0 and API to Posts are separate paid add-ons (October 2026).
Does WPGetAPI support AI or MCP?
Its pricing page does not mention MCP or AI (October 2026). It can call any REST API, including an AI provider's, but it does not give an AI client a way into your site.
Which request methods does WPGetAPI send?
GET, POST, PUT, PATCH, and DELETE, with query string, header, and body parameters. Authentication in the core covers API keys, bearer tokens, basic auth, and username and password (October 2026).
What happens if I stop paying for WPGetAPI Pro?
The plugin keeps working, but you lose updates and support for the premium plugin. Licenses auto-renew and can be switched to manual renewal (October 2026).
Where does WPGetAPI beat the Connector?
For fetching live remote data into pages, it is far more capable: unlimited endpoints, caching, token handling, and a block. The Connector sends no requests to outside APIs at all.
Which is for inbound and which for outbound?
WPGetAPI is outbound: WordPress asks another service for data. The Connector is inbound: an AI client asks WordPress to read or change something. Many sites need both directions.
Can the Connector read WPGetAPI output?
An agent can read the published page that shows the output, through post and page tools. WPGetAPI settings themselves are not exposed unless it registers WordPress Abilities.
Does the Connector cost anything?
No. It is GPL v3 in the WordPress directory with no paid tier, no trial, and no license key, on as many sites as you like.
How do ChatGPT and Claude sign in?
They connect through OAuth 2.0 with PKCE and a WordPress sign-in. Since 1.6.8 there is no client ID or secret to generate first. Cursor and Windsurf use an Application Password.
Can an agent be limited to reading?
Yes. A read-only profile exposes viewing tools only. The WordPress role you sign in as is a hard cap above any profile.
What are the requirements?
WordPress 5.8 or later and PHP 7.4 or later. Version 2.2.0 is tested up to WordPress 7.1.2, and tools from other plugins need WordPress 6.9 or later.
Does anything leave my server?
No. The MCP client calls the REST API on your own site, with no relay of ours between. The AI client you connect receives only what it requests, under its own terms.
When should a site stay with WPGetAPI alone?
When all you need is remote data on pages and no assistant has to work inside WordPress. The Connector adds nothing to that job.
