connect_walletLABSCO SUMMARY
It signs with a key you place in the environment.
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.
What it is
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.
What you get
connect_wallet— connect to a Stellar wallet using its secret keylist_tokens— every token and asset held in that walletget_balances— current balances for XLM and any other assetstransfer_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
Requirements
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.
Setup effort
One command plus a key — npx chronos-mcp@latest, then supply credentials
USE CASES
01
Checking a balance without opening a wallet app
Ask for the XLM balance and get the current figure straight from Horizon.
02
Seeing everything an account holds
List the assets on the wallet, not just the native balance, before deciding what to move.
03
Sending a payment by asking for it
Name the destination, the amount and the asset; the transfer goes out on the network you configured.
4 tools
Listed in project docs. Your client may show a different list.
list_tokensget_balancestransfer_fundsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js
- STELLAR_SECRET_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx chronos-mcp@latestMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"stellar": {
"command": "npx",
"args": [
"chronos-mcp@latest"
],
"env": {
"STELLAR_NETWORK": "mainnet",
"STELLAR_SECRET_KEY": "<YOUR_STELLAR_SECRET_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"stellar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--env-file",
"<YOUR_PATH_TO_ENV>",
"chronos-mcp"
],
"env": {
"STELLAR_NETWORK": "mainnet"
},
"disabled": false,
"autoApprove": []
}
}
}
