Tools

Memberfy's MCP server has 188 tools, which cover every module of the community: the assistant does what the app lets the connected person do, with their role. The assistant picks which one to use from your request on its own; this page and the subject pages are there so you know what it can do, with which role, and how to ask. The names are in English, as the assistant sees them, and they are the same in every language; the title shown in Claude or ChatGPT comes in the language of whoever connected.

#By subject

Each tool has a badge: Read-only changes nothing, Changes creates or changes something right away, and Asks to confirm only acts after your yes to a summary.

#All tools

Minimum role: the lowest role the tool shows up for. "Any" includes members. Finance is listed separately because it isn't on the same ladder as the other roles.

#How many each role sees

All 40 call-for-papers tools show up for everyone because a call's owner can be a regular member, and any member proposes, reviews or votes when the call allows it. Memberfy checks each call against the module's rules. See Call for papers.

A connection authorized for reading only sees just the role's read tools.

Seeing a tool in the list doesn't guarantee every call goes through: Memberfy checks each action as if it were done on screen. A member sees create_post, but posting in a space with Who can post = Staff is refused. See Roles and permissions.

#Shared rules

#Ids

The tools work with ids, and wherever they ask for an id they also accept the link copied from the app (see open_link). Almost every conversation starts with get_community_context, which returns the sections and spaces with their ids; the list tools return the ids of what they list. Each tool's description says where each id comes from, and the assistant chains them on its own: you ask "post in the Announcements space", it looks up the Announcements space id and posts.

#Pagination

List tools accept page (the page, starting at 1) and limit (how many per page). The response includes the items and the total, so the assistant knows whether to ask for the next page.

#Draft first

Everything that is sold starts as a draft: create_product, the product from create_course, the ticket from create_event and the options from create_plan. Nothing goes on sale without publish_product (or publish: true in the composite tool). That way you review first.

Creating doesn't depend on approved business information; publishing does. In a community without approval, a composite tool that was asked to publish undoes nothing: the course, event or plan stays as a draft, the response gives the reason in publish_blocked, and the suggested next step is to fill in the business information and publish later. See Drafts before approval.

#Idempotency in the composite tools

The three composite tools accept idempotency_key (up to 100 characters). Repeating the call with the same key returns the result of the first one, without creating anything again. It's for when the connection drops mid-call and the assistant doesn't know whether the call went through.

#Undoing when a step fails

The composite tools create things in order and, if a step fails, delete what they had already created (except when what failed was publishing without approved business information: then everything stays as a draft), newest first, and say which step failed: "The step "módulo 2" failed and everything this call created was undone." If something can't be undone, the response lists what was left behind so you can check it in the dashboard.

#Next steps

When a follow-up makes sense, the tool's response carries next_steps: up to three suggested actions, each with the tool, the reason (in the language of whoever connected) and, sometimes, the arguments ready to use. They depend on what came back and on your role: only tools you can use are included. The assistant offers these actions before suggesting anything else, and none of them happens unless you ask.

#Errors

When Memberfy refuses, the assistant gets Memberfy's message, the same one you'd see on screen:

#Server and tool list version

Every Memberfy deploy changes the server version, and the tool list a connection receives has its own fingerprint. That's how you tell whether an assistant's list is up to date.

Calling a tool that isn't on the connection's list returns a tool error (isError) asking the person to open a new conversation or reconnect; if the name is one of the old Portuguese ones, the response includes renamed_to with the new name. The call is logged in the audit as tool.unknown.

The owner and admins compare the last list a connection received with the current one at GET /api/oauth/connections/{id}/diagnostics: the listUpToDate field says whether it's up to date. See Audit.

#Ask for confirmation

Only the tools that touch money and the ones that delete (those starting with delete_, remove_, revoke_, withdraw_ or cancel_) ask for confirmation. With the Asks to confirm badge, they don't act on the first call: they return a summary and a code, and only act when the assistant repeats the call with the code, after your yes. All the others, including invites, role changes, settings and issuing certificates, run on the first call. The table above shows each one's badge. See Money and confirmation.

#Markdown text

The assistant writes and reads Memberfy text in Markdown. Memberfy converts it to the app's formatted text on the way in, and back to Markdown on the way out: the post shows in the app with bold and lists, not with asterisks.

What doesn't carry over to the app:

• An image inside the text becomes a link to the image. For a post's cover or an event's banner, use image_url (see Images).
• A table becomes lines of text, one per table row.
• Scripts, event attributes and javascript: links are removed.

Ready-made HTML is accepted too and goes through the same filter. When reading, the tools return formatted text in Markdown and mark the result with text_format: "markdown". Reading and saving the same text again changes nothing.

#Images

create_post, add_gallery_image, create_course, create_event, update_post, update_event and update_course accept the image in two ways:

• image_url: the link to an image that is on the internet. Memberfy downloads it and keeps it as if you had uploaded it in the dashboard.
• image_base64 (with image_type, optional): the file itself, up to 5 MB. It's the way to use an image the assistant generated in the conversation. SVG is accepted and becomes PNG; an SVG that points to external files is refused.

A link to a page (rather than to the image itself) is refused with "the file is not a JPEG, PNG, WebP or GIF image".

In the composite tools, a bad image doesn't undo the rest: the course or event is created without the cover, and the response gives the reason in warnings ("Could not use the image at …: the image is larger than 10 MB."). Ask again with another link, or add the image in the dashboard. In the single-item tools (create_post, add_gallery_image), a bad image prevents the creation.

#Related

• Recipes
• Money and confirmation
• Security and limits