For developers
How Honawa connects to WordPress over MCP, where credentials are kept, what our gateway sees, and how to use your own AI key.
How Honawa connects to your site
- Honawa is a desktop app. It talks to your site's own MCP endpoint over HTTP, straight from your computer. There is no Honawa server between the app and your site.
- The endpoint comes from an MCP plugin on your site. Honawa finds it from the site's REST API index, so you only enter the site address.
- It signs in with a WordPress application password, or with the plugin's own API token if the plugin uses one (Easy MCP AI does).
- The password or token is stored in the operating system's keychain, not in a settings file.
- The tools Honawa can call are the plugin's "abilities". Honawa sees only the abilities you allow in the plugin.
Nothing goes through our servers except AI requests, and only when you use a Honawa code. With your own key, the app talks only to your site and your AI provider.
Tested MCP plugins
Tested on local sites with the same three requests: list drafts, create a draft, rename a page.
| Plugin | Endpoint (REST route) | Tools (read-only) | Notes |
|---|---|---|---|
| AcrossAI MCP Manager (recommended) | /acrossai/mcp |
11 (6) | Listing and creating worked. Marks read abilities as read-only, so Honawa doesn't ask before reading. |
| Easy MCP AI | /easy-mcp-ai/v1/mcp |
9 (6) | All three worked. Uses its own API token; leave Username empty. |
| Agent Abilities for MCP | /agent-abilities-for-mcp/mcp |
7 (5) | Listing and creating worked. The rename looped until the 20-step limit. Abilities start switched off. |
| MCP Adapter (default server, on its own) | /mcp/mcp-adapter-default-server |
10 (5) | No post tools, so it can't create or edit posts unless another plugin adds abilities. |
Novamira connects, but it changes posts by running PHP code you'd have to approve. Use it only on staging sites. Vibe AI (WPVibe) doesn't work: it runs MCP from its own cloud, not from your site.
More for site owners: WordPress MCP plugins: what they are and which to use.
Approvals and the activity log
- Tools the plugin marks as read-only run without asking. Everything else shows an approval card first: create, update (with the old and new values), or delete.
- If a plugin doesn't mark its read tools as read-only, Honawa asks before those too, to be safe.
- Several changes proposed together come as one card, and you can untick any of them.
- Every action Honawa took or proposed is listed under Activity. Tasks and the activity log are stored only on your computer.
- Text in posts, comments or files that tries to instruct the AI is shown as a warning and treated as data. Changes still need approval.
See Approvals, files and images.
Using your own AI key
In Connections → AI model, choose your own provider and enter:
- Provider address: the base URL of any OpenAI-compatible API, such as OpenRouter (
https://openrouter.ai/api/v1), Anthropic or OpenAI. - Model name, as your provider spells it.
- API key, stored in the system keychain.
The model must support tool calling. If it can read images, you can switch on Let the AI see images.
With your own key, requests go straight from the app to your provider. We see nothing and charge nothing. Provider settings and tested models: Use your own AI key.
What the Honawa gateway sees
With a Honawa code, AI requests go through our gateway at api.honawa.com (a Cloudflare Worker) and on to the model through OpenRouter.
For each request the gateway records which code made it, the model, the tokens used and the cost. It never records your prompts, your site content or the replies. Which models and hosts are used is in Privacy.
Source code
Honawa's source code is not public.
Security
Found a security problem? Email hello@honawa.com with the details. Please don't post it publicly until we've had a chance to fix it.
Versions and updates
The current version is 0.1.1. Honawa checks for updates and installs them from inside the app.