MCP server
by jonator
Osmosis bridge for seamless DeFi on-chain swaps, balance queries, and account management on the Osmosis blockchain.
Connects to the Osmosis blockchain to perform DeFi operations like token swaps, balance queries, and account management. Requires your wallet mnemonic to interact with the protocol.
Osmosis is a community-built MCP server published by jonator that provides AI assistants with tools and capabilities via the Model Context Protocol. Osmosis bridge for seamless DeFi on-chain swaps, balance queries, and account management on the Osmosis blockchain. It is categorized under finance, developer tools.
You can install Osmosis in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Osmosis is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired Osmosis into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Osmosis is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Osmosis is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: Osmosis surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Osmosis is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Osmosis has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated Osmosis against two servers with overlapping tools; this profile had the clearer scope statement.
Osmosis is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Osmosis into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Osmosis against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 43
This repository contains a collection of packages that are used to build the Osmosis Agent Toolkit. Large Language Models (LLMs) can use these tools to interact with the Osmosis protocol.
@osmosis-agent-toolkit/coreThe core package contains the core functionality that is used by the other packages. This is where registry data, query clients, and sign and broadcast logic is defined.
@osmosis-agent-toolkit/ai-sdkAn implementation of Vercel's AI SDK for the Osmosis Agent Toolkit.
@osmosis-agent-toolkit/mcpModel Context Protocol (MCP) server implementation of the Osmosis Agent Toolkit.
Add the following to your claude_desktop_config.json or .cursor/mcp.json. See here for more details.
{
"mcpServers": {
"Osmosis": {
"command": "npx",
"args": [
"-y",
"@osmosis-agent-toolkit/mcp"
],
"env": {
"OSMOSIS_MNEMONIC": "<your mnemonic here>"
}
}
}
}
Install dependencies using yarn or bun:
bun i
Start watch mode for local development:
bun run dev
To build:
bun run build
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.