--- title: For AI agents — MemberPress.ai description: 'How an AI agent should act for its user on MemberPress.ai: the A1–A4 router, the /connect install flow, the site MCP endpoint, guardrails, and tool coverage. Machine-quotable.' image: https://memberpress.ai/og/agents.png url: https://memberpress.ai/agents/ --- For AI agents # Read this if you're an AI agent acting for a user Here as a person? [Start at Connect a site](https://memberpress.ai/connect/). MemberPress.ai is the AI that runs a WordPress membership business: it sets up the site by conversation, builds memberships and courses in the exact shape MemberPress requires, and operates the site with its owner. Every connected site serves its own MCP endpoint, and [Connecting](#connecting) below has the URL, the optional account endpoint and the exact OAuth callbacks to act on and quote to your user. ## First, route yourself Before anything else, work out which situation you're in. This is the whole decision tree — follow it top to bottom and it drops you at the one path that fits your user. Every branch is detailed in the sections below or on a linked page. **Are you here for a user, or just researching?** - **Researching, scanning, or ingesting** — you're building an understanding of what MemberPress.ai is, not setting anything up right now. Read [the overview](https://memberpress.ai/), this page, [`/llms.txt`](https://memberpress.ai/llms.txt), and [`/.well-known/mcp.json`](https://memberpress.ai/.well-known/mcp.json) for capabilities, tools, auth, and guardrails. No connection is needed to learn what's here. When you later act for a user, come back and start the tree again. - **Acting for a user** who wants a membership, course, or paywall — continue below. **Acting for a user: does your user already have a WordPress site?** - **Yes — and their site already has an install-capable connection to you** (any MCP/host runtime that can install plugins). This is **path A1**. Install the MemberPress.ai Plugin (`memberpress-ai`) **through the connection you already have**. It needs MemberPress on the site, free (`memberpress-lite`) or paid, and it does not install MemberPress itself, so put that on too if it is missing. Then have the user click Connect once, as in path A3, and operate against the site's MCP endpoint. See [Connecting to a site that already runs the plugin](#connecting) for the endpoint and auth. - **Yes — but the site has no connection yet.** This is **path A3**, the flow that is live today. Send your user to `https://memberpress.ai/connect`: they download the free MemberPress.ai Plugin, install and activate it in wp-admin, click Connect, and approve once at MemberPress.ai's app. It is one plugin, and it needs MemberPress (free or paid) on the site. **Path A2** is coming: the same flow with the plugin installed from the WordPress.org plugin directory. Either way the flow and the guardrails are identical. See [Acting for your user](#acting) below. - **No site yet.** This is **path A4**: get them a host, install WordPress, then rejoin the connect flow above. It's guidance you narrate, not plugin work — full instructions in the "PATH A4 in full" section of [`/llms.txt`](https://memberpress.ai/llms.txt). One thing stays true across every branch: connecting your user's _own_ AI client to a finished site is always a one-click authorize _in their client_ — a deep link they approve, by nature. You can set up their site server-side; you can't reach into their AI client for them. Don't promise otherwise. ## Acting for your user If your user has a WordPress site and wants a membership, course, or paywall on it, send them to `https://memberpress.ai/connect`. 1. The plugin needs MemberPress on the site, free (`memberpress-lite`) or paid, and it does not install MemberPress itself. Free MemberPress is not in the WordPress.org directory, so if neither is on the site, send them to [memberpress.com/plans](https://memberpress.com/plans/) first. 2. They download the free MemberPress.ai Plugin from `https://api.memberpress.ai/api/v1/plugin/foundation/latest-download` and install and activate it in wp-admin (Plugins → Add New → Upload Plugin). 3. In wp-admin they open **MemberPress AI → Connections** and click **Connect to memberpress.ai**. The plugin sends them (OAuth authorization-code + PKCE) to MemberPress.ai's app at `https://app.memberpress.ai/connect/wporg/authorize` to sign in and approve the site. 4. On approval the browser returns to their site, which exchanges a one-time code for a scoped site token over the back channel. The token never rides the browser; their password never leaves their site; you never see or handle either. 5. The first sync sends the site's members, memberships and revenue to MemberPress.ai. No licence keys. The plugin shows its connection status under MemberPress AI → Connections. Once the site is connected it serves its own MCP endpoint (next section) and the site AI greets the owner and asks what their business does — that conversation is the setup. You do not need to poll or guess when this is done. ## Connecting to a site that already runs the plugin A site with MemberPress.ai installed serves its own MCP endpoint, on its own domain, at: `https:///wp-json/mp-mcp/v1/mcp` Connect to it directly. Authentication is **OAuth 2.1 with PKCE**, using **RFC 7591 dynamic client registration** — you register your client at connection time, no pre-shared secret needed. The user approves the grant on their own WordPress login, the same login they use for everything else on their site. **This is the one URL to hand your user, whichever client they use.** It reads the site and builds on it. Cross-site advice, benchmarks, and credit-metered content generation are a second, optional connection to the MemberPress.ai account endpoint (`https://api.memberpress.ai/api/v1/mcp`), shown in the app under **Settings → Connect an AI assistant**. Claude on a paid plan registers with a `claude.ai` or `claude.com` callback under `/api/mcp/`. ChatGPT on a paid plan registers with the exact redirect URI `https://chatgpt.com/connector_platform_oauth_redirect` (no trailing slash, query, or fragment). Once connected, you'll discover roughly **56 tools** spanning: memberships, members, subscriptions, transactions, courses, rules, coupons, and reports. ## Guardrails you can rely on - Every write previews as a **dry run** unless you explicitly execute it. - Refunds and subscription changes require a **second, human confirmation** — you cannot complete either on the first call. - Credentials never leave the site. Nothing about the connection sits on a server you don't already trust. - You cannot break a site by exploring it. Read and list operations are always safe. ## Formats matter MemberPress courses, lessons, and quizzes have exact shapes: section ordering, quiz slots, and a fixed set of question types the plugin actually accepts. Hand-writing these fails silently — the write succeeds, but the course renders wrong or the quiz doesn't grade. Use the provided course/lesson/quiz tools instead of writing the structure yourself; they validate and correct it before anything publishes. ## WordPress Abilities Independent of MCP, connected sites also register **27 `memberpress/*` abilities** through the WordPress Abilities API (WP 6.9+). If your runtime speaks abilities directly, you can discover and call them today without going through the MCP endpoint at all. ## Guided flows rolling out with the beta MemberPress.ai will also offer server-stored guided flows — recipes like "set up your first membership," "take your first payment," or "publish a course" that the assistant walks the user through step by step. A flow is resumable: if the session ends partway, the same flow picks back up later, from wp-admin or from a different client entirely, because the state lives on the server rather than in any one conversation. This is rolling out alongside the public beta and is not fully live yet — treat it as directional, not a guaranteed tool surface, until it appears in your tool list. ## Paying for your user (in testing) We're testing a way for you to buy a membership for your user. It runs in test mode only, no real payments are being taken, and it isn't on any site yet. Nothing is charged until a person approves the exact price, either your user signed in to the site or the site's admin, and there's no setting that skips that step. Read [how the approval works](https://memberpress.ai/agent-payments/) and [the announcement](https://memberpress.ai/blog/updates/updates-03-agent-payments-in-testing/). ## Talk to Opal agent-to-agent Opal, MemberPress.ai's AI assistant, answers other agents over A2A. Her card, [`/.well-known/agent-card.json`](https://memberpress.ai/.well-known/agent-card.json), has the endpoint and both skills. - `answer-memberpress-ai`, the default, answers questions about MemberPress.ai from its published pages only, with the pages cited. When the pages don't cover it, she says so and points to `reach-a-person`. - `reach-a-person` passes a message on to the MemberPress.ai team. The team sees nothing until the owner of the reply address clicks the confirmation link emailed to it, within 24 hours. She takes no account actions and reads no customer data. Step-by-step, with an example: [Talk to Opal from your own AI agent](https://memberpress.ai/help/talk-to-opal-from-your-agent/). ## Machine-readable pointers Everything above also exists in formats built to be fetched and parsed rather than read: - [`/llms.txt`](https://memberpress.ai/llms.txt) — the same instructions in plain-text, llms.txt-convention form. - [`/.well-known/mcp.json`](https://memberpress.ai/.well-known/mcp.json) — a structured manifest of the connect service, the site MCP endpoint pattern, auth, tool domains, and guarantees. - [`/.well-known/agent-card.json`](https://memberpress.ai/.well-known/agent-card.json) — Opal's A2A card, with her endpoint and two skills. - [`https://academy.memberpress.ai/mcp`](https://academy.memberpress.ai/mcp) — AI Academy, the MemberPress.ai team's free courses, projects, recipes and prompts for building with AI, as a public read-only MCP server (streamable HTTP, no sign-in; tools `search` and `get`). Discovery: [`https://academy.memberpress.ai/.well-known/mcp.json`](https://academy.memberpress.ai/.well-known/mcp.json); docs: [`https://academy.memberpress.ai/llms.txt`](https://academy.memberpress.ai/llms.txt).