# Troubleshooting

> Missing tools, insufficient-scope errors, reply attribution, and picking the right client config.

Product: Clad MCP
Source: https://docs.useclad.ai/mcp/troubleshooting

---

**The agent connects but sees no tools (or too few).**
The tool list is scope-filtered. Call `whoami` to see the granted scopes. A
read-only grant won't show write tools; admin tools require an admin grant.
Re-authorize with the scopes you need, or ask a workspace admin.

**A tool returns "insufficient scope".**
The credential is missing the resource scope for that action (e.g. `issues:write`
to reply). Reconnect with the broader scope, or use an API key that has it.

**Replies show up as the agent's name instead of mine.**
Use an **OAuth** connection rather than a shared API key — OAuth attributes
actions to the signed-in user. (A machine-user API key has no human owner to
attribute to.)

**The connection stopped working after a role change.**
That's expected. Grants follow your role live; if your role was reduced or you
were removed from the workspace, the agent's access is clamped or revoked. An
admin can restore your role, then re-authorize.

**Which client config do I use?**
Open **Settings → MCP** in the Clad app for copy-ready snippets for Cursor,
Claude Code, Claude Desktop, VS Code, Codex, and any generic remote-MCP client.