tesseron MCP server

List every action and resource registered by currently claimed Tesseron sessions. Use this to discover what you can invoke via tesseron__invoke_action when your MCP client has not refreshed its tool list after a claim.

List every claim code the gateway can currently redeem (gateway-minted sessions waiting for claim, plus host-minted manifests with an unconsumed code). Recovery path when a previously-claimed session was invalidated mid-conversation (browser refresh, dev-server reload, resume failure) and tools/call returns "No claimed session found": call this, pick the entry whose app_id matches, then call tesseron__claim_session({ code }) to re-pair without asking the user to read the new code from the app UI. Returns an empty list when no claim is pending — in that case, ask the user to reload the app.

Read a resource exposed by a claimed Tesseron session. Prefer this over the generic ReadMcpResourceTool — it takes the Tesseron app_id + resource name directly, so the agent does not need to know the client-side MCP server identifier (which varies by how the server is mounted, e.g. "plugin:tesseron:tesseron" in Claude Code plugin installs vs "tesseron" in a raw config). Use tesseron__list_actions to enumerate available resources.

Claim a pending Tesseron session by its 6-character code (format: XXXX-XX) so its actions appear as MCP tools. Web apps display this code in their UI when the user clicks "Connect Claude".

Invoke any action on a currently claimed Tesseron session. Fallback dispatcher for MCP clients that do not refresh tools/list after notifications/tools/list_changed — lets you call `<app_id>__<action>` tools even when they are absent from the client tool list.