Connect your agent
to Solana.

Read onchain data, pay for services, and send transactions through one MCP connection.

You control each agent’s permissions and spending limit.

Get started

One connection. Less setup.

Keep provider API keys out of agent configs. Manage permissions, spending limits, and activity in LanaTools.

an API key in an agent’s configa call from an agent
todayEach agent and tool pair needs its own server, API key, and config. Add a tool and you repeat it five times.
with lanatoolsEach agent connects once, with one URL and no API keys in its config. Paid calls settle from your embedded wallet, within the limit you approve for each agent.

Connect OpenClaw, Hermes, and other MCP-compatible clients and harnesses.

how it works

Every call runs inside the rules you set.

how a call movesa call from an agentstopped by your rules
mcp.lanatools.shCursorClaudeCodexGrok botOthersPaymentsPaymentsOnchain dataOnchain dataTransactionsTransactionsAnalyticsAnalytics+ $0.251 creditfree+ $0.10denied · over limityour toolkitchecking limitchecking permissionsrecording callchecking limitchecking permissionsrecording callchecking limitchecking permissionsrecording callchecking limitchecking permissionsrecording call
  1. 1Every agent connects once.Connect Cursor, Claude, Codex, Grok bot, and MCP-compatible harnesses such as OpenClaw and Hermes through mcp.lanatools.sh. No API keys live in their configs.
  2. 2Every call is checked first.Is this agent allowed to perform the action? Does it fit the limit you set for that agent? If either check fails, the call stops here.
  3. 3It runs the action and logs the result.Approved calls read data, pay for services, or submit transactions. Paid calls settle from your wallet. Each action and its result go in the activity log, with costs recorded when applicable.

control

You decide what each agent can do.

Try it. Pick an agent and switch off what it shouldn’t do. Sample calls keep arriving in the activity log, so you can see which ones still get through.

tools

Connect once. It keeps getting more useful.

Payments, onchain data, and transactions through one connection. Give your agents the tools to act on Solana, with permissions and one limit for each agent.

  1. first at launch

    Pay for services

    Discover paid services in the catalog and let your agent pay for what it needs within the permissions and limit you set for that agent.

  2. next

    Ask for a result, skip the setup

    Ask for a paid result and let the router reach the right provider, without finding and configuring each URL yourself.

  3. planned

    Create and execute transactions

    Create Solana transactions and execute them through your embedded wallet within the permissions you grant, or sign with your own wallet and let LanaTools submit them.

  4. planned

    Read Solana

    Read onchain data, explore portfolios, and query activity through the same connection your agent uses to take action.

connect

Paste one URL.

  1. 1Paste the URL into Cursor, Claude, Codex, or any MCP client.
  2. 2Ask for Solana data or a transfer. No account needed.
  3. 3Log in when you want the LanaTools wallet, paid APIs, and limits.
{
"mcpServers": {
"lanatools": {
"url": "https://mcp.lanatools.sh/mcp"
}
}
}

Or paste this into a chat with any agent:

Read https://lanatools.sh/SKILL.md and connect to LanaTools.

updates

Follow what we’re building.

An occasional email when we ship something new.