Use the Faaaster MCP server with Codex or Claude

The Faaaster MCP server lets you manage your websites from your own AI agent, including Codex, Claude, Claude Desktop, and Claude Code.

For example, you can ask your agent to check a website’s status, read its logs, manage backups, work with WordPress, or start a controlled development session.

The model you use and its billing remain with your agent provider. Using the MCP server does not consume credits from Faaaster’s built-in AI assistant.

Choose your setup

• Codex with the graphical interface
• Codex CLI
• Claude or Claude Desktop
• Claude Code CLI

Requirements

Before you begin, make sure that:

• you have an active Faaaster account;
• you are an owner or administrator of at least one website;
• you have access to Codex, Claude, Claude Desktop, or Claude Code;
• MCP access has not been disabled for the website or organization.

You do not need a Faaaster API key, and you should never share your WordPress password with the agent. Authentication uses Faaaster OAuth in your browser.

MCP server address

Use the following address:

https://mcp.faaaster.io/mcp

You can also find it in Faaaster from your website under Development → AI / MCP.

Set up Faaaster in Codex using the graphical interface

The graphical setup is recommended if you use the Codex app or its IDE extension.

1. Open the MCP settings

1. Open the Codex settings.
2. Select MCP servers.
3. Click Add server.

2. Add Faaaster

Enter the following details:

Save the server, then restart Codex or the extension if prompted.

3. Authorize Codex

In the list of MCP servers, select Authenticate for faaaster.

Your browser opens the sign-in page. Sign in with your Faaaster account, review the requested authorization, then return to Codex.

4. Check the connection

In a Codex conversation, enter:

/mcp

The faaaster server should appear as connected.

Set up Faaaster with Codex CLI

1. Add the server

Run the following command in a terminal:

codex mcp add faaaster --url https://mcp.faaaster.io/mcp

Codex saves this configuration and shares it between local Codex clients that use the same configuration file.

2. Sign in to Faaaster

Start the OAuth authentication flow:

codex mcp login faaaster

Your browser opens the sign-in page. Sign in with your Faaaster account, then authorize Codex to access the MCP server.

3. Check the connection

List the configured servers:

codex mcp list

You can also open Codex and enter:

/mcp

The faaaster server should appear as connected. If Codex was already open during setup, restart the session.

Set up Faaaster in Claude or Claude Desktop

This setup uses Claude custom connectors. It works in Claude on the web and in Claude Desktop.

Free, Pro, or Max account

1. Open Customize → Connectors.
2. Click the + button next to Connectors.
3. Select Add custom connector.
4. Enter Faaaster as the name.
5. Enter https://mcp.faaaster.io/mcp as the URL.
6. Do not enter a Client ID or Client Secret in the advanced settings.
7. Click Add, then Connect.
8. Sign in with your Faaaster account in the OAuth window that opens.

Team or Enterprise account

An owner of the Claude organization must first add the connector:

1. Open Organization settings → Connectors.
2. Click Add.
3. Hover over Custom, then select Web.
4. Add https://mcp.faaaster.io/mcp without a custom Client ID or Client Secret.
5. Save the connector.

Each authorized member can then open Customize → Connectors, find Faaaster, and click Connect to authenticate with their own Faaaster account.

Enable Faaaster in a conversation

In a new Claude conversation:

1. click the + button at the bottom left of the input field;
2. select Connectors;
3. enable Faaaster for the conversation.

You can now ask Claude to list your Faaaster websites. If the connector does not appear, make sure it is connected under Customize → Connectors.

Set up Faaaster with Claude Code CLI

1. Add the server

To make Faaaster available in all your Claude Code projects, run:

claude mcp add --transport http faaaster --scope user https://mcp.faaaster.io/mcp

The user scope saves this configuration for your local account without adding it to the project files.

2. Sign in to Faaaster

You can start the OAuth authentication flow directly:

claude mcp login faaaster

Alternatively, open a Claude Code session:

claude

Then enter:

/mcp

Select faaaster, choose the sign-in option, then complete the authorization in your browser.

3. Check the connection

Run the following command in a terminal:

claude mcp list

The faaaster server should display the Connected status. In Claude Code, you can also use /mcp to check its status and available tools.

First requests to try

Once connected, enter your requests normally. For example:

List my Faaaster websites.

What is the status of example.com?

List the WordPress plugins installed on this website and indicate which ones are active.

Analyze the latest PHP errors on this website.

Create a backup of this website.

Fix the issue described on this website in a development session.

If several websites match your request, the agent asks you to select one. You can avoid this step by including the website name or domain in your request.

Confirmations and approvals

Faaaster applies the same security rules regardless of which agent you use:

• read-only operations and diagnostics can run directly;
• standard changes require confirmation in Codex or Claude;
• sensitive operations, such as restoring a backup or starting a development session, may display a Faaaster approval link;
• permissions, the target website, and the WordPress identity are checked again before each operation;
• operations remain associated with your account in the Faaaster history.

If an approval link appears, open it, review the operation, and approve it in Faaaster. Then return to your agent and ask it to continue.

Troubleshooting

The server asks you to authenticate

In the Codex graphical interface, open Settings → MCP servers, select faaaster, then click Authenticate.

In Claude or Claude Desktop, open Customize → Connectors, find Faaaster, then click Connect.

From a terminal, restart the OAuth authentication flow:

codex mcp login faaaster

or:

claude mcp login faaaster

In Claude Code, you can also use /mcp, select faaaster, then choose Re-authenticate.

The browser does not open

Copy the authorization URL displayed in the terminal and open it manually in your browser. After signing in, return to the terminal to complete the process.

No websites are available

Make sure you are using the correct Faaaster account and that this account is an owner or administrator of the relevant website. Also check the MCP policy under Development → AI / MCP.

The server appears disconnected

First, check the configured address:

https://mcp.faaaster.io/mcp

Then check the connection details:

codex mcp list

or:

claude mcp get faaaster

A 401 or 403 error usually means that you need to authenticate again or grant the required Faaaster authorization.

An operation is still waiting after approval

Return to the conversation and ask the agent to check the operation’s status and continue. Do not create a second identical operation: Faaaster keeps an operation ID to prevent duplicate execution.

Security and revocation

You can revoke MCP access from the Faaaster settings or clear the authentication from the client you use.

In Claude or Claude Desktop, open Customize → Connectors, select Faaaster, then disconnect the connector. In Claude Code, open /mcp, select faaaster, then use Clear authentication.

In Codex, remove or disable faaaster under Settings → MCP servers. To view the available Codex CLI commands, run:

codex mcp --help

Never share the following with the agent:

• your WordPress password;
• an API key or hosting secret;
• an OAuth token copied from your browser.

The Faaaster MCP server handles authentication, permissions, confirmations, and auditing itself.

Client documentation

• Configure an MCP server in Codex
• Add a custom MCP connector to Claude or Claude Desktop
• Configure an MCP server in Claude Code

Updated on: 08/09/2026