Skip to main content
Glama

embodied-nav-mcp

部屋を見回し、名前を指定されたものへ移動し、見えたものを数え、完了したら停止できる言語モデル。

モデルは何をするかを決定します。センサーは物がどこにあるかを決定します。

ツール

ツール

機能

get_view

360°カメラからの4つの透視面とポーズ

ground

参照表現 → ピクセルボックス → ライダー距離(メートル) → コンバーターでスナップされたウェイポイント

drive_to

マップフレームの (x, y) を1つパブリッシュし、到着または停止するまで待機

stop

プランナーが最後のウェイポイントを追いかけないように停車

parse_numerical

計数質問をターゲット/アンカーに分割

count_in_view

この視点のみをカウント。各インスタンスはライダーで位置が特定される

commit_count

位置ごとに観察をクラスタリングし、整数をパブリッシュ

publish_object

最後の ground のライダーAABB。3Dマーカーをパブリッシュ

commit_count はモデルから数値を受け取りません。4つの枕を2回見ても、8ではなく4になります。

ジオメトリはTeam Xiao Heiの feat/xiao-hei-instruction-merge のType 3スタックです: サイズゲート、ブラインドコーン処理、コンバーターのセトルポーズ、退出時パーキング。

Related MCP server: Webots MCP

インストール

uv sync --extra dev
export ANTHROPIC_API_KEY=...
uv run pytest

Python 3.11以上。実機ロボット/シミュレーションにはROS Jazzyと自律スタックが必要です。テストはフェイクロボットを使用するため、どちらも不要です。

試す

# Dry run, no ROS
uv run embodied-mcp-agent --fake "How many blue chairs are between the table and the wall?"
uv run embodied-mcp-agent --fake "Find the potted plant on the kitchen island closest to the fridge."
uv run embodied-mcp-agent --fake "Take the path near the window to the fridge."

スタックが起動しているロボット(またはチャレンジコンテナ)上で:

uv run embodied-mcp-challenge
# evaluators still run: ros2 launch dummy_vlm dummy_vlm.launch

embodied-mcp --attach-ros はstdio MCP経由の同じツールです。チャレンジノードはこれらをインプロセスで呼び出します。ロボットコンテナにはリモートMCPコネクタ用の公開URLがないためです。

CMU VLN Challenge

ドロップインアダプター: examples/cmu_vln/。パッケージ名 dummy_vlm は変更されていません。

タイプ

ツール

ROS出力

数値

parse_numerical, count_in_view, commit_count

/numerical_response

オブジェクト参照

ground, publish_object

/selected_object_marker

指示追従

get_view, ground, drive_to, stop

/way_point_with_heading

許可されるセンサー: /camera/image、/registered_scan、/terrain_map、/terrain_map_ext、/state_estimation。到着は /way_point_reached ではなく /state_estimation です。プロセスごとに1つの質問です。

設定

変数

デフォルト

ANTHROPIC_API_KEY

—

必須

EMBODIED_MCP_MODEL

claude-opus-5

ホストおよびピクセルグラウンディング/計数モデル

EMBODIED_MCP_BUDGET_S

540

プロセス開始からの秒数

XIAO_HEI_IMAGE_TOPIC

/camera/image

カメラトピック

ライセンス

MIT。Team Xiao Hei からベンダリングしたジオメトリとROS I/Oを含みます。NOTICE を参照してください。

Available Tools

8 tools
commit_countA

Cluster every count_in_view look by lidar position and publish one integer on /numerical_response. Two views of the same four pillows become 4, not 8. You do not pass the number — geometry does.

Inputs: no named parameters. Returns: result

count_in_viewA

Count matching instances from the current vantage point only. The call is never told the running total — do not add previous looks yourself. Each instance is boxed and lifted with lidar so later looks can be de-duplicated. If sufficient is false, drive as next_view suggests (or ground the anchor) and count_in_view again. When you are done looking, call commit_count — that publishes the clustered integer.

Inputs: target (required), question (required), anchor. Returns: result

drive_toA

Publish one waypoint (map-frame x, y) and wait until the vehicle arrives or settles. Arrival is decided from /state_estimation, not from a 'waypoint reached' topic. Prefer publish_xy from ground() over coordinates you invent.

Inputs: x (required), y (required), timeout_s. Returns: result

get_viewA

Capture the robot's current 360° camera, split into four perspective faces (front, right, back, left), and return them with the current pose. Call this when you need to see the room. Do not guess what is around you.

Inputs: no named parameters. Returns: result

groundA

Ground a referring expression in the live camera + lidar. Pass the object or place to go to, in the instruction's own words (e.g. 'the lantern closest to the fan decoration'). The tool asks a pixel-grounding model for a box, lifts metres from the registered scan, size-checks the range, and snaps the waypoint to where the platform converter will actually settle. Use publish_xy as the argument to drive_to. If committed is false, this is a step to a better viewpoint — drive there and ground again. If visible is false, drive to suggested_xy and look again.

Inputs: query (required). Returns: result

parse_numericalA

Split a counting question into target, attribute, relation, and anchor. Use this first on numerical questions so you know what to ground and what to pass to count_in_view.

Inputs: question (required). Returns: result

publish_objectA

Publish a 3D cube marker on /selected_object_marker for the object you last grounded. Call ground() on the unique referred object first. The box centre and size come from the lidar cluster, not from a guess.

Inputs: label (required). Returns: result

stopA

Park at the current pose so the local planner stops chasing the last waypoint. Call this when the instruction is finished, or after you have published a numerical or object-reference answer.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool serves a distinct function: perception (get_view), grounding (ground), navigation (drive_to, stop), numerical parsing (parse_numerical), counting (count_in_view), finalizing counts (commit_count), and object publication (publish_object). There is no overlap or ambiguous boundaries between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_phrase pattern with snake_case (e.g., get_view, drive_to, commit_count). The verbs are imperative and descriptive, making the intent of each tool predictable from its name alone.

    Tool Count5/5

    With 8 tools, the server is well-scoped for embodied navigation and counting tasks. Each tool covers a necessary step in the workflow without redundancy or excessive granularity, fitting within the ideal 3-15 tool range.

    Completeness5/5

    The tool surface fully covers the lifecycle of the domain: perceiving the environment, grounding references, moving, stopping, parsing questions, counting from multiple views, committing aggregated results, and publishing object markers. There are no obvious gaps or dead ends for the intended tasks.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.
      24
      36
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables agents to identify appliances and retrieve grounded, robot-executable operation packages, reducing hallucinations from 24% to nearly 0%.
      4
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM agents to control robot simulations (grasping, pouring) in the Genesis physics simulator through persistent sessions, allowing multi-turn interaction with the same scene.
      -