MCP troubleshooting
“Unauthorized” or 401 from the server
Section titled ““Unauthorized” or 401 from the server”Your assistant’s access to Linnia expired or was revoked. Reconnect:
- Claude: Settings → Connectors → Linnia → Disconnect, then Connect again.
- Claude Code:
/mcp→ linnia → Authenticate (or clear authentication first). - Codex:
codex mcp login linnia. - Cursor / VS Code: sign in again from the MCP settings when Linnia shows “Needs login”.
Access tokens last 8 hours and refresh automatically for up to 30 days. A connection also stops working when:
- the person who signed in was disabled by an owner or admin,
- the workspace is suspended or still waiting for approval,
- the connection was made with an API key that has since been revoked.
The sign-in page says something went wrong
Section titled “The sign-in page says something went wrong”| Message | What to do |
|---|---|
| Wrong email or password. | Use the same email and password as app.linnia.ai. Reset it there if needed. |
| Too many attempts… | Five wrong passwords lock the account for 15 minutes; too many attempts from one network are also paused for 15 minutes. Wait and try again. |
| That code didn’t match. | Enter the current 6-digit code from your authenticator app, or one of your recovery codes. |
| Your workspace is waiting for approval. | Linnia hasn’t approved the workspace yet. You’ll get an email. |
| Pick at least one account. | Tick at least one LinkedIn account for this assistant. |
“This connection wasn’t granted access to that account”
Section titled ““This connection wasn’t granted access to that account””When your workspace has more than one LinkedIn account, the sign-in page asks which accounts this assistant may use, and tools refuse the others. To change the selection, disconnect and connect again, then tick the accounts you want. list_accounts shows what the current connection covers.
“This connection doesn’t have the … permission”
Section titled ““This connection doesn’t have the … permission””The connection was authorised without a scope the tool needs (for example write:messages to send messages). Reconnect and allow it.
“Several accounts are connected; pass account”
Section titled ““Several accounts are connected; pass account””Tell the assistant which account to use (“use Emma’s account”), or ask it to call list_accounts first.
A write didn’t go out
Section titled “A write didn’t go out”That’s usually by design. Ask the assistant to call get_job; the answer says why:
awaiting_approval: someone needs to approve it in Approvals. The assistant can’t.scheduled: outside working hours or today’s budget is used up; it goes out at the time ineta.failed: the error explains why (for exampledoNotContact,alreadyConnected,duplicateContent,lowQualityTarget), with anexthint.
Never ask the assistant to “try again” on a queued write: Linnia de-duplicates identical requests for 15 minutes, but a reworded one becomes a second job.
Revoke access
Section titled “Revoke access”- Just this assistant: disconnect it in the assistant’s own settings.
- Everyone signed in as a person: an owner or admin can disable that person under Team; every session and connection they made stops working.
- Connections made with an API key: revoke the key under Integrations → API keys; MCP access granted with it is revoked too.