# Fix your AI assistant's connection to RightMessage

If your AI assistant can't connect, opens the wrong project, or returns an error, you'll find the checks to get it working with RightMessage again.

Available on the Grow, Scale, and Pro plans.

You can narrow down a connection problem by finding the last thing your assistant did successfully. Match the error to a section below, whether it couldn't connect, opened the wrong project, or failed to make a change.

Connecting for the first time? Follow [how to connect RightMessage to your AI assistant](https://rightmessage.com/help/connect-rightmessage-to-ai-assistants-via-mcp).

## My assistant can't find the MCP server

Set the connection to HTTP or Streamable HTTP and use this hosted MCP URL:

```text
https://api.rightmessage.com/mcp/rightmessage
```

Then check the connection:

1. Check the URL for spelling mistakes or an extra path. The dashboard URL and REST `/v1` URL aren't MCP endpoints.
2. Check that your assistant supports a remote HTTP MCP server.
3. If your network filters outbound requests, check access to the server and its OAuth discovery endpoints.
4. Restart the assistant's connection flow.

The public discovery endpoints are `/.well-known/oauth-protected-resource/mcp/rightmessage` and `/.well-known/oauth-authorization-server` on `api.rightmessage.com`. These describe the connection and authorization setup. Your account still needs authorization even if that metadata loads.

## I can sign in, but approval fails

1. Review the account under **Signed in as**.
2. Check **Application** and **Redirect host** before approving.
3. If the error names the redirect URI, compare your assistant's connection settings with the [supported connection reference](https://rightmessage.com/help/mcp-authorization-reference).
4. If the token lacks `mcp:use`, restart authorization and grant that requested scope.

OAuth needs a compatible callback origin, a PKCE authorization-code flow, and the `mcp:use` scope. Don't paste an API token into an OAuth scope field. OAuth and manual bearer authentication are separate setup methods.

## My connection used to work, but now I can't sign in

1. Open **Your profile**, then **AI Connections**.
2. Check whether the OAuth client appears.
3. Reconnect from your assistant.
4. Complete browser approval again if prompted.

![AI Connections settings explaining where authorized ChatGPT and Claude clients appear before any are connected](https://rightmessage.com/help/screens/profile-ai-connections.light.webp)

An expired or revoked token can stop a previously working connection. **Disconnect** revokes the connection rather than repairing it. Use it when you're replacing or removing a client. It doesn't undo earlier edits made through that connection.

For a manual bearer connection, check **API Tokens** instead. A deleted token can't be recovered. [Create a replacement](https://rightmessage.com/help/api-tokens-and-permissions#create-a-token-in-the-app), then update the assistant's secure header setting.

## The error says no eligible project is available

Check that you've signed in with the intended account and can open the project in the dashboard. Review any expired-trial, suspension, or billing notice there. A lapsed subscription does not automatically retain MCP access.

A connection needs at least one eligible project. Each operation also needs access to the project it uses. If you can open other projects but not this one, ask the project owner to check your membership. Reauthorizing won't give you membership you don't have.

## My assistant opens the wrong project

[Confirm the project before making changes](https://rightmessage.com/help/connect-rightmessage-to-ai-assistants-via-mcp#confirm-the-project-before-making-changes). Ask your assistant to include the same explicit project ID in its `get-project-context` call, then check the returned name and website.

When a tool call leaves out `project_id`, it can use the remembered active project or the last eligible project you accessed in the dashboard. Use explicit `project_id` values when working across several projects.

There isn't a `list-projects` tool. The [configuration overview resource](https://rightmessage.com/help/mcp-prompts-and-resources) provides a way to discover accessible projects.

## A tool is missing or unknown

Check the exact tool name in the [MCP reference](https://rightmessage.com/help/topics/mcp-reference), then refresh your assistant's discovered tool list. Refresh it after changing projects or connecting an integration too.

Keep these differences in mind:

- `get-analytics-overview` is not `get-overview`.
- `list-apps` and `get-app-resources` appear only when Senja is connected to the active project.
- Tools inside Righty aren't necessarily available to an external assistant.

The normal public count is 128 tools, or 126 without the two Senja-dependent tools. Your assistant may filter or paginate its list, so check for the specific tool you need rather than relying on the count.

## A tool runs, but returns an error

Fix the request rather than repeatedly reconnecting. If the server returns an operation-specific error, the connection and authentication have already worked.

| If you see…               | What to do                                                                                                          | Why it happens                                                                |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Required argument missing | Compare the request with the tool's reference and discovered schema.                                                | The assistant left out an argument or nested field.                           |
| Resource not found        | Read the selected project's resource list and use the returned ID.                                                  | The ID was invented, deleted, or belongs to another project.                  |
| Feature unavailable       | Check the feature and project plan.                                                                                 | The project lacks a required entitlement. MCP access alone doesn't unlock it. |
| Provider error            | Read the provider's error and [verify the integration](https://rightmessage.com/help/verify-an-integration-change). | The integration rejected credentials, permissions, or a request.              |
| Rate limited              | Reduce concurrency and request frequency.                                                                           | Requests exceeded the hosted limit of 120 per minute.                         |
| Export not ready          | Use the returned job ID with `get-export-status`. Don't start another job because the first is pending.             | Exports run as asynchronous jobs.                                             |
| Publish rejected          | Read the returned error and review the full draft before retrying.                                                  | Publishing has its own project and draft requirements.                        |

## My assistant says it made a change, but my site hasn't changed

Ask the assistant to read the resource back so you can check the saved edit. Then review [drafts and publishing](https://rightmessage.com/help/drafts-and-publishing) and test the intended visitor path.

Ordinary configuration tools save a draft. They don't publish automatically. A draft split test also needs its separate start action.

Some operations, such as integration changes or feedback, take effect immediately. Before repeating an operation that changes something, read its current state to find out whether the first request succeeded.

## I still can't get it working

Send support these details:

- Your assistant's name and version.
- The configured server URL and authentication method.
- The project ID and tool name.
- Redacted arguments, the exact error, and the approximate time.
- The step that failed, such as discovery, approval, project selection, or a tool call.

Leave out API tokens, OAuth access or refresh tokens, webhook secrets, and private visitor data. Replace contact values with example addresses such as `jordan@example.com`.