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.
Your agent can also:
- analyze a site's performance: latest PageSpeed scores, resource usage, and a server-side trace of a page to spot the plugin or query that costs the most;
- run a security scan: Wordfence, WordPress file integrity, search for suspicious code;
- change the settings you find in the dashboard: PHP, cache, firewall, domains, and your site's Nginx configuration files — a file Nginx rejects is put back as it was.
- undo its changes during a development session: a starting point of the site's files is recorded when the session opens; your agent can list what it changed and put a file back as it was, and if it cancels the session, it must ask you whether to put the files back. The database stays covered by the backup taken when the session opened.
Ready-made prompts
The server provides five prompts that give your agent a goal and let it choose its tools:
Prompt | What it asks for |
|---|---|
| a performance audit, cross-checked with resource usage, with ranked improvements |
| a security assessment based on evidence, without changing anything |
| plugin updates behind a restore point, then a check of the site |
| finding the cause of a problem you describe, fixing it, then checking the fix |
| opening a development session to build or change what you describe, then checking the result |
Their text is written in your Faaaster account's language. Where they appear depends on your agent; in Claude Code they are commands, for example /mcp__faaaster__performance-audit.
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/06/2026
Thank you!