MCP.so
Sign In

Auto MCP ✨🤖

@snick-m

About Auto MCP ✨🤖

This package provides necessary tooling to launch an MCP server for the ROS network. It provides support for introspection and manual config.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "auto_mcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:5000/sse"
      ]
    }
  }
}

Tools

No tools detected

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Auto MCP?

Auto MCP is a drop-in MCP (Model Context Protocol) server for any ROS‑based system. It uses introspection to detect all active ROS topics and their interfaces at startup, then creates an SSE‑over‑HTTP transport MCP server on port 5000, enabling an LLM to interact with a robot.

How to use Auto MCP?

Clone the repository into a colcon workspace’s src directory, build with colcon build --packages-select auto_mcp, then run ros2 run auto_mcp server. This launches the node, performs introspection, and starts the MCP server bound to 0.0.0.0:5000; the SSE endpoint is at http://localhost:5000/sse. For Claude Desktop, use the npx mcp-remote proxy with the URL set to http://localhost:5000/sse in the MCP configuration. If the mcp Python package is not available via rosdep, install it manually with pip install mcp.

Key features of Auto MCP

  • Drop‑in MCP server for any ROS system
  • Automatic topic and interface detection via introspection
  • SSE over HTTP transport on port 5000
  • Simple integration with any MCP‑compatible LLM client
  • Works with Claude Desktop using a local proxy workaround

Use cases of Auto MCP

  • Give a ROS‑based robot a reasoning and planning layer via an LLM
  • Connect a robotic system to a conversational AI assistant
  • Enable natural‑language control of ROS topics and services

FAQ from Auto MCP

What is MCP?

The Model Context Protocol (MCP) is a protocol developed by Anthropic (and now supported by OpenAI) that allows LLMs to interact with various tools. Auto MCP uses this protocol to expose ROS topics as MCP tools.

Why should I use Auto MCP instead of writing a custom ROS–LLM bridge?

Auto MCP automates the bridge: it introspects the ROS system at runtime, discovers topics and their interfaces, and creates a standard MCP server – no manual tool definition or topic mapping is needed.

What are the dependencies and runtime requirements?

You need a ROS 2 workspace (e.g., Foxy or later) with colcon. The mcp Python package (MCP SDK) must be installed via pip install mcp until the rosdep pull request is merged.

How does the transport work?

The server uses SSE (Server‑Sent Events) over HTTP on 0.0.0.0:5000. The SSE endpoint is accessible at http://localhost:5000/sse from the local machine.

Can I use Auto MCP with Claude Desktop?

Yes, but Claude Desktop does not natively support SSE MCP servers. Use a local proxy (e.g., npx mcp-remote) and configure the MCP command to point to http://localhost:5000/sse as shown in the README.

Frequently asked questions

What is MCP?

The Model Context Protocol (MCP) is a protocol developed by Anthropic (and now supported by OpenAI) that allows LLMs to interact with various tools. Auto MCP uses this protocol to expose ROS topics as MCP tools.

Why should I use Auto MCP instead of writing a custom ROS–LLM bridge?

Auto MCP automates the bridge: it introspects the ROS system at runtime, discovers topics and their interfaces, and creates a standard MCP server – no manual tool definition or topic mapping is needed.

What are the dependencies and runtime requirements?

You need a ROS 2 workspace (e.g., Foxy or later) with colcon. The `mcp` Python package (MCP SDK) must be installed via `pip install mcp` until the rosdep pull request is merged.

How does the transport work?

The server uses SSE (Server‑Sent Events) over HTTP on `0.0.0.0:5000`. The SSE endpoint is accessible at `http://localhost:5000/sse` from the local machine.

Can I use Auto MCP with Claude Desktop?

Yes, but Claude Desktop does not natively support SSE MCP servers. Use a local proxy (e.g., `npx mcp-remote`) and configure the MCP command to point to `http://localhost:5000/sse` as shown in the README.

Comments

Basic information

Category

Other

License

BSD-3-Clause license

Transports

stdio

Author

snick-m

More Other MCP servers