---
title: Connect your AI agent to MemberPress.ai
description: Work on your membership site from the AI you already use. Which agents connect today, which are coming, and what each connection can do.
image: https://memberpress.ai/og/help-connect-your-ai-agent.png
url: https://memberpress.ai/help/connect-your-ai-agent/
---

[Help Center](https://memberpress.ai/help/)

# Connect your AI agent to MemberPress.ai

Updated October 19, 2026

You already spend your day in an AI assistant. Connect it to your membership site and ask it about your members, your revenue and what to fix next, without opening wp-admin. Each connection is authorized on your own login, and you can revoke it at any time.

## Review site assistant rules

  

[Video](https://pub-0d3b698f9f4b4d78b4b87cc06192a2b1.r2.dev/review-site-assistant-rules-layout-v3.mp4)

The request limit and sign-in duration of **Never** shown here are test-site settings, not recommended defaults. Turning on **Assistants can make changes** does not raise the **Read only** ceiling. See [Using MemberPress.ai from your own AI client](https://memberpress.ai/help/using-your-own-ai-client/) for permission limits and connection steps.

Open **MemberPress AI** > **AI agents** > **Your assistants** to review those rules.

## Agents you can connect today

-   **[Claude](https://memberpress.ai/help/connect-claude/)**: claude.ai on the web, Claude Desktop, and Claude Code.
-   **[Grok](https://memberpress.ai/help/connect-grok/)**: the xAI API.
-   **[ChatGPT](https://memberpress.ai/help/connect-chatgpt/)**: your MemberPress.ai account.
-   **[Codex](https://memberpress.ai/help/connect-codex/)**: your MemberPress.ai account, for Pro accounts with at least one connected site. Open **Settings > AI assistants**, then the Codex section. Copy its add-server command for your environment, or use the configuration alternative shown there. Run the login command, then follow the browser consent steps to choose what Codex may do.

## Coming soon

These don’t have a tested end-to-end setup guide yet.

-   **Muse** (Meta)

## Two places an agent can connect

Every agent comes through one of two doors, and you can use both.

-   **Your site’s own endpoint.** It reads your site and builds on it, and it needs no plan. You copy its address from your site and approve the connection on your own WordPress login.
-   **Your MemberPress.ai account.** This is the advisor: cross-site advice, benchmarks and content generation. It is authorized on your MemberPress.ai login, and it needs the paid plan.

[Using MemberPress.ai from your own AI client](https://memberpress.ai/help/using-your-own-ai-client/) covers both doors in full: what each permission unlocks, and what an agent can never do.

## The consent screen

When an agent signs in to your MemberPress.ai account, it sends you to a consent screen first. The screen names the agent, the sites it will have access to and where access will be sent. It lists each thing the agent is asking to do, with a note on what that touches.

Most things start ticked, so the agent can act on your behalf. **Buy credits, or a month of Pro** starts unticked; tick it only if you want it. Untick anything you don’t want it to do, then choose **Allow access** or **Deny**. You can revoke the connection later under **Connected AI assistants** in **Settings → AI assistants**.

Grok uses an access key instead: you tick what it may do when you create the key.

Content the advisor writes lands as an unpublished draft, and changes made through your site’s own endpoint run as a dry run first. A connected AI agent gives the confirmations itself as it works. The setup confirmation is the exception: the agent is told to ask you first. Sending it makes live the draft membership levels the agent added to a new site, along with MemberPress’s Join, Checkout, Account and Login pages. You see what it did afterwards under **Connected AI assistants → Activity** in **Settings → AI assistants**. See [Which changes ask you to confirm](https://memberpress.ai/help/what-you-approve/).