# Common problems

> What to do when the assistant won't connect, loses the connection, doesn't show a tool, acts in the wrong community or gets a money or deletion confirmation refused, and what MCP doesn't do yet.

The most common problems with MCP, with the cause and the way out. For each assistant's step by step, see [Connect Claude](/mcp/conectar-o-claude), [Connect ChatGPT](/mcp/conectar-o-chatgpt) and [Connect Claude Code and Cursor](/mcp/conectar-claude-code-e-cursor).

## The connection

### "Unauthorized", 401 or "token expired"

The assistant doesn't have a valid key.

| Cause | What to do |
|---|---|
| Authorization didn't finish (the window was closed before **Allow**) | Connect again from the assistant |
| You disconnected in **My Account › AI assistants**, or an admin disconnected in **Settings** | Connect again, if that makes sense |
| The connection went more than 30 days unused | Connect again |
| You left the community | The connection is no longer valid; ask to rejoin the community |
| Memberfy shut the connection down for security (an already used key showed up again) | Connect again. If it happens again, remove the connector and add it from scratch |

The access key lasts 1 hour and renews on its own; if the assistant keeps asking you to reconnect, remove the connector and add it again.

### *"This access request isn't valid"*

The consent screen got an incomplete request, or one with a return address that doesn't match. Remove the connector in the assistant, add it again and connect.

### The community doesn't show up on the consent screen

The account you signed in with isn't a member of it. Sign out of Memberfy in the browser and sign in with the right account before connecting.

## The tools

### A tool doesn't show up

The assistant only sees the tools your role can use. A moderator doesn't see `create_plan`; a member doesn't see `list_members`; finance doesn't see `request_payout`. Check your role with *"which community are you in, and with what role?"* and compare with [Tools](/mcp/ferramentas#how-many-each-role-sees).

Other causes:

- The connection was authorized **for reading only**: the create and money tools don't appear. Connect again with read and write.
- The connector is turned off in the conversation (Claude) or wasn't selected (ChatGPT).

### The assistant uses old names, like `criar_post`

On October 6, 2026 the tools got English names (`create_post`, `list_spaces`, `issue_certificate`). A conversation opened before that may keep the old list, and the call fails because the tool no longer exists. Open a **new conversation**; if that doesn't fix it, connect the connector again. The current names are in [Tools](/mcp/ferramentas).

### A tool is missing, or the assistant says a tool doesn't exist

Some assistants keep Memberfy's tool list from the start of the conversation. If Memberfy updated the server after that, the assistant keeps the old list: it doesn't see a new tool, or it tries to use one that was renamed.

1. Open a **new conversation**.
2. If that doesn't fix it, disconnect and reconnect the Memberfy connector in the assistant.

When the assistant tries to use a tool that was renamed or isn't on its list, Memberfy says so in the response itself: it gives the new name, or asks you to open a new conversation or reconnect.

The community's owner and admins can see which version of the list each connection received and whether it's up to date. For now that's in the API, in the [connection diagnostics](/api/referencia/mcp/get-oauth-connections-by-id-diagnostics), with no screen in the dashboard yet. See [Server and tool list version](/mcp/ferramentas#server-and-tool-list-version).

### *"Your role (…) does not allow this action in this community."*

The tool shows up, but that specific action is refused. For example:

- a member posting in a space with **Who can post = Staff**;
- a moderator using `create_event` with a ticket, or without giving an existing space;
- an action in a space your role can't see.

### *"The API refused (400): …"*

An invalid value: a zero price, a title that's too short, a date without a time zone, the id of something else. The message says which field. Ask the assistant to fix it and try again.

### A composite tool failed halfway

The response says which step failed and that everything was undone. Fix the cause (for example, use a space with the right module) and ask again. If the response says something **couldn't** be undone, check the listed item in the dashboard and delete it by hand.

### *"Too many calls in a short time"*

The limit is 120 tool calls per minute per connection. It happens with big requests (replying to 200 comments at once). Wait a minute, or ask in parts.

## The wrong community

The assistant created something in the wrong community because it was connected to it. Each connection belongs to one community only.

1. Ask: *"which community are you connected to?"*.
2. Turn off the wrong community's connector in the conversation and turn on the right one. If there isn't one, create a [connection for the other community](/mcp/autorizar-e-desconectar#switching-communities).
3. Delete what was created in the wrong place through the dashboard (there's no delete tool).

To avoid it: give the connectors clear names (*Memberfy · School*, *Memberfy · Coworking*) and keep only one turned on per conversation.

## The money and deletion confirmation

### *"Invalid, expired or already used confirmation, or different arguments"*

| Cause | What to do |
|---|---|
| More than 10 minutes passed between the summary and your yes | Ask again: the assistant generates a new summary |
| The assistant changed a value on the second call | Ask again; check that the new summary has the right values |
| The code was already used (the action already happened) | Check the dashboard before asking again, so you don't duplicate it |

### The assistant went ahead without asking

The money and deletion tools always return a summary first. If the assistant went ahead without showing it, it didn't follow the instructions. Check in the dashboard what was done, disconnect and reconnect, and say explicitly at the start of the conversation: *"always show me the summary before confirming anything involving money or deletion"*.

Invites, role changes, settings and issuing certificates do **not** ask for Memberfy's confirmation: they run on the first call. If you want to review them first, ask *"show me before doing it"*, and keep those tools on "ask first" in the assistant's permissions.

## What it can't do yet

MCP doesn't yet cover everything the dashboard does. These come later, and stay in the dashboard for now:

| Not possible yet | For now |
|---|---|
| Saving a lesson's content (text, video) | The assistant creates the lesson with title, type and duration; the content goes in through the dashboard |
| Editing or deleting modules and lessons | In the dashboard |
| Scheduling a post | The post goes out immediately |
| Adding ticket buyers to the participant list | The purchase unlocks the space; the person confirms attendance |
| Refunds | In the dashboard |
| Changing another subscriber's plan | Only the subscriber changes their own plan, in [Billing](/pagamentos/faturamento-do-membro#change-plan) or with `change_my_plan` |
| Moderating several items in one call | The assistant moderates one item at a time, with `moderate_item` |
| Changing the community's domain, language and integrations | In the dashboard |
| Deleting anything | In the dashboard |

## Related

- [MCP overview](/mcp/o-que-e-o-mcp)
- [Security and limits](/mcp/seguranca)
- [Tools](/mcp/ferramentas)