How do I manage my Faaaster sites from my own AI agent?
Faaaster provides an MCP server that lets your AI agent — Claude, Codex, Claude Code, Cursor… — view and act on your sites. You set it up from the site's AI / MCP tab.
The model used and its billing stay with your agent's provider. Using MCP doesn't consume your organization's AI credits.
What you can ask your agent
Check a site's status, read its logs, manage its backups, work on WordPress, or start a supervised development session.
Prerequisites
- an active Faaaster account;
- the Owner, Admin or Member role on the site — a Viewer can't open this access;
- an MCP-compatible agent;
- MCP access not disabled for the site or the organization.
You don't need any API key, and you must never give your WordPress password to the agent: the connection goes through Faaaster's OAuth authentication in your browser.
Where to set it up
The site's AI / MCP tab, in the Development group of the sidebar, brings everything together: the address to give your agent, a link to the setup guide, and the WordPress identity the agent will act under.
Two addresses, two scopes
Address | What it gives you |
|---|---|
Generic address | Lets you interact with all of your sites. |
This site's address | Targets this site directly. |
Each one comes with a Copy button.
Choose the narrowest scope that gets the job done. The site's address is enough to work on a specific project; keep the generic address for tasks that really span several sites — an audit, a cross-site search.
Set up your agent
The approach is the same everywhere: add a remote MCP server at the copied address.
Claude Code
claude mcp add --transport http faaaster <copied address>Claude, Cursor, Codex and other clients — add a remote MCP server with this address in the app's settings.
The first time you use it, your browser opens the Faaaster login page: you sign in, authorize the agent, and you're done.
No API key to generate, no secret to copy. Authorization goes through your usual Faaaster session. If a tool asks you for a Faaaster API key or your WordPress password, it's not this connector.
The View the setup guide button links to the detailed procedure for each app.
The agent's WordPress identity
The second card on the screen, AI agents' WordPress identity, decides which WordPress account the agent works under, and it's an important distinction:
- Complete reads — a global read-only administrator, enabled in one click with Enable / upgrade. It's used for all lookups, without you having to choose anything.
- Choose the WordPress user who will make the changes — the account the agent will write under. You choose it explicitly from the Choose an administrator list.
That's what makes actions traceable. Changes made by the agent will appear in WordPress under the account you designated, not under an anonymous identity.
The History button, at the top of the External development agent (MCP) card, lists past external development sessions.
If the connection is refused
Three possible causes:
- Your role on the target site is Viewer: it lets you view the site, not change it.
- Agent access is set to Disabled for your account — see Settings → Development AI agent access.
- The site itself has been excluded by its owner (Blocked for all users).
👉 How does the AI assistant work? · What can I configure in the account settings?
Updated on: 10/03/2026
Thank you!