> For the complete documentation index, see [llms.txt](https://developer.frontitude.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.frontitude.com/mcp/troubleshooting.md).

# Troubleshooting

Find your symptom below.

## Add to Cursor or Add to VS Code does nothing

The button opens the editor through a link. That fails if the editor isn't installed on this computer, or if your browser blocked it. Add the server to the editor's config file by hand instead. The block to paste is on the [Cursor](/mcp/connecting/cursor.md) and [VS Code](/mcp/connecting/vs-code.md) pages.

## Codex connected, but every call is refused

Codex doesn't ask you to sign in on its own. Run this once, then try again:

```bash
codex mcp login frontitude
```

## Your agent lists no tools at all

Open the ***Profile*** tab and find the connection under ***Connected agents (MCP)***. If the ***Access*** column shows ***Nothing***, click ***Tools*** and select the ones this agent needs. Each change saves immediately.

If a tool you select still doesn't appear, this connection was never approved for it. The picker can only turn off tools that were selected at the start. Click ***Disconnect***, connect the agent again, and approve the access it needs.

If the tools are selected and the agent still sees none, check the workspace switch. Ask an editor or an admin whether ***AI tools*** is on under the [***Integrations*** tab](https://app.frontitude.com/settings/integrations?utm_source=mcp-docs). If it's on, get in touch with us.

## Every call says you don't have access

Your account can't get to that content any more. Somebody may have removed you from the workspace the connection points at, or your access to that project changed. Click ***Disconnect*** on the connection on your ***Profile*** tab, connect the agent again, and pick the workspace you want.

## Your agent says a component or text isn't there

Your agent is looking something up by id, and nothing has that id. Either it's wrong, or what it named has been deleted. Ask your agent to find the component or text again rather than reuse an id from earlier in the conversation.

## Auto-translation stopped after your agent moved copy to Final

The workspace went past its translation allowance. That call translated nothing, and auto-translation is now off for everybody. Your workspace admin has the email. An editor or an admin turns it back on under ***AI translations*** on the [***Integrations*** tab](https://app.frontitude.com/settings/integrations?utm_source=mcp-docs).

## Your agent stopped working and you didn't change anything

A connection stops working after 90 days without a call. It also stops if the same agent configuration runs on a second computer, or is restored from a backup. A sign-in belongs to one copy of the agent. Connect it again.

## Nobody was emailed about a comment your agent posted

A comment posted by an agent emails nobody, even when the text names somebody with an @mention. The comment sits in the app until that person opens it.

## A call was refused for going over a limit

Try to do less at once: fewer items in one write, read a narrower part of the library, or run a count before a list. If the message names your plan's component limit, delete components you no longer need or ask an admin to upgrade your plan.

## ChatGPT doesn't accept the address

Turn on ***Developer mode*** in ChatGPT before you add a custom connector. See the [ChatGPT](/mcp/connecting/chatgpt.md) page.

{% content-ref url="/pages/zfRlJpKwImEgIwEODRDZ" %}
[Limits and errors](/mcp/limits-and-errors.md)
{% endcontent-ref %}