Invisico runs a Model Context Protocol (MCP) server, so AI agents and MCP-aware tools — Claude Code, Claude Desktop, Cursor, and others — can convene a council, read your sessions, and follow up, using the same account you use on the web.
Premium feature. Agent Access is enabled per account. If the tools return
ENTITLEMENT_REQUIRED, your plan doesn't include MCP access yet. 1. Create a token
- Sign in at invisico.ai.
- Go to Settings → Agent Access.
- Click Create token, name it (e.g. "Claude Code – laptop"), choose scopes (start with council:read and council:write), and create it.
- Copy the token now — it's shown once and starts with
inv_pat_. Store it like a password.
2. Point your client at the server
The MCP endpoint is:
https://mcp.invisico.ai/mcp/Keep the trailing slash. Without it, some clients drop the auth header and you'll get a 401.
Claude Code
export INVISICO_MCP_PAT="inv_pat_your_token_here"
claude mcp add --transport http invisico https://mcp.invisico.ai/mcp/ \
--header "Authorization: Bearer $INVISICO_MCP_PAT" \
--scope user Then start a new Claude Code session (MCP servers connect at startup). Verify with claude mcp list (it should show connected) or /mcp inside a session.
Cursor, Claude Desktop, and other MCP clients
Add an HTTP (Streamable HTTP) MCP server with this shape:
{
"mcpServers": {
"invisico": {
"type": "http",
"url": "https://mcp.invisico.ai/mcp/",
"headers": { "Authorization": "Bearer inv_pat_your_token_here" }
}
}
}Check your client's docs for where this config lives, then restart the client.
3. What you can do
- list_counselors — see who you can convene.
- start_council — start a council on a problem.
- get_session_status — check whether a council has finished.
- get_session_transcript — read a finished council.
- list_sessions — list your recent sessions.
- retry_session / recover_session — recover an errored session.
Councils run asynchronously: start_council returns a session id straight away — poll get_session_status until it's complete, then read it with get_session_transcript.
Troubleshooting
- 401 Unauthorized — check the trailing slash and that the token is current. A wrong token shows as a failed connection, not a login prompt.
ENTITLEMENT_REQUIRED— your plan doesn't include Agent Access yet.RATE_LIMITED/CAPACITY— you're going too fast or the council pool is busy. Back off and retry; both are normal.- Revoke a token — Settings → Agent Access → revoke. It takes effect immediately. Create one token per tool/machine so you can revoke them individually.