Littlejohn MCP

What littlejohn-mcp does

littlejohn-mcp MCP server provides a local MCP application and interactive CLI for Robinhood Chain workflows. It reads assets and contracts, constructs USDG or Stock Token exchange decisions, requests direct confirmation in a connected wallet through WalletConnect, and records received hashes and observed transaction results in local storage.

The exchange flow requires the user to supply transaction-critical conditions such as the Stock Token, pool, sent or received quantity, exact, maximum, or minimum values, fee caps, and execution deadline. Token units are treated separately from underlying shares. Missing conditions are not selected silently.

The server also supports data signing for personal messages and EIP-712 typed data through App controls and the CLI. A model-visible tool cannot approve a wallet request by itself; the user must inspect and approve the request in the wallet.

How it works

The normal installation runs as a local stdio MCP server. Its no-argument process serves MCP, while CLI commands use the same local backend and Wallet session. The backend can remain active after an MCP host closes its connection so that wallet sessions and pending work remain available. It continues using memory and local files until explicitly stopped, terminated by the operating system, or ended by a fatal failure.

littlejohn-mcp MCP server uses a local profile and a fixed loopback port. Multiple processes sharing one profile must use compatible configuration. Runtime commands can report or stop the observed backend generation without starting a new one:

• littlejohn-mcp runtime status --json
• littlejohn-mcp runtime stop --json

Exchange requests and signing requests require an explicit interactive confirmation in the CLI or a direct App control in an MCP host. Allowances are separate decisions and wallet requests; completing one does not automatically submit the next transaction.

Setup and configuration

Install a published release with Node.js matching the package engines requirement:

npm install --global @zktx.io/littlejohn-mcp
littlejohn-mcp --help

Configure the installed command as a local stdio server:

{
  "mcpServers": {
    "littlejohn-mcp": {
      "command": "littlejohn-mcp",
      "args": []
    }
  }
}

Use the executable's absolute path if the host cannot find it through the shell environment. No website, browser login, public server, or navigable loopback page is required.

LITTLEJOHN_MCP_RPC_URL optionally selects an RPC endpoint. If omitted, the runtime's public default is used. A supplied URL must pass the current HTTPS configuration checks. LITTLEJOHN_MCP_DATA_DIR selects another local profile directory, and LITTLEJOHN_MCP_WALLETCONNECT_PROJECT_ID overrides the Wallet adapter project ID. SQLite is installed as an npm dependency; a separate SQLite service is not needed.

Tools and capabilities

The CLI includes commands for wallet connection, pool listing, exchange creation and fee replacement, activity lookup, and signing. Examples include:

• wallet connect presents a connection decision and pairing QR.
• uniswap-v4 list-pools lists packaged candidates from the current official asset snapshot; it is not a liquidity or best-route claim.
• exchange start creates a new decision and requests one interactive confirmation.
• exchange replace-fees builds a replacement decision from an independently read pending request.
• activity get and activity list read local records, while activity inspect rechecks the chain within a finite wait.
• signing start reads a user-owned JSON payload for an interactive signing decision.

Limitations and notes

Exchange actions are implemented, but Robinhood Wallet transaction and replacement behavior has not been qualified. The package does not claim executable or receipt-verified support. Physical qualification with Robinhood Wallet and each MCP host application is incomplete.

A host without direct App controls cannot authorize a transaction. CLI exchange confirmation requires both input and output to be a TTY, so flags, redirected input, and JSON output cannot approve a transaction. Local activity records are not the same as chain verification; use the explicit inspection command when a chain recheck is needed.

Do not treat a stop acknowledgement or missing listener as proof that resources were released. For uncertain transactions or signing requests, inspect the original operation after recovery rather than resending it. Keep RPC credentials in the MCP host's secure configuration instead of command arguments.