> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exec.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Troubleshooting

> Fixes for the problems people actually hit when connecting an AI assistant to Exec.

Start here if the connection is not behaving. If it is working but the answers look wrong, you want [Prompts and reliable answers](/mcp/prompts-and-answers) instead.

***

## Start with this

```text theme={null}
Show me my most recent roleplay sessions in Exec.
```

| What happens                 | What it means                                                         |
| :--------------------------- | :-------------------------------------------------------------------- |
| Your sessions come back      | The connection is fine. The problem is in how the question was asked. |
| An empty answer, no error    | Almost always an unfinished sign-in. See below.                       |
| It says it has no Exec tools | Not connected, or the capability is blocked in your assistant.        |
| An error about permission    | Either blocked in your assistant, or genuinely not yours to see.      |

***

## Everything comes back empty

**This is the most common problem, and the most confusing, because nothing looks broken.** If the sign-in did not complete, the connection still appears connected and simply returns nothing. Your assistant then answers as though your workspace is empty, with no hint that anything went wrong.

The fix: disconnect Exec in your assistant, connect it again, and this time watch for the Exec sign-in page to open in your browser. Enter your email, sign in, choose a workspace if you are asked, and click **Authorize**. If no browser tab opens, look for a blocked popup.

<Tip>
  If you have several tools connected, an empty answer can also mean your assistant used a different tool. Try again starting with "Using the Exec MCP, ...".
</Tip>

***

## Exec is not offered as a connector

If your company is on a team or enterprise plan for your AI tool, somebody with owner access has to approve Exec once before it appears for anybody. Until then it will not be in your list.

Ask whoever administers your AI tool to add `https://api.exec.com/mcp` as a custom connector. It takes them a minute and grants no data access on its own: everyone still signs in individually afterwards and gets only their own Exec permissions. See [Connect your AI tool](/mcp/connect).

On an individual plan you can add it yourself.

***

## It says it cannot see Exec, or lacks permission

Two different causes.

**Blocked in your assistant.** Assistants ask permission before using a connected tool for the first time, and the choices are usually along the lines of ask every time, always allow, or block. If a capability was blocked, your assistant will say it cannot do it without explaining why. Find the per-tool permissions for the Exec connector in your assistant's settings and re-enable it.

**Genuinely not yours to see.** Skill proficiency and scenario analytics need workspace admin or group admin, and a member is refused even when asking about their own scores. Your own sessions, grades, and coach feedback are still readable. Sessions belonging to other people are not visible unless you administer their group. That is working correctly. See [What the AI can see](/mcp/what-the-ai-can-see).

***

## I cannot sign in

| Symptom                                                | Fix                                                                                            |
| :----------------------------------------------------- | :--------------------------------------------------------------------------------------------- |
| Wrong password                                         | Reset it in Exec, then reconnect. It is the same password as the app.                          |
| "Too many failed attempts"                             | Sign-in protection is shared with the Exec app. Wait for it to clear, or reset your password.  |
| Single sign-on sends you back with an error            | Usually means your email is not attached to that workspace. Ask your workspace admin to check. |
| "No active workspaces"                                 | Your account is not currently active in any workspace. Ask your admin.                         |
| "This authorization request is invalid or has expired" | The sign-in was left open too long. Start again from your assistant.                           |
| "This authorization request was already completed"     | Two sign-ins raced each other. Harmless. Reconnect.                                            |

***

## It connected to the wrong workspace

A connection is bound to the workspace you chose when you signed in. Disconnect it in your assistant and connect again, choosing the right one.

If you were never asked which workspace, you only belong to one, so that is the one you have.

***

## It did not ask me to sign in this time

Expected. If you still hold a live authorization for that assistant, reconnecting goes straight through and reuses the workspace you picked originally. To change workspace, disconnect first.

***

## Charts and dashboards do not appear

Charts need an assistant that can display interactive panels. If yours cannot, you get the numbers as text instead, which is not a failure.

If your assistant does support panels and a chart still does not appear, the first one in a session takes a few seconds to start up. Ask again.

***

## My scenario request was refused

Scenario requests are checked for content that reads as code or as instructions aimed at the assistant, and those are rejected with a note asking you to rephrase.

**If you pasted a formatted spec, that is why.** Describe the scenario in plain sentences instead: who the buyer is, what they care about, what they push back on. It works better anyway, because it gives the builder room.

***

## It cannot find the scenario it was building

Your assistant can only come back to a build for about an hour. After that, ask it to build again, or open Scenario Studio in Exec, where the conversation it started is waiting under a title beginning with "MCP:".

Two related cases: a scenario you started building inside Exec cannot be picked up by an assistant, and only the person who started a build can check on it.

***

## It says I have reached a limit

Each workspace has a cap on custom scenarios. Publishing is refused once you are at it. Archive scenarios you no longer use, or talk to us about raising the cap.

***

## It stopped working after a while

Connections refresh quietly and normally last about a month of inactivity before needing a new sign-in. Reconnecting fixes it.

If it stopped abruptly, check whether your Exec account was deactivated or removed from the workspace. That cuts access immediately, by design.

***

## Nothing here helped

Ask your assistant this and include the answer when you contact us:

```text theme={null}
Check my Exec connection and tell me exactly what came back.
```

That returns a confirmation and the Exec build you are talking to, which tells us more than a description of the symptom. Then email [hello@exec.com](mailto:hello@exec.com) with which assistant you are using, what you asked, and what came back.