MCP server

packages/mcp is a stdio MCP server (@modelcontextprotocol/sdk). It is a thin client of the OpenPons REST API: every tool maps 1:1 to an endpoint.

Status: BETA, local. Not yet published to npm; a hosted HTTP endpoint is COMING SOON.

Build & run

npm run build:mcp    # → packages/mcp/dist/index.js

Env: OPENPONS_API_URL (default https://openpons.xyz/api/v1; use http://localhost:4663/api/v1 when self-hosting).

Client configuration

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json) and Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "openpons": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/openpons/packages/mcp/dist/index.js"],
      "env": { "OPENPONS_API_URL": "https://openpons.xyz/api/v1" }
    }
  }
}

Claude Code:

claude mcp add openpons --env OPENPONS_API_URL=https://openpons.xyz/api/v1 \
  -- node /ABSOLUTE/PATH/TO/openpons/packages/mcp/dist/index.js

Tools

Tool	Kind	Parameters
`openpons_search_tokens`	read	`q?`, `sort?` new\|active\|graduated, `limit?`
`openpons_get_token`	read	`address`
`openpons_get_trades`	read	`address`, `limit?`
`openpons_get_quote`	read	`token`, `side`, `amount`, `slippageBps?`
`openpons_get_wallet`	read	`address`
`openpons_get_portfolio`	read	`address`
`openpons_get_launches`	read	`address`
`openpons_get_creator_fees`	read	`address`
`openpons_get_transaction`	read	`hash`
`openpons_prepare_buy`	prepare	`token`, `amount` (ETH), `from`, `slippageBps?`
`openpons_prepare_sell`	prepare	`token`, `amount` (tokens), `from`, `slippageBps?`
`openpons_prepare_launch`	prepare	`from`, `name`, `symbol`, `logo`, `description?`, `socials?`, `creatorTaxBps?`, `devBuyEth?`, `slippageBps?`
`openpons_prepare_claim`	prepare	`from`
`openpons_prepare_sweep`	prepare	`token`, `from`

Inputs are validated with zod (address/hash regexes, decimal strings, bounded ints) before any HTTP call.

Security semantics

Prepare tools prefix their output with an UNSIGNED TRANSACTION notice. It instructs the model to show the preview, not to claim execution, and not to ask for a signature when simulation.ok is false.
There is no signer, wallet or key parameter. The server cannot spend funds.
To execute, the user signs in the OpenPons web app or in their own wallet or signer. For autonomous agents, see the capped-signer pattern on /agents. OpenPons never ships that key.