MCP overview
Memberfy's MCP server lets Claude, ChatGPT, Cursor and Claude Code run your community from a conversation, with your role, in a single community, and with confirmation before anything touches money or deletes. What it is, what it's for, how it works, what it can and can't do, and an example from request to result.
MCP (Model Context Protocol) is the open standard AI assistants use to operate other systems. Memberfy has an MCP server at https://api.memberfy.net/mcp. Once your assistant is connected to it, it stops just giving advice about your community and starts doing the work inside it. You describe what you want in a conversation; it reads what it needs, creates things in the right order and tells you what it did.
What it's for
People who run communities spend much of their time setting things up: the space for a new course, the modules and lessons, the sales page, this month's event with its ticket, the plan with monthly and annual options, the campaign coupon. Each of those is a sequence of screens and forms. With MCP, it's one request.
| Who | What they ask the assistant | What happens in Memberfy |
|---|---|---|
| Online school | "Build the course Excel from Scratch with 4 modules and 3 lessons in each, and a R$ 297 product in up to 10 installments" | A Courses space, the course, 4 modules, 12 lessons and the product as a draft, unlocking the space |
| Group mentoring | "Create the Mentoring plan with a R$ 390 monthly option and a R$ 3,900 annual option, with a 6-month contract on the monthly one" | Two billing options and the plan with both, as drafts |
| Events community | "Create the in-person meetup on 11/15 at 7 p.m. in São Paulo, with 80 tickets at R$ 60" | The Events space, the event and the ticket with a stock of 80 |
| Coworking | "Who joined the community this week? Write a welcome post in the Feed mentioning each of them" | The list of new members and the post in the Feed |
| Any community with sales | "How much did we sell in the last 90 days, by product? Make a chart" | The sales summary, which the assistant turns into a table or a chart |
The assistant also reads: members, spaces, posts and comments, events and participants, courses, plans, products, coupons and, for those with access, sales, subscriptions, statement, balance and payouts. Answering "who confirmed for Thursday's event?" becomes a question, not a search through the dashboard.
How it works
Three rules that define everything
1. The assistant acts with your role. It comes in as you, with the role you have in that community, checked on every call. A connected moderator can pin posts and create events, but not create plans; a member can post and comment wherever they already could. If your role changes in the dashboard, the assistant changes with it; if you leave the community, the connection stops working. MCP has no permission rules of its own: every action goes through the same checks as the screen. See Roles and permissions.
2. One connection, one community. When you connect, you choose one community, and the assistant only sees and only touches that one. To work in another, you make another connection. See Authorize and disconnect.
3. Revocable at any time. In My Account › AI assistants (/account?tab=assistants), one click on Disconnect cuts access immediately. The owner and admins also see and disconnect any assistant with access to the community, in Settings › AI assistants.
The tools
The server offers 188 tools, organized by subject, and covers every module of the community: what the app lets you do, the assistant does through the conversation. It only sees the ones your role can use: a member's list is much shorter than an owner's.
| Subject | What you can do | Examples |
|---|---|---|
| Community and structure | The connection's context, sections and spaces (create, reorder, delete, who sees them), opening an app link, the community settings | get_community_context, create_space, update_space_access |
| Content and engagement | Search, publish, edit, move and delete posts and comments, react, pin, gallery | create_post, move_post, create_comment |
| Courses | Build a whole course, edit and delete modules and lessons, enrollment and progress | create_course, update_lesson |
| Events | Create events with tickets, edit them, live streaming, see who's going | create_event, start_live_stream |
| Members | Invite one person or a class, change roles, remove, groups, tags and org chart | invite_members, update_member_role, create_group |
| Sales and plans | Plans, options, add-ons, products, prices, coupons and downsell, as drafts until approval | create_plan, update_coupon |
| Subscriptions | Who subscribes to what, complimentary access, discounts, extensions and cancellations; your own subscriptions | list_subscriptions, manage_my_subscription |
| Finance | Sales, statement, balance, payouts and the fee | get_sales_summary, request_payout |
| Certificates | Templates with the preview in the conversation, issuing to the class, revoking | create_certificate_template, issue_certificate |
| Call for papers | The whole cycle: opening the call, committee, scores, decision, negotiation, schedule and voting; and the proposer's side | create_call_for_papers, review_proposal, submit_proposal |
| Reports and charts | Sales, MRR, active members, engagement and the ranking, events and courses, with the chart in the conversation | sales_report, community_overview |
Each tool either only reads, changes something right away or asks for your confirmation before acting; each one's badge is in the list.
The full list, with the minimum role for each, is in Tools.
After showing data or finishing an action, Memberfy suggests to the assistant up to three next steps that fit what came back and your role. See Next steps. In Claude, eight frequent requests are also ready in the menu: see Ready-made recipes in the menu.
Money and deletions only with your yes
No money or deletion tool acts on the first call. It returns a summary (the coupon, the discount, the validity; the current and the new price; the payout amount and the balance) and a confirmation code. The assistant shows you the summary, you reply "yes", and only then does it repeat the call with the code. The code lasts 10 minutes, works once and only with the same values as the summary. Everything else (invites, roles, settings, certificates) runs on the first call, like a click in the dashboard. See Money and confirmation.
What never comes out
The assistant sees what your role sees, and nothing more. In amounts, the platform fee shows up; internal processing costs are not part of any response, not even for the owner.
An example, from request to result
Marina owns the community Planilhas que Pensam. She connected Claude and wrote:
Build the course "Excel from Scratch" in the courses space that already exists: 3 modules (Basics, Formulas, Pivot tables), with 3 video lessons in each. Also create the product to sell the course for R$ 297 in up to 10 installments, but leave it as a draft.
What the assistant did, tool by tool:
| # | Tool | Why | Result |
|---|---|---|---|
| 1 | get_community_context | Find out which community and role it has, and locate the sections and spaces | Owner; section Learn with the Courses space (module courses) |
| 2 | create_course | Build everything at once, with space_id of the Courses space, the 3 modules with 3 video lessons each, and sale with price: 297, max_installments: 10 | The course, 3 modules, 9 lessons and the Excel from Scratch product as a draft, unlocking the Courses space |
And it replied:
Done. I created the course Excel from Scratch in the Courses space, with the modules Basics, Formulas and Pivot tables and 3 lessons in each (9 in total). The product Excel from Scratch, R$ 297.00 in up to 10 card installments, is a draft: when you want to start selling, just ask me to publish it. The lessons don't have content yet; you add that in the dashboard.
In Memberfy, Marina finds the course in the space, and the product in Monetization › Products, as a draft. If she says "go ahead and publish", the assistant calls publish_product. Had any step failed halfway through (for example, if the given space weren't a courses space), create_course would have undone everything it had already created and explained why, without leaving a half-built course behind.
More ready-made requests, with the expected sequence of tools, are in Recipes.
What it can and can't do
| It can | Not yet |
|---|---|
| Create sections, spaces, posts, comments and reactions; pin posts | Schedule a post for later |
| Create, edit and delete courses, modules and lessons (title, type, duration) | Save a lesson's content (text, video) |
| Create online, in-person or hybrid events, with tickets | Automatically add ticket buyers to the participant list |
| Create billing options, products and plans with add-ons; publish and unpublish; change your own plan (with confirmation) | Change another subscriber's plan |
| Create coupons, change prices, request and cancel payouts, cancel subscriptions (with confirmation) | Issue refunds |
| Invite one person or a class, change roles, organize groups, tags and the org chart (with confirmation to remove someone) | Moderate several items in one call (the assistant moderates one at a time) |
| Read sales, subscriptions, statement, balance and payouts; change name, colors, logo, SEO, language and entry rules | Change the domain and integrations |
| Create certificate templates and issue to a class; decide call-for-papers proposals; change the ranking and the store | Change another subscriber's plan (each one changes their own) |
What it can't do yet stays in the dashboard, as always. See Common problems.
Who can use it
Anyone with a Memberfy account and a role in a community: what the assistant can do depends on that role.
| Role | In practice |
|---|---|
| Owner and Admin | Everything MCP offers: build structure, courses, events, plans, coupons; see and touch money, with confirmation |
| Moderator | Read the community and members, post, comment, pin posts, create events without tickets |
| Finance | Read sales, subscriptions, statement, balance and payouts; cancel subscriptions, with confirmation; post and comment |
| Member | Read what they already see, post where they already could, comment and react |
Where to start
- Connect your assistant: Claude, ChatGPT or Claude Code and Cursor.
- Ask something read-only first, to check the connection: "Which community are you connected to, and with what role?".
- Try a recipe.
- Read Security and limits before giving access to other people on the team.
Frequently asked questions
Do I need to know how to code? No. In Claude and ChatGPT, connecting means pasting an address and clicking Allow. The API is for those who want to integrate with code; MCP is for those who want to talk.
Does the assistant remember what it did yesterday? Remembering is up to the assistant, depending on the conversation. Memberfy keeps the result: whatever was created is in the dashboard, and every action of the assistant is recorded and shows up for the owner and admins in Members › Logs. See Activity logs.
Can the assistant delete things?
Yes, with your confirmation. There are tools to delete posts, comments, sections, spaces, events, courses, groups, tags, certificates and more (they all start with delete_, remove_, revoke_, withdraw_ or cancel_), and none of them acts on the first call: it shows what will be deleted, you say "yes", and only then does the assistant repeat the call with the code. It is the same two-step confirmation used for money; see Money and confirmation. The composite tools only undo what they themselves just created, when a step fails.
What if the assistant misunderstands? Anything that doesn't involve money or deletion happens right away, as if you had clicked: check the result and fix it in the dashboard or by asking again. Anything that involves money or deletes only happens after your yes to the summary.
Does it cost anything? The MCP server is part of Memberfy. The assistant (Claude, ChatGPT, Cursor) has its own plans.