rosgraph-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_packagesA | List ROS2 packages in the workspace, optionally filtered by group (the
top-level src// directory a package lives under — this varies by
workspace, e.g. "vendor"/"description" for one repo, something else
entirely for another), a finer-grained subgroup within it, or a
case-insensitive substring of the package name. Call |
| list_groupsA | List every group and, within each, the subgroups actually present in
this workspace. By default these are derived generically from the src/
directory layout (group = first path segment, subgroup = the next one);
a workspace can opt into richer classification via an optional
|
| get_package_dependenciesA | Get a package's dependencies (from package.xml) and, conversely, which
packages depend on it. |
| rescan_workspaceA | Rebuild the package index cache for a workspace by re-scanning all
package.xml files under it. Call this after pulling new source or after
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list_groups exposes the grouping hierarchy, list_packages lists packages with filters, get_package_dependencies analyzes dependency relationships, and rescan_workspace refreshes the cache. There is no overlap or ambiguity among them.
All tool names follow a consistent verb_noun pattern in snake_case: list_groups, list_packages, get_package_dependencies, rescan_workspace. The naming is predictable and uniform.
With only 4 tools, the set is tightly scoped for a ROS2 workspace graph server. Each tool addresses a distinct need, and the count is appropriate for the server's purpose without feeling thin or bloated.
The tool surface covers the core workflows: discovering groups, listing packages, querying dependencies (forward and reverse), and refreshing the index after changes. There are no obvious dead ends or missing operations for the stated domain of package graph exploration.