# MCP troubleshooting

> Fix common problems with the Emailit MCP server, from sign-in and missing scopes to wrong workspaces, Admin-only tools and clients that load too many tools.

Start by asking your assistant "Which Emailit workspace am I connected to?". It calls `get-current-workspace` and tells you the workspace, your role and the granted access, which explains most problems below.

## The sign-in page says the client is unknown

The client registration is stale. Remove the Emailit server from your AI tool and add it again so it registers a fresh client.

## A tool says it needs full access

The connection was approved with the `sending` scope only. Clients that support step-up authorization, such as ChatGPT, show the approval screen again: approve **full** access. With other clients, revoke the connection under **Account → Connected apps**, reconnect and approve full access. With an API key, use a [Full Access key](/docs/developers/api-keys/).

## Changes happen in the wrong workspace

Name the workspace in your request, for example "In Marketing, list the domains", or ask the assistant to switch: "Switch to my Marketing workspace". API keys always act on the workspace they belong to.

## A workspace is missing

The connection only covers the workspaces you allowed. Open **Account → Connected apps**, choose **Edit access** and add it, or choose **All workspaces**. If you were removed from the workspace, ask an Admin to invite you again.

## A tool says it needs the Admin role

The error `admin_role_required` means you're a Member in that workspace, and the tool manages API keys or deletes a domain. Ask a workspace Admin to do it or to [change your role](/docs/workspaces/members-and-roles/).

## The client shows too many tools or fails to load them

Some clients cap the number of tools. Load only what you need with `?toolsets=` in the server URL or the `X-MCP-Toolsets` header, for example `https://api.emailit.com/mcp?toolsets=emails,domains`. See [Toolsets and read-only mode](/docs/mcp/toolsets/).

## An email is rejected

The sender must use a [verified sending domain](/docs/domains/verification/). Ask the assistant to check the domain with `get-domain`, publish any missing records and run `verify-domain`. Until your workspace has [production access](/docs/workspaces/production-access/), you can only send to workspace members' account emails.

## Retry fails

Only bounced, failed, suppressed or held emails can be retried, within 30 days and while their content is still stored. See [Retry and forward](/docs/email-api/retry-and-forward/).

## The client shows "Method not allowed"

The server is stateless and only accepts `POST` requests. Update your client to a version that supports the Streamable HTTP transport, or use the [local server](/docs/mcp/local-server/) over stdio.

## The client keeps asking you to sign in

The refresh token expired after 60 days without use, was reused, or the connection was revoked. Sign in again from the client. If it happens repeatedly, make sure only one copy of the client uses the connection at a time.

## Still stuck?

Ask in [Discord](https://discord.emailit.com) or email [support@emailit.com](mailto:support@emailit.com) with the client name, the tool that failed and the error text.

---
Source: https://emailit.com/docs/mcp/troubleshooting/