ro.coderevolution/aimogen-pro
Aimogen Pro
Is the Aimogen Pro MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-04.
Manage your WordPress site from your AI assistant: posts, pages, media, comments and WooCommerce.
needs auth probed 2026-11-15 · unchanged since 2026-11-04 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Sign in with OAuth to use this server."}- Endpoint
- https://coderevolution.ro/wp-json/aimogen-relay/v1/mcp (streamable-http)
- Host
- coderevolution.ro
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://coderevolution.ro/wp-json/aimogen-relay/v1/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server coderevolution.ro, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/CodeRevolutionPlugins/AimogenMCP
- Website
- https://coderevolution.ro/docs/aimogen-pro/advanced-tools/claude-and-chatgpt/
- Registry
- active, updated 2026-11-04 · registry entry
Compare this server with others.
More servers
Servers that mention woocommerce or wordpress.
- MerchantFlow ai.merchantflow/mcp · needs auth
- SharksAPI.AI ai.sharksapi/marketing · needs auth
- Store Catalog com.agenttoolworks/storecatalog · alive
- ClearPost: WordPress SEO Agent com.clearpostplugin/wordpress-seo · needs your URL
- Easy MCP AI — Connector for Claude, ChatGPT & SEO Data com.easymcpai/easy-mcp-ai-wordpress · needs your URL
- WP Agent - WordPress publishing & management with Claude com.getwpagent/wordpress · needs auth
- com.lightsyncpro/lsp · not found
- Nikola Dikic - Full-Stack Developer, WordPress, WooCommerce, ERP Integrations com.nikoladikic/nikola-dikic · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.