# October 6, 2026 > You can now run your whole community by chatting with Claude or ChatGPT, set up products and plans as drafts while your business information is under review, issue certificates and follow every subscription on one screen. Buyers also get card installments with interest, and Pay now to settle a late renewal. A lot shipped at once today, and most of it changes the daily routine of whoever runs a community. The six highlights: 1. **[AI assistants](#ai-assistants-your-community-in-a-conversation)**: connect Claude, ChatGPT or Cursor and just say what you need, like building a course, opening a call for papers, inviting a cohort or checking this month's sales. The assistant covers every module of the community. 2. **[Set up monetization before approval](#set-up-monetization-before-approval)**: products, plans, options, coupons and offers start as drafts while your business information is under review; publishing and selling wait for approval. 3. **[Certificates](#certificates)**: a new space for issuing certificates to a whole cohort, with a PDF, a verification page and an Add to LinkedIn button. 4. **[Subscription management](#subscription-management)**: the list of who subscribes to what, with your team's actions on each subscription, now under **Members**. 5. **[Installments with interest and Pay now](#installments-with-interest-and-pay-now)**: the annual plan in up to 12 card installments, and late payers settle up without subscribing again. 6. **[My Account in tabs](#my-account-in-tabs)**: profile, password, communities, assistants and payments, each in its own place. After them come the other new features (among them the **Activity logs**, with who did what in the community, and the **Gamification** tab, to decide how much each action is worth), improvements and fixes, each with what changes for you. At the end, set apart, is what matters to developers, including a change to the API paths that requires updating integrations. ## AI assistants: your community in a conversation **What it is.** Memberfy now works inside Claude, ChatGPT, Claude Code and Cursor. You connect the assistant once, and from then on you write what you want the way you'd ask someone on your team. The assistant does the work in your community and tells you what it did. **Why it matters.** Plenty of tasks that take several screens today become a single request: building a course with modules and lessons, creating this month's event with tickets, opening the conference's call for papers with tracks and a committee, inviting a cohort, issuing certificates, putting together the monthly report with a chart. The assistant does what the app lets you do, in every module: reorganizing sections and spaces, moving a post, editing modules and lessons, starting an event's live stream, editing coupons and offers. And members use it too: proposing a talk, enrolling in a course, RSVPing, viewing or canceling their own subscription. The assistant acts with your role and in one community only. Anything that touches money or deletes something waits for your "yes" to a summary before it happens; everything else happens right away, like a click in the dashboard. And you can disconnect it whenever you like. **Where to find it.** In the sidebar, under your name, **My Account › AI assistants**. Owners and admins also find it in **Settings › AI assistants**, along with the list of every assistant connected to the community. **How to start.** 1. In **My Account › AI assistants**, click **Copy** next to **MCP server address**. The steps for each assistant are right below it. 2. In Claude, open **Settings › Connectors › Add custom connector**, name it *Memberfy*, paste the address, then click **Add** and **Connect**. 3. In the Memberfy window that opens, pick the community and click **Allow**. To check, ask: *"Which community are you connected to, and with what role?"* ![My Account › AI assistants](/screens/minha-conta-assistentes.png "The server address with the Copy button, and the steps to connect Claude, ChatGPT, Claude Code and Cursor (the screen in Portuguese).") **Requests you can paste into Claude.** - *"Build a 4-module course on Excel for beginners, with 3 lessons in each, and a R$ 297 product in up to 10 installments. Keep everything as a draft."* The course, modules and lessons appear in your courses space; you add each lesson's content from the dashboard. - *"Invite these 30 people to the Cohort 3 group: ana\@memberfy.net, bruno\@memberfy.net, …"* The assistant shows you the list first and, after your ok, reports who got the invite, person by person. - *"How did sales do this month compared with last month? Make a chart."* The numbers come with the chart right in the conversation. - *"Issue the completion certificate to the September cohort group."* Before issuing, it does a dry run and tells you how many people will get one and who is left out. - *"Open the call for papers for Congress 2027, with the tracks Product, Data and Career and proposals until November 30. Make Ana and Bruno reviewers for Data and show me before publishing."* The call appears as a draft in the Call for papers space, with the tracks and the committee; you publish it when you approve. In Claude, eight common requests come ready-made in the **+** button of the message box, under **Connectors › Memberfy**: the monthly report, inviting a cohort, issuing certificates, a certificate template with your brand's artwork, creating a course, creating an event, opening a call for papers and reviewing proposals. See [MCP overview](/mcp/o-que-e-o-mcp), [Connect Claude](/mcp/conectar-o-claude), [Connect ChatGPT](/mcp/conectar-o-chatgpt), [Recipes](/mcp/receitas) and [Create a call for papers](/mcp/receitas#13-create-a-call-for-papers). ## Set up monetization before approval **What it is.** Products, billing options, plans, add-ons, coupons and downsell offers can be created and configured **before** the community's Business Information is approved. Everything starts as **Draft**. What waits for approval is going live: publishing (the **Active** status) and selling. **Why it matters.** The Business Information review takes up to 7 business days. Before, that was dead time: you couldn't even create a product. Now you use the review to set up your plans, prices and coupons, and on approval day you just publish. **Where to find it.** The Business Information is under **Settings › Business Information**. Products and plans are under **Monetization › Products**, **Options** and **Plans**. **How to start.** 1. In **Settings › Business Information**, fill it in and click **Submit for Review**. 2. While the review runs, create the billing options, the plan, the add-ons and the coupons. They stay as **Draft**. 3. When the status changes to **Approved**, switch the options and products to **Active**. **Example.** Escola Excel submits its Business Information on a Monday and, that same afternoon, sets up the *Student* plan with the R$ 49 monthly and the R$ 470 annual options, the *Mentoring* add-on and the *LAUNCH* coupon. Trying to publish before approval shows: *"To publish and start selling, the community needs approved business information. Meanwhile you can create and configure everything as a draft."* Approved the following week, the school publishes the options and starts selling the same day. **Good to know.** - **Editing approved Business Information pauses sales.** It goes back to review, and checkout refuses new purchases until it's approved again. Only edit it when you need to, and submit it for review right away. - **The currency comes from the country.** A draft's price is in the currency of the Business Information's country (or in reais, without it). If the community is approved in another country, adjust the currency and the price before publishing. - **The same through the AI assistant.** If you ask for a course, an event or a plan already published and the community isn't approved yet, the assistant creates everything as a draft, undoes nothing and tells you the next step is the Business Information. - **The dashboard tells you where things stand.** While the community can't sell yet, the top of **Monetization** shows the situation (not submitted, under review with the expected answer date, rejected with the reason, or sales suspended after an edit) and the **Open Business Information** button. - **Nothing is lost if you try to publish early.** Choosing **Active** without approval saves the rest of the form and keeps the product as a draft, with the notice *"Your other changes were saved."* With approval, choosing **Active** on creation publishes right away. See [Business information](/pagamentos/informacao-comercial#before-approval-everything-as-a-draft), [Products](/monetizacao/produtos) and [Plans](/monetizacao/planos). ## Certificates **What it is.** A new space module for issuing completion, attendance or training certificates. Each person gets the certificate as a PDF and as an image for social media, with a code and a QR that anyone can check on a public page. **Why it matters.** A certificate is no longer a file you make by hand, one at a time. You issue it to the whole cohort at once, members get it by email and add it to LinkedIn in one click, and anyone who sees it can confirm it's genuine. **Where to find it.** In the sidebar, **Add Space** under a section, then the **Certificates** module. Inside the space, **Manage certificates** shows the **Issued** certificates and the **Templates**. **How to start.** 1. Create the space with the **Certificates** module and choose **Who issues**: admins only, or the whole team. 2. In **Manage certificates › New template**, choose **Platform design** (your community's logo and colors; you only fill in the text) or **Your own artwork** (your designer's image, where you mark where the name, date and QR go). Then **Activate** it. 3. Click **Issue certificate**, pick the template and, under **Recipients**, choose members, groups or tags. Confirm. **Example.** The September cohort of your *Excel from Scratch* course has finished. You issue the *Certificate of completion* to the *September cohort* group, with 8 hours of coursework: all 37 people get the email, download the PDF and post it on LinkedIn with the verification link. If someone was included by mistake, the certificate can be revoked or reissued. ![An issued certificate](/screens/certificado.png "The member's certificate: the PDF, the image, LinkedIn, the verification link and the social media images (the screen in Portuguese).") See [Certificates](/espacos/certificados). ## Subscription management **What it is.** A new tab in **Members** with every subscription in your community: who subscribes to what, how much they pay, when the next charge is and what state it's in. **Why it matters.** Your team can now handle on screen what used to have no place to be done: spotting who's past due and sending them a payment link, giving a discount for a few months, extending the period for someone who had a problem, giving a speaker a complimentary plan. Every action asks for confirmation and is logged, with who did it and when. **Where to find it.** In **Members › Subscriptions**. Owners, admins and the finance role have access; finance gets there through the **Members** menu item, which opens straight on that tab for them. Anyone who saved the old Monetization link lands in the new place. **How to start.** 1. Open **Members › Subscriptions** and use the filters: **Past due**, **Canceling**, the plan or the start date. 2. Click the row (or **View details** in the **⋮** menu) to open the subscription, with its charges, timeline and actions. 3. Pick the action: **Send payment link**, **Apply discount**, **Extend period**, **Add add-on**, **Cancel subscription** or **Reactivate**. **Example.** A speaker from your conference will be part of the community until the end of the year. In **New subscription**, pick the person and the plan, choose **Complimentary** with an end date of December 31 and confirm: she sees the plan's spaces at no charge, and the complimentary subscription ends on its own. To send the list to your accountant, **Export CSV**. ![Members › Subscriptions](/screens/assinaturas.png "Filters by status, plan and date, and each subscription with its amount, next charge and payment method (the screen in Portuguese).") See [Subscription management](/pagamentos/gestao-de-assinaturas). ## Installments with interest and Pay now ### Card installments, with interest **What it is.** Buyers can split a card payment into up to 12 installments, with Memberfy's installment interest: **4.29% in total from 2 to 6 installments** and **6.00% in total from 7 to 12**. Paying in full, by PIX or by boleto, has no interest. **Why it matters.** An annual plan fits more budgets, and you decide who pays the interest. By default it's the buyer, and you receive the same as a one-time payment. If you'd rather advertise "interest-free", the community absorbs the interest and the buyer pays only the list price. **Where to find it.** In **Monetization › Options** (or **Products**): in the option's **⋮** menu, **Edit**, then the **Payment & Pricing** tab and the **Who pays the installment interest?** field. **How to start.** 1. Open the billing option (the *Annual* one, for example) with **Edit**. 2. In the **Payment & Pricing** tab, choose **Buyer** or **Organization** under **Who pays the installment interest?** 3. Save and check your pricing page: the card shows the installment amount and the total. **Example.** Growth Annual costs R$ 1,188.00. With the buyer paying the interest, the page shows *"12× R$ 104.94 on your card (total R$ 1,259.28)"*, and you receive the same as a one-time sale. With the organization paying, the buyer pays 12× R$ 99.00, and the R$ 71.28 of interest comes out of what the community receives. ![Growth Annual checkout in 12 installments](/screens/pricing-juros.png "The installment with interest, the card total and the one-time price by PIX or boleto (the screen in Portuguese).") See [Annual in installments](/monetizacao/anual-parcelado#installment-interest). ### Pay now **What it is.** A button on the member's Billing page to pay a late renewal right away, with the saved card, another card, PIX or boleto. **Why it matters.** Before, anyone who missed a renewal had to subscribe again: a new subscription was created and the old one was left hanging. Now the same subscription is brought up to date, with the same date, coupon and add-ons. You get the payment back without chasing it by hand. **Where to find it.** For the member, in the sidebar under their name, **Billing**. The **Pay now** button only appears on a past-due subscription. **How to start.** There's nothing to set up. When someone falls behind, send them the link with **Send payment link** in subscription management. The member: 1. Opens **Billing** and sees *"The renewal was not paid. Pay to keep your access."* 2. Clicks **Pay now** and chooses **Saved card**, **Another card**, **PIX** or **Boleto**. 3. Confirms. By card, the answer is immediate; by PIX or boleto, the page updates on its own when the payment comes in. **Example.** A member's card expired and the Growth Monthly renewal failed. They get your link, open Billing, pay with a new card and, within the same minute, the subscription goes from **Past due** back to **Active**. The new card is saved for the next renewal. See [Pay now](/pagamentos/pagar-agora). ## My Account in tabs **What it is.** Your account page is now organized in five tabs: **Profile**, **Security**, **Communities**, **AI assistants** and **Payments**. **Why it matters.** Everything has its place, and each tab has its own address, so you can send someone straight to it (*"go to My Account › Security and change your password"*). Changing your password is always at hand, and a wrong current password is flagged right in the form. **Where to find it.** In the sidebar, under your name, **My Account**. **How to start.** 1. Open **My Account**. 2. In **Profile**, adjust your name, photo and bio in the community. 3. In **Security**, change your password: at least 8 characters, with an uppercase letter, a lowercase letter and a number. **Example.** A member asks where to change their password. Instead of explaining the way there, send them your community's address followed by `/account?tab=security`, and they land right on the tab. See [Account and profile](/conceitos/conta-e-perfil). ## More new features - **The community's language.** Before, only the Memberfy team could change the community's main language, which is the language of its emails. Now the owner and admins change it through the AI assistant (*"change the community language to Mexican Spanish"*) or through the API. See [Languages](/configuracoes/idiomas). - **Renewal by PIX and boleto.** Members who pay by PIX or boleto now get the renewal charge by email five days before it's due, and it also shows up on their Billing page. Fewer forgotten renewals, fewer lost subscribers. See [Renewal](/pagamentos/renovacao). - **Add-ons at checkout.** Subscribers tick the extensions on the same page as the plan and pay for everything in one payment. Existing subscribers can add an extension later from Billing, with **Add an extension**. See [Add-ons](/monetizacao/adicionais). - **Last chance (downsell).** Someone who skipped an add-on gets a discounted offer for it by email after paying. You set the discount and how long it lasts. See [Downsell](/monetizacao/downsell). - **Annual in installments and contract length.** The whole year in one purchase, in up to 12 card installments; and a monthly plan can have a minimum term, such as a 6-month contract. See [Annual in installments](/monetizacao/anual-parcelado) and [Contract length](/monetizacao/duracao-do-contrato). - **Coupons at checkout and on renewals.** Buyers enter the code when they pay, and a "forever" or "for a few months" coupon keeps applying on renewals without you having to remember. See [Coupons](/monetizacao/cupons). - **Copy the plan's link.** In each plan's and option's menu, **Copy link** grabs the direct address of the pricing page, ready to paste on Instagram or WhatsApp. See [Plans](/monetizacao/planos#copy-the-plan-s-link). - **Activity logs in Members › Logs.** Before, there was nowhere to see who did what. Now the owner and admins have a timeline with the team's actions on subscriptions, everything an AI assistant did in the community (connecting, disconnecting, each tool used and what was refused) and the member actions that earn points. You can filter by source, person and period, open the before → after of each action and send the filtered link to someone on the team. See [Activity logs](/membros/registros-de-atividades). - **Gamification in the dashboard.** Before, how much each action is worth could only be changed through the API. Now the owner and admins turn points on or off and change the value of each action (posting, commenting, completing a lesson, attending an event…) under **Members › Gamification**. The new value applies from the next action on, and points already earned don't change. See [Gamification](/membros/gamificacao). ## Improvements - **Order page.** Every payment now has its own page: it shows the PIX or boleto, confirms on its own when the payment comes in, and lets you cancel a PIX or boleto that won't be paid. The confirmation then shows the summary and what was unlocked, so buyers aren't left wondering. See [Checkout](/pagamentos/checkout#the-order-page). - **Billing page redone.** Members see everything about their subscription on the plan card: amount, next charge, add-ons and contract. The charge history now shows up, and they can cancel right there without contacting support. See [Member billing](/pagamentos/faturamento-do-membro). - **A clearer statement.** Each sale, payout or chargeback is now a single line, with how much it changed your balance. One click opens the line and shows what came in and each debit, such as the platform fee and installment interest. See [Balance and statement](/pagamentos/saldo-e-extrato). - **Members and Monetization reorganized.** People are now together: **Members** has the tabs Members, Subscriptions, Groups, Tags, Org chart, Gamification and Logs. **Monetization** kept the money: Dashboard, Payments, Products, Plans, Options, Coupons and Fees. **Payout account** is now called **Payments**, and **Billing options** became **Options**. See [Manage members](/membros/gerenciar-membros#the-tabs) and [Monetization overview](/monetizacao/visao-geral). - **The AI assistant asks less.** Memberfy's two-step confirmation now covers only what touches money (coupons, prices, payouts, subscriptions, offers) and what deletes, removes, revokes or cancels. Inviting, changing roles, changing settings, issuing certificates and deciding proposals happen on the first request; before issuing certificates, the assistant does a dry run and shows who gets one. Claude keeps its own permission prompt, which you can set to "always allow" in the connector settings. See [Money and confirmation](/mcp/dinheiro-e-confirmacao). - **The assistant writes with formatting.** Posts, event descriptions, the call for papers text and the proposals the assistant writes reach the app with bold, italic, lists, links and subheadings, as if they had been written in the editor. See [Markdown text](/mcp/ferramentas#markdown-text). - **CPF or CNPJ kept.** Buyers used to type their tax ID on every purchase. Now it stays on their account and comes filled in next time. See [Checkout](/pagamentos/checkout#cpf-or-cnpj-kept-on-the-account). - **Invite with a link to create a password.** People invited without an account used to get a temporary password. Now they get a link, valid for 7 days, to create their own, and every invitee gets the email, bulk invites included. See [Invite members](/membros/convidar-membros). - **Who can post.** Each space's rule (**Anyone**, **Staff** or **Admins**) wasn't always saved. Now it's stored and enforced on every post. See [Spaces](/conceitos/espacos). - **Who pays the fees.** New products and options start with **Buyer**: you receive the full price without changing anything. See [Platform fee](/pagamentos/taxa-da-plataforma). - **Links the platform sends.** Payment, certificate verification, invite and offer links have new, standard addresses. The ones already sent keep working. ## Fixes - **A plan subscribed twice.** Someone who already subscribed to a plan could buy it again. Now checkout tells them they already subscribe and, if they have an unpaid PIX or boleto for that plan, reuses it instead of creating another. See [Checkout](/pagamentos/checkout#someone-who-already-subscribes-to-the-plan). - **A paid PIX stuck on "waiting".** When the payment confirmation was slow, the order sat still. Now Memberfy fetches the result on its own, and access opens as soon as the payment is confirmed. - **Card renewal.** The subscription period could move forward before the card was approved. Now it only moves when the payment is confirmed. - **Wrong current password.** Getting the current password wrong while changing it used to sign the person out. Now the warning appears in the form, and they stay signed in to try again. - **One password rule everywhere.** Each screen asked for something different. Now it's always the same: at least 8 characters, with an uppercase letter, a lowercase letter and a number, and no special character required. See [Sign-up and access](/membros/cadastro-e-entrada). - **Reserved addresses.** A section with an address like `admin` or `pricing` hid a platform page. Now those names, and any starting with `_`, are refused when you create the section. See [Sections](/conceitos/secoes). - **Asterisks in the assistant's posts.** Before, posts created by the AI assistant showed asterisks and other symbols instead of formatting. Now the text arrives formatted. - **Reacting and commenting on a status outside a space.** Before, reacting to or commenting on a status posted outside a space gave an error. Now it works like any other. - **Product or option created twice.** Before, when creating a product or a billing option, the screen showed an error even though everything had been created, and a second click created a copy. Now creation shows success, and there's no duplicate. ## For developers This part is for anyone integrating Memberfy through code, or who wants the MCP server's technical details. None of it is needed to use what's above. ### API - **Breaking change: the community left every path.** Community routes no longer carry `/api/communities/{communityId}`: the community comes only from the `X-CommunityId` header. The old paths were removed, with no transition period, and answer 404. Without the header, the routes answer 400 with `errors[0].param = "X-CommunityId"`. - `/products`, `/coupons`, `/subscription-groups` (with `downsell-offers` and `reorder`), `/fees` and `/fees/simulate`, `/ledger`, `/payouts`, `/reports/*`, `/business-information` and `/payout-settings` move to `/api/`. - Team subscription management moves to `/api/manage/subscriptions`; `/subscriptions/me` and `/purchases/me` move to `/api/subscriptions/me` and `/api/purchases/me`. - The nested checkout is gone: use `/api/checkout/*`. E-mail stats, `/webhooks/email/stats/{communityId}`, move to `GET /api/emails/stats`. - Only the SuperAdmin routes under `/api/admin/communities/{communityId}/fee-overrides/...` and the community's own routes keep the id in the path: `PUT` and `DELETE /api/communities/{id}`, `GET /api/communities/{id}/members` and `PATCH /api/communities/{id}/settings`. - The `operationId`s didn't change, so the SDK method names stay the same; only the nine nested checkout operations are gone. Don't pass `communityId` in the SDK arguments anymore: it would go into the body. - The full before-and-after table is in [X-CommunityId](/api/x-community-id#the-paths-that-changed). - **Subscription management** at `/api/manage/subscriptions`: list, export, view the detail, create and act on each subscription. - **Pay now** at `POST /api/subscriptions/{id}/pay-now`, and confirming an order at `POST /api/checkout/purchases/{id}/refresh`. - **Installment interest** in the `calculate-price` and checkout responses, with the installment options and the total. - **Setting the invite password** at `POST /api/auth/set-password`. - **Search by title** at `GET /api/search`: posts, events, courses, sections, spaces and calls for papers, ignoring accents and case, and only what the person can open. - **Moving a post** at `PUT /api/content/{id}/move`, moderator and up; the destination must be a Content or Feed space. - **Modules and lessons** at `PUT` and `DELETE /api/courses/module/{moduleId}` and `PUT` and `DELETE /api/courses/lesson/{lessonId}`: rename, reorder, move a lesson to another module and delete, keeping progress. - **Community language** with the optional `language` field in `PUT /api/communities/{id}`: only the 10 variants (`pt-BR`, `es-MX`…); any other value returns 400. - **Monetization as drafts**: `POST /api/products` no longer requires approved Business Information (the product starts as `DRAFT`, in the currency of its country or in `BRL`). Publishing (`POST /api/products/{id}/publish`, or `PUT` with `status: ACTIVE`) without approval returns 403 with the translated message, and with a currency different from the approved one, 400 (`param: currency`). Checkout, buying an add-on and accepting a downsell refuse with 403 any product from a community without approval. - **Activity logs** at `GET /api/activity-logs` (owner and admin): the timeline behind **Members › Logs**, with the sources `team`, `assistant` and `members` and the filters `source`, `profileId`, `from`, `to`, `page` and `limit`. Each item has `actor`, `action`, `actionLabel` in the request's language, `target` and `details`; the assistant's arguments come summarized, without tokens, images or secrets. - **Diagnostics for an MCP connection** at `GET /api/oauth/connections/{id}/diagnostics` (owner and admin): the last tool list the connection received, the current one, and whether it's up to date (`listUpToDate`). See the [API reference](/api/referencia). ### MCP: technical details - **If the assistant can't find a new tool, it tells you to open a new conversation.** Some assistants keep the tool list from the start of the conversation; when Memberfy is updated afterwards, the assistant now gets that message instead of an unexplained error. Under the hood: `serverInfo.version` is now `+`; `initialize` and `tools/list` return `_meta.memberfy` with `server_version`, `tools_fingerprint` and `tool_count`; the audit gains the `session.initialize`, `tools.list` and `tool.unknown` events; and the connection diagnostics show whether the list is up to date. See [Common problems](/mcp/problemas-comuns#a-tool-is-missing-or-the-assistant-says-a-tool-doesn-t-exist) and [Server and tool list version](/mcp/ferramentas#server-and-tool-list-version). - **Logs and diagnostics through the assistant: 184 tools.** `list_activity_logs` (owner and admin, read-only) reads the activity logs with the same filters, and `profile` takes an id, an e-mail or an app link; `get_connection_diagnostics` (owner and admin, read-only) says whether the assistant's tool list is up to date (with `listUpToDate` false, reconnect). `member_activity` now also takes the profile link. The recipe [Who did what](/mcp/receitas#14-who-did-what) puts them together. See [Members](/mcp/ferramentas-membros#list-activity-logs). - **Every module: 182 tools (up from 102) and 8 prompts.** The whole call for papers (40 tools: the space's rules, opening and editing the call with tracks, days and banner, publishing and unpublishing, owners, reviewers per track, inviting speakers, submitting, editing and withdrawing a proposal, scores and progress, deciding, counter-offers, confirming in the program and voting) and the `create_call_for_papers` prompt. Structure: `update_section`, `reorder_sections`, `reorder_spaces`, `delete_section`, `delete_space`, `update_space_access` and `update_space` with `section_id`; `create_space` accepts `call4papers`. Content: `move_post` and `create_short_post`. Events: `delete_event`, `start_live_stream`, `stop_live_stream`, `rsvp_event`. Courses: editing and deleting modules and lessons, `delete_course`, `enroll_in_course`, `complete_lesson`. Gallery: list, edit, react and delete. Members: `remove_member`. Subscriptions: `export_subscriptions_csv`. Sales notices: `get_notification_settings` and `update_notification_settings`. Certificates: duplicating a template, who issues, resending the e-mail, retrying, `list_my_certificates` and `set_certificate_indexing`. Sales: editing and deleting downsell offers and coupons, `delete_product`, `delete_plan`, `reorder_plans`. A member's own side: `list_my_subscriptions`, `list_my_purchases`, `manage_my_subscription` and `get_my_points`. `search_content` now searches on the server and finds calls; `update_community_settings` accepts `language`. The 40 call-for-papers tools show up for every role, because a call's owner can be a member; Memberfy decides call by call. See [Tools](/mcp/ferramentas) and [Tools · Call for papers](/mcp/ferramentas-chamada). - **Publishing without approval doesn't undo the composite tool.** In `create_course`, `create_event` and `create_plan` with publish, a refusal for lack of approved Business Information leaves everything as a draft, returns `publish_blocked` with the reason, and `next_steps` points to the Business Information and then `publish_product`. See [Drafts before approval](/mcp/ferramentas-vendas#drafts-before-approval). - **Server** at `https://api.memberfy.net/mcp`, with OAuth authorization through the Memberfy account and the tools grouped by subject, each with a badge: read-only, changes data, or asks for confirmation. See [Tools](/mcp/ferramentas). - **English names.** Tools have English names, the same in every language (`create_post`, `list_spaces`, `issue_certificate`, `sales_report`); the title shown in Claude or ChatGPT comes in the language of whoever connected. The assistant picks up the new list in the next conversation. - **Links and search.** `open_link` understands a link copied from the app, and every id parameter accepts that link; `search_content` finds posts, events, courses and spaces by title. Posts (cover, pin), events (banner), courses (cover, status) and comments can be edited. See [Tools · Content and engagement](/mcp/ferramentas-conteudo). - **Two-step confirmation only for money and deletion.** The money tools (`create_coupon`, `update_coupon`, `update_coupon_status`, `delete_coupon`, `update_price`, `request_payout`, `cancel_payout`, `cancel_subscription`, `create_manual_subscription`, `update_subscription`, `create_downsell_offer`, `update_downsell_offer`, `delete_downsell_offer`, `manage_my_subscription`, `delete_product`, `delete_plan`) and every tool whose name starts with `delete_`, `remove_`, `revoke_`, `withdraw_` or `cancel_` require `confirmation_token`: 36 in total. Everything else runs on the first call, including `invite_member`, `invite_members`, `update_member_role`, `update_community_settings`, `update_space_access`, `issue_certificate`, `resend_certificate_email`, `retry_certificate`, `decide_proposal`, `negotiate_proposal` and `update_plan`. `issue_certificate` gained `dry_run: true`, which returns who gets one and who is skipped without issuing. Money and deletion tools carry `destructiveHint`. See [Money and confirmation](/mcp/dinheiro-e-confirmacao). - **Markdown both ways.** Post text (`create_post`, `update_post`), event description (`create_event`, `update_event`), call text (`create_call_for_papers`, `update_call_for_papers`) and proposal description (`submit_proposal`, `update_proposal`) take Markdown (bold, italic, lists, links, subheadings from level 2, quote, code) and are stored as the app's formatted text. The short post (`create_short_post`, `update_post` with `type: status`) takes only bold, italic, links and line breaks. Titles, names, comments and the descriptions of courses, products, plans, groups, spaces and sections lose the marks. An image inside the text becomes a link, and a table becomes lines. When reading, the text comes back in Markdown, with `text_format: "markdown"`. See [Markdown text](/mcp/ferramentas#markdown-text). - **Images** by URL or as the file itself (up to 5 MB; SVG becomes PNG), and space icons picked by topic. See [Images](/mcp/ferramentas#images). - **Members, groups, tags and org chart**: up to 100 invites per call, with a line-by-line result. See [Tools · Members](/mcp/ferramentas-membros) and the [Invite a class](/mcp/receitas#10-invite-a-class) recipe. - **Community settings** through `update_community_settings`: name, colors, logo, favicon, SEO and joining rules. See [Tools · Community and structure](/mcp/ferramentas-comunidade#update-community-settings). - **Certificates**: templates (platform design or your own artwork) with the preview as an image in the conversation, issuing with a dry run first, revoking, reissuing and deleting. See [Tools · Certificates](/mcp/ferramentas-certificados) and the recipes [Issue certificates to the class](/mcp/receitas#11-issue-certificates-to-the-class) and [Create a template with the brand's art](/mcp/receitas#12-create-a-template-with-the-brand-s-art). - **Call for papers, ranking, store and moderation.** See [Tools · Call for papers](/mcp/ferramentas-chamada). - **Sales and subscriptions**: editing plans and products, pausing coupons and seeing who used them, creating downsell offers, and complimentary, discount, extension, add-ons and payment link on each subscription. See [Tools · Sales and plans](/mcp/ferramentas-vendas) and [Tools · Subscriptions](/mcp/ferramentas-assinaturas). - **Reports** (`sales_report`, `subscriptions_report` with MRR, `members_report`, `engagement_report`, `events_report`, `courses_report`, `community_overview`), with data ready for charts. The finance role sees sales and subscriptions; moderators see members, engagement, events and courses. See [Reports and charts](/mcp/relatorios-e-graficos). - **`next_steps`**: after showing data or finishing an action, the response suggests up to three next steps to the assistant, based on the result and the role. See [Next steps](/mcp/ferramentas#next-steps). - **MCP prompts**: the eight recipes in Claude's menu are server *prompts*, translated and filtered by role (owner and admin 8, moderator 6, finance 3, member 2). See [Ready-made recipes in the menu](/mcp/conectar-o-claude#ready-made-recipes-in-the-menu).