Get the FREE Ultimate OpenClaw Setup Guide →

axum-http

MCP server from apepkuss/axum-http-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio apepkuss-axum-http-mcp-server wasmedge --dir .:. ./target/wasm32-wasip1/release/axum-mcp-server.wasm

How to use

This MCP server is an Axum-based HTTP MCP server implemented in Rust and compiled to WebAssembly. After building and running with the WasmEdge runtime, you can interact with the server via the exposed JSON-RPC over HTTP. The server provides a tool named counter, which you can invoke using the tools/call interface to perform operations like increment, decrement, and get_value. Use the provided HTTP endpoint /api/counter to send JSON-RPC payloads and receive structured responses containing the counter value. The workflow typical uses the WasmEdge runtime to host the WASM binary produced by cargo build, then clients issue POST requests to manipulate and read the counter state.

How to install

Prerequisites:

  • Rust toolchain (cargo) installed
  • WasmEdge runtime installed
  • A Unix-like environment (Linux/macOS) or Windows with appropriate tooling

Installation steps:

  1. Clone the repository and build the WASM module in release mode: git clone https://github.com/apepkuss/axum-http-mcp-server.git cd axum-http-mcp-server cargo build --release

  2. Install WasmEdge runtime (example command shown in the README): curl -sSf https://raw.githubusercontent.com/WasmEdge/WasmEdge/master/utils/install_v2.sh | bash -s -- -v 0.14.1

  3. Start the server using WasmEdge with the built WASM module: wasmedge --dir .:. ./target/wasm32-wasip1/release/axum-mcp-server.wasm

  4. Verify the server is running by sending a request to the counter tool as described in the usage section.

Additional notes

Tips and notes:

  • Ensure the WasmEdge runtime version matches the build targets (.wasm32-wasip1).
  • The counter tool is exposed via the endpoint /api/counter and accepts JSON-RPC payloads with methods under tools/call and arguments such as operation: increment, decrement, or get_value.
  • If you change the working directory, adjust the --dir parameter accordingly so the WASM module and any needed assets are accessible.
  • If you encounter port issues, ensure the server is listening on the expected port (default 10086 in examples) and that firewall rules allow local access.
  • This MCP server is a Rust/WebAssembly implementation; no npm package is involved.

Related MCP Servers

Sponsor this space

Reach thousands of developers