Three of the four tools read; the fourth sends funds, and the credential that authorises it sits in your client config or a .env file, against the network you name. Use an account funded with only what you are willing to have an agent move, and decide deliberately whether `transfer_funds` should be auto-approved in your client.
A Node MCP server that talks to the Stellar network through the Horizon API. It gives an assistant four on-chain actions against a wallet you configure, and installs like any other npm package.
- `connect_wallet` — connect to a Stellar wallet using its secret key
- `list_tokens` — every token and asset held in that wallet
- `get_balances` — current balances for XLM and any other assets
- `transfer_funds` — send to another Stellar address, taking the destination, the amount and optionally an asset other than XLM
- A stdio server that runs from npx, a global install, or a Docker image
- Extension points documented for adding tools of your own
Node.js v14 or higher and npm, or Docker. Install with `npm install -g chronos-mcp` or run `npx chronos-mcp@latest` straight from the client config. It reads STELLAR_SECRET_KEY and STELLAR_NETWORK from the environment — a .env file in development, the env block in your client config otherwise, or `--env-file` when running the container. Network access to Stellar is required. MIT licensed.
One command plus a key — npx chronos-mcp@latest, then supply credentials