How to troubleshoot an MCP connection
Find the problem in the tables below. Each row says what is happening and how to fix it.
Connecting
| Problem | Cause | Fix |
|---|---|---|
| “This client could not be verified. Only supported AI clients can connect to Drum.” | The client cannot use Sign in with Drum | Use an API token if the client accepts one. See Supported clients |
| “This connection request has expired.” | The consent screen was open too long | Start the connection again from the client |
| The client asks for a client id and secret | It needs a confidential OAuth client, which Drum does not offer | Leave them empty. If it requires them, use an API token |
| The client cannot reach the server | A wrong URL, or a firewall | Check the URL is exactly https://app.getdrum.com/api/v1/mcp. On a managed network, ask IT to allow app.getdrum.com |
| The client says the server needs SSE, or runs a local command | The client expects a local or SSE server | Use the HTTP (Streamable HTTP) option of the client. Drum has no local server |
Signing in
| Problem | Cause | Fix |
|---|---|---|
401 from the endpoint |
The token is missing, wrong, expired or revoked | Check the Authorization: Bearer header. Create a new token, or reconnect the client |
401 “This endpoint requires an account-scoped API token” |
The token was made before tokens had an account | Create a new token |
403 “Account access revoked” |
You were removed from the account | Ask an account admin |
| The connection stopped after a long break | A Sign in with Drum connection unused for 30 days expires | Connect the client again |
| The assistant works in the wrong account | The connection or token belongs to another account | Connect again and choose the right account, or use a token made in that account |
Tools
| Problem | Cause | Fix |
|---|---|---|
| A tool you expect is missing | Its toolset is not selected, or your role does not allow it | Check the toolsets on Connected Agents or the token. If the toolset is selected, ask an admin about your role |
| The assistant says a tool is in another toolset | tool_not_selected |
Add that toolset (see Choose toolsets) |
| You changed the toolsets, but the tools did not change | The client read the tool list when it connected | Start a new chat, reconnect the server, or restart the client |
| The assistant can read but not change anything | A read-only connection, or a role with only api_read |
Check Access on Connected Agents. Reconnect and allow write access, or ask an admin to add api_create and api_update to your role |
| Setup, Templates or Proposal templates is not offered | They are on only where Drum has turned on account setup through the API | Ask Drum support |
| The Beat tools are missing | Beats are not on for the account | Nothing to fix |
| The assistant picks the wrong tool | Too many tools selected | Deselect toolsets you do not need. Keep the total under 30 |
Calls
| Problem | Cause | Fix |
|---|---|---|
“Not permitted” (not_authorized) |
Your role does not allow the work | Ask an admin. Retrying does not help |
| A record is “not found” | It does not exist, or you cannot see it | Check you can open it in Drum. If you cannot, ask for access |
timesheet_locked |
The timesheet week is locked | Ask a timesheet manager to unlock it |
conflict |
The record changed, or another request is using it | Ask the assistant to read the record again and retry |
conflict with rate_limited, or HTTP 429 |
Too many requests | Wait a minute. The limit is 300 API requests a minute for each account |
internal_error |
Drum hit an unexpected error and has a report of it | Ask the assistant to read the record again before it retries. If it keeps happening, contact Drum support |
Still stuck
Contact Drum support with the client’s name, the time it happened, and the error message. Never send your API token.