Celina MCP

Run it locally with Node

Install Celina globally, then point your MCP client at the absolute path from which, where, or Get-Command. GUI clients (Cursor, Claude Desktop) spawn the command with a minimal PATH that often omits nvm, fnm, Homebrew, or npm’s global bin — an absolute command avoids ENOENT reconnects. Works in any stdio client. Requires Node.js ≥ 20.

1. 01. Install globally:
   $npm i -g @andrewkimjoseph/celina-mcp@latestCopy
2. 02. Copy the binary path:

   macOS / Linux

   $which celina-mcpCopy

   Windows (cmd)

   >where celina-mcpCopy

   Windows (PowerShell)

   PS>(Get-Command celina-mcp).SourceCopy
3. 03. Add to your MCP client — replace the example command with your path:

   macOS / Linux

   Copy

   {
     "mcpServers": {
       "celina-mcp": {
         "type": "stdio",
         "command": "/path/to/celina-mcp",
         "args": [],
         "env": {
           "CELO_PRIVATE_KEY": "0x...",
           "SELF_AGENT_PRIVATE_KEY": "0x..."
         }
       }
     }
   }

   Windows

   Use the .cmd shim path from where / Get-Command.

   Copy

   {
     "mcpServers": {
       "celina-mcp": {
         "type": "stdio",
         "command": "C:\\Users\\YourName\\AppData\\Roaming\\npm\\celina-mcp.cmd",
         "args": [],
         "env": {
           "CELO_PRIVATE_KEY": "0x...",
           "SELF_AGENT_PRIVATE_KEY": "0x..."
         }
       }
     }
   }

4. 04. Restart your MCP client.
5. 05. Confirm Celina is connected.

If logs show spawn celina-mcp ENOENT, path lookup was skipped or the path is stale after a Node/nvm upgrade or npm global prefix change on Windows.