Viam Mcp Server

Name: Viam Mcp Server
Author: erh

by erh

viam mcp server running on robots

0 tools GitHub

No known CVEs

No license

Actively maintained

Last commit 0d ago

Untested

Transport: stdio

0 tools

Grade F

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Untested on Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "viam-mcp-server": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/viam-mcp-server)](https://mcppedia.org/s/viam-mcp-server)

Read me

What Viam Mcp Server does

viam mcp server running on robots

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

24/100across 5 weighted dimensions

How we score →

0255075100

−76

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Viam Mcp Server safe to use?: Viam Mcp Server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install Viam Mcp Server?: Viam Mcp Server can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with Viam Mcp Server?: Viam Mcp Server is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.
Is Viam Mcp Server actively maintained?: Viam Mcp Server is actively maintained — last commit was 0 days ago.

Similar servers

Others in other

View all →

Memory MCP Server98

Persistent memory using a knowledge graph

84.1k 5

Context Mode95

Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.

7.7k 6

Idea Reality MCP Server95

Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.

606 1

Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.95

Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.

405 5

MCP Security Weekly

Get CVE alerts and security updates for Viam Mcp Server and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Module viam-mcp-server

Runs an embedded Model Context Protocol server as a Viam generic service. The MCP server lets an MCP-compatible client (an LLM agent, claude, etc.) drive a configured allow-list of components on the machine — both via a generic do_command and via per-method tools generated from each component's typed Go interface (e.g. motor1__set_power, base1__move_straight, mysensor__readings).

The server's lifecycle is tied to the service: it starts when the service is constructed and shuts down when the service is closed or reconfigured.

Tutorial

Add the module to your machine. In the Viam app, add erh:viam-mcp-server from the registry (or point at this repo).

Configure the service. Add a generic service using the erh:viam-mcp-server:mcp-server model with the components you want exposed:

{
  "components": ["motor1", "door1"],
  "address": ":8765"
}

Each name in components must be an existing component on the machine; it becomes a required dependency.

Open the port. Make sure :8765 (or whatever you set) is reachable from wherever your MCP client runs. Verify with nc -zv <machine-host> 8765.

Connect from Claude Code:

claude mcp add --transport http viam-mcp http://<machine-host>:8765

Then /mcp inside Claude Code to load the tools.

Use the tools. Two flavors are available:

Typed per-method tools, named <component>__<method> — e.g. ask Claude "set door1 to position 0" and it'll call door1__set_position.
Generic do_command for anything not covered by a typed tool.

list_components returns the names the server is exposing. See the model doc for the full per-type tool list.

Frequently Asked Questions

Is Viam Mcp Server safe to use?

Viam Mcp Server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install Viam Mcp Server?

Viam Mcp Server can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with Viam Mcp Server?

Viam Mcp Server is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.

Is Viam Mcp Server actively maintained?

Viam Mcp Server is actively maintained — last commit was 0 days ago.

Module viam-mcp-server

The server's lifecycle is tied to the service: it starts when the service is constructed and shuts down when the service is closed or reconfigured.

Models

This module provides the following model(s):

erh:viam-mcp-server:mcp-server — an MCP server exposed over streamable HTTP that controls a configured list of components.

Tutorial

Add the module to your machine. In the Viam app, add erh:viam-mcp-server from the registry (or point at this repo).
Configure the service. Add a generic service using the erh:viam-mcp-server:mcp-server model with the components you want exposed:
```
{
  "components": ["motor1", "door1"],
  "address": ":8765"
}
```
Each name in components must be an existing component on the machine; it becomes a required dependency.
Open the port. Make sure :8765 (or whatever you set) is reachable from wherever your MCP client runs. Verify with nc -zv <machine-host> 8765.
Connect from Claude Code:
```
claude mcp add --transport http viam-mcp http://<machine-host>:8765
```
Then /mcp inside Claude Code to load the tools.
Use the tools. Two flavors are available:
- Typed per-method tools, named <component>__<method> — e.g. ask Claude "set door1 to position 0" and it'll call door1__set_position.
- Generic do_command for anything not covered by a typed tool.
list_components returns the names the server is exposing. See the model doc for the full per-type tool list.