Home / MCP / Osmosis Agent Toolkit MCP Server

Osmosis Agent Toolkit MCP Server

Provides an MCP server to run the Osmosis Agent Toolkit, enabling LLMs to query and act on the Osmosis protocol.

typescript

9stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "osmosis": {
            "command": "npx",
            "args": [
                "-y",
                "@osmosis-agent-toolkit/mcp"
            ],
            "env": {
                "OSMOSIS_MNEMONIC": "<your mnemonic here>"
            }
        }
    }
}

You set up an MCP (Model Context Protocol) server to run the Osmosis Agent Toolkit so you can leverage LLMs to interact with the Osmosis protocol. This server exposes the toolkit’s core capabilities to your MCP client, enabling context management, querying, and action execution in a structured, scalable way.

How to use

To use the Osmosis MCP server with your MCP client, connect your client to the local or remote MCP endpoint exposed by the Osmosis toolkit. The server runs as a local stdio process that you launch from your environment. You supply the necessary mnemonic to initialize and authorize operations, and then your client can request data retrieval, transaction signing, and broadcast actions through the MCP interface. Use clear, authenticated prompts to request operations such as querying balances, building and signing transactions, or broadcasting them to the Osmosis network.

How to install

# Prerequisites: ensure you have a compatible runtime (Node.js) and a package manager installed.
# Install dependencies for all packages
bun i

# Start development in watch mode
bun run dev

# Build for production or local testing
bun run build

Configuration and usage notes

The Osmosis MCP server is run as a local stdio process. You start it by invoking the package runtime with the MCP entry, and you pass any required environment variables for authentication or mnemonic access. The basic configuration example shows how to launch the server via a command line that the MCP client can spawn.

Troubleshooting and tips

If you encounter issues starting the MCP server, verify that your environment variable for the mnemonic is set correctly and that the spawn command is accessible from your shell. Check that your MCP client is configured to communicate with the correct stdio process and that any required dev dependencies are installed before starting the server.

Examples and quick start

The following MCP configuration example shows how to launch the Osmosis MCP server as a stdio process from your client configuration. Include the mnemonic as an environment variable for initialization.

Available tools

registry

Centralized registry data used to resolve available commands, capabilities, and data sources for the Osmosis toolkit.

queryClient

Client component used to query data from the Osmosis protocol and related services.

signAndBroadcast

Core function to sign prepared transactions and broadcast them to the Osmosis network.