1. Conduid
  2. Developer Tools
  3. Auto MCP
MCP server · Developer Tools

Auto MCP

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

Unclaimed BSD-3-Clause last commit a year ago devtools
54Fair

Scored 13 days ago · breakdown

About Auto MCP

Auto MCP is an MCP server published by snick-m in the Developer Tools category: this package provides necessary tooling to launch an MCP server for the ROS network. It provides support for introspection and manual config.

The repository has 12 stars and 4 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/snick-m/auto_mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Auto MCP

Powered by Claude · Grounded in docs

I know everything about Auto MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • ✓Tests presentA test suite exists in the repository.
  • !Dependencies pinnedNo lockfile. Installs can pull different code over time.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Auto MCP ✨🤖

This package works as a drop-in MCP Server for any ROS based system. Using introspection tools, the automcp_listener node picks up the list of topics and their interfaces that are live on the system. It then proceeds to create an SSE over HTTP Transport MCP server at port 5000.

Due to this introspection at start behavior - it should be the last node to run.

What is it ❔

Essentially, this package will allow you to give your ROS based robot a big LLM brain with very little work.

It works by creating an MCP server that you can connect with your LLM/Client of choice providing your robot a brain, and the LLM a body.

Model Context Protocol or MCP for short is a new protocol for LLMs to interact with various tools. Anthropic, the company behind Claude developed this protocol which has recently seen support from OpenAI as well. Learn more about it from the official website

Now, this Auto MCP ROS2 package aims to make the process of creating an MCP for your robot effortless. Through introspection, this package can detect all the topics running on a ROS system and provide necessary tools. All you have to do is run its node after everything else, and add the configuration to your preferred client.

Why is it ❕

As LLMs get more and more powerful, I figured many more robotics developers will want to build connections between their robots and LLMs. As I had been working on such a concept to run on the Mars rover prototype at TMR, I saw MCP become popular and realized this is perfect for this use case.

But as a firm believer in quality of life improvements, I wanted to make this super easy to use and thus - Auto MCP.

Setup 🔧

The dependencies in the package.xml contain rosdep dependencies. However, the MCP SDK for Python is not yet in the rosdep repo. I have a pull request open for that.

Until that gets resolved, you can use pip install mcp to install the dependency as noted in the python-sdk repo for the Model Context Protocol.

Installation 📥

In order to install this package create a colcon workspace following the instructions on the official ros website.

After that, clone this repo to the src directory in your workspace.

cd src
git clone https://github.com/snick-m/auto_mcp.git

Then, go back to the root workspace directory and run the build command.

cd ../

# If you want to only build this package
colcon build --packages-select auto_mcp

# If you want to build all packages in the workspace
colcon build

After this you should be able to proceed to using it.

Usage 🏃🏼‍➡️

Once built and installed using your ros2 workspace, you can launch the node by simply running

ros2 run auto_mcp server

This will launch the node that will first do introspection and start the MCP server on 0.0.0.0:5000, therefore, on the local system you can access the SSE endpoint at http://localhost:5000/sse

Adding to Claude Desktop 🔗

Currently I've only tested with Claude Desktop, I'll try to add more necessary instructions over time.

At the time of writing this, Claude Desktop doesn't support adding MCPs with SSE over HTTP transport. However, a really simple workaround from Cloudflare makes it usable.

For the Claude Desktop MCP configuration just use the following while modifying the url based on your setup.

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

Contribution 🫂

Contribution guidelines are soon to come, for now check the issues to see the planned upgrades to this package. If any of them interest you, feel free to ping me on the issue to work on it.

README fetched from the repository 6 days ago. The original is authoritative.

Questions

About Auto MCP

How do I install Auto MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Auto MCP safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Auto MCP still maintained?

The last commit was a year ago and 3 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.