# Connect Claude

> Step by step to connect Claude (claude.ai in the browser and the desktop app) to your Memberfy community, with the custom connector, the authorization, the first test, and how to turn the connector on and off in a conversation.

In Claude, Memberfy comes in as a **custom connector**. You paste the server address once, authorize with your Memberfy account, and Claude gets your community's tools in any conversation.

> [!TIP]
> The address and these steps are also in Memberfy itself. In **My Account › AI assistants** (`/account?tab=assistants`), or in **Settings › AI assistants** (owner and admin), the **Connect an assistant** block shows the **MCP server address** with a **Copy** button, and the steps for each assistant: **Claude**, **ChatGPT** and **Claude Code / Cursor** (with the command and the file snippet, under **Copy the snippet**).

## Before you start

- A Claude account on a plan that allows custom connectors. In company accounts (Team and Enterprise), adding connectors is usually done by the organization's admin in Claude.
- A Memberfy account, with a role in the community you want to connect.
- The server address: **`https://api.memberfy.net/mcp`**.

The same connector works in the browser ([claude.ai](https://claude.ai)) and in the desktop app: added in one, it shows up in the other.

## Step by step

1. In Claude, open **Settings** (in the menu under your name, in the corner of the screen).
2. Go to **Connectors**.
3. Click **Add custom connector**.
4. Fill in:
   - **Name**: *Memberfy* (or the community's name, if you'll connect more than one);
   - **Remote MCP server URL**: `https://api.memberfy.net/mcp`.
   Leave the advanced settings (OAuth client ID and secret) blank: Memberfy registers Claude on its own.
5. Click **Add**. The connector appears in the list, not yet connected.
6. Click **Connect**. A Memberfy window opens.
7. If asked, sign in with your Memberfy email and password.
8. On the authorization screen, choose the **community**, check what Claude will be able to do and click **Allow**. See [what the screen shows](/mcp/autorizar-e-desconectar#the-consent-screen).
9. The window closes and the connector shows as connected.

> [!TIP]
> Menu names may vary a little depending on Claude's version and language. The address is always the same.

## Using it in a conversation

1. Start a new conversation.
2. In the tools menu of the message box, check that **Memberfy** is turned on. From there you can turn the connector on and off, and individual tools too.
3. Ask something simple to test: *"Which Memberfy community are you connected to, and with what role?"*. Claude calls `get_community_context` and replies with the community's name, your role and the sections.

When it's about to use a tool that changes something, Claude may ask for your permission for it, once or for good. That prompt is Claude's, not Memberfy's. To stop being asked on every action, set the tool as always allowed in the prompt itself or in the connector settings (**Settings › Connectors**, under **Memberfy**), where each tool has its own choice. That doesn't turn off [Memberfy's confirmation](/mcp/dinheiro-e-confirmacao#the-assistant-s-permission) for anything that touches money or deletes, which happens regardless.

## Ready-made recipes in the menu

Memberfy gives Claude eight ready-made recipes, with title and text in your account's language. To use one:

1. In a conversation with the connector turned on, click the **+** in the message box.
2. Hover over **Connectors** and then over the **Memberfy** option: the menu shows the recipes.
3. Pick one. If it has fields (the list of people, the course title), fill them in; the optional ones can stay blank.
4. Claude receives the assembled request and carries on, with the same confirmations as always.

| Recipe | What it does | Who sees it |
|---|---|---|
| **Monthly report** | Sales, members, engagement and events of the month, with charts and suggestions | Owner, admin, moderator and finance |
| **Invite a class** | Invites a list of people at once, in a group and with tags, after showing the summary | Owner and admin |
| **Issue certificates for a class** | Issues the completion certificate to a group, with a dry run first | Owner, admin and moderator |
| **Certificate template with the brand artwork** | Creates a template from your artwork and shows the preview before activating it | Owner, admin and moderator |
| **Create a course** | Builds a course with modules and lessons and, optionally, the product that sells it, as a draft | Owner and admin |
| **Create an event** | Creates an event, with an optional ticket, and announces it in the feed after your ok | Owner, admin and moderator |
| **Open a call for papers** | Opens a call for an event, with tracks and deadlines, as a draft, and publishes it after your ok | Every role (opening depends on the space's rule) |
| **Review call-for-papers proposals** | Shows the pending proposals of a call and decides each one with you | Every role (deciding belongs to the team and the call's owners) |

A recipe only shows up for whoever can use the tools it depends on: the owner and the admin see all 8, the moderator 6, finance 3 (the monthly report and the two call-for-papers ones) and the member 2 (the call-for-papers ones, because a call's owner can be a member). The same recipes, in more detail, are in [Recipes](/mcp/receitas).

> [!NOTE]
> **Connected Claude before October 6, 2026?** The tools now have English names (`create_post` instead of `criar_post`) and gained the menu recipes. A conversation that was already open may keep the old list: open a **new conversation** for Claude to see the new names. You don't need to connect again; if the old names keep showing up, click **Connect** on the connector again.

## Two communities

Each connection belongs to one community. To use two:

1. Add a second custom connector, with another name (*Memberfy · School*, *Memberfy · Coworking*) and the same address.
2. In **Connect**, choose the other community.
3. In the conversation, turn on only the connector for the community you're working in, so Claude doesn't mix them up.

## Disconnecting

- **In Claude**: in **Settings › Connectors**, open the connector and choose to disconnect or remove it. Claude loses access, but the authorization stays listed in Memberfy until it expires or is disconnected there.
- **In Memberfy** (the sure way): **My Account › AI assistants** (`/account?tab=assistants`), **Disconnect**. It cuts access immediately. See [Authorize and disconnect](/mcp/autorizar-e-desconectar).

## Connection problems

| What happens | What to do |
|---|---|
| The Memberfy window says *"This access request isn't valid. Go back to the assistant and connect again."* | Remove the connector, add it again and click **Connect** |
| The community you want doesn't appear in the list | The account you signed in with isn't part of it. Sign in with the right account |
| The connector connects, but Claude doesn't use the tools | Check that the connector is on in the conversation, and ask explicitly: *"use Memberfy to…"* |
| Tools you expected are missing | Your role doesn't allow them. See [Tools](/mcp/ferramentas) |
| After a while, Claude says the connection failed | Click **Connect** on the connector again; if you disconnected in Memberfy, you need to authorize again |

More cases in [Common problems](/mcp/problemas-comuns).

## Related

- [MCP overview](/mcp/o-que-e-o-mcp)
- [Authorize and disconnect](/mcp/autorizar-e-desconectar)
- [Recipes](/mcp/receitas)