Finexia and Claude Code

EvidenceProven by a third-party program, named and versioned: Claude Code 2.1.265, on 2026-09-10. It connected to the MCP server inside the 0.0.24 disk image, listed seven tools, called one, and received the fourteen roles the running application holds. That is a different claim from “our tests pass”, and it is the reason this page exists.

#What you need first

• The Finexia 0.0.24 disk image, installed — the client launches the binary from inside the application bundle.
• The Finexia application running. The server is a thin front: it hands the request to the app over a local Unix socket. With the app closed, it answers “Finexia is not running — open the app, then try again” instead of breaking the session.
• Claude Code installed and signed in. The proof was taken with 2.1.265; older versions negotiate a different protocol revision, which is the subject of the troubleshooting page.

#Declare the server

One command, and it is the one that was proven — not an illustration of one. It declares a local server the client launches itself as a subprocess, which is what the stdio transport is 4.

claude mcp add finexia -- /Applications/Finexia.app/Contents/MacOS/finexia-os --mcp-stdio

Claude Code stores that declaration per project, per user, or in a file shared through the repository, depending on the scope you choose 3. Nothing about Finexia depends on which one you pick.

#Check that it connected

1. Run the client’s MCP command. Finexia should be listed as connected — that status comes from a real handshake, not from the declaration existing.
2. Ask for the tools. Seven should appear, all prefixed finexia_. If the list is empty, the handshake succeeded and the surface did not: read the troubleshooting page.
3. Call the first one, finexia_agents_list. It takes no arguments and returns the roles the running application holds, with what each one owns. Fourteen came back on 2026-09-10.
4. That answer is the proof the whole chain works: the client launched the binary, the binary reached the application over a local socket, and the application answered.

EvidenceCall finexia_agents_list first, and not out of politeness: the roles decide what a mission can produce. A client that asks for a workbook without knowing which role owns that format is guessing.

#Where this stops

• CLIENT-VERIFIEDConnecting, negotiating, discovering, calling finexia_agents_listClaude Code 2.1.265 did all four on 2026-09-10, against the binary shipped in the disk image.
• CLIENT-VERIFIEDfinexia_desk_startThe window now listens. On 2026-09-10 a call from Claude Code opened a real desk in the application: one new conversation, three cards, three distinct roles, three distinct card identifiers — and the call returned started, after the window acknowledged, not before.
• CLIENT-VERIFIEDfinexia_desk_status and finexia_desk_cancelBoth exercised from the client on that run. Cancel stopped the card and its vendor CLI disappeared; the socket stayed usable straight after.
• PARTIALfinexia_desk_result and the two artifact toolsWritten and covered by tests in the core. No mission started from MCP has produced a deliverable yet — the three cards of that run ended in run failed, because the facts they needed are not served by any tool. There is nothing to point these three at, and the page will not pretend otherwise.
• AVAILABLEThe four promptsShipped and served. A prompt is a menu entry the user picks — never the model — and each one states what it refuses to invent.

LimitSo: a client can open a desk, watch it and stop it. What it cannot yet get back is a finished deliverable — the desk runs, and the run stops on data it has no tool to fetch. That is a missing tool, not a missing wire.

#Remove or replace the declaration

• Removing it is the client’s own command, not Finexia’s — nothing in the application holds a registration.
• Replacing it means removing and adding again: the declaration is a name pointing at a binary path, and a second entry under the same name would collide.
• The name matters. Two declarations merge into one namespace, and a third-party server taking the name Finexia already uses would silently replace one of them.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "finexia_agents_list",
    "arguments": {}
  }
}