Skip to main content
Glama
iowap-org

iowap-mcp

by iowap-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iowap-client-mcp

MCP toolkit for IOWAP: run a curated IOWAP toolset from any MCP-speaking agent — without teaching every agent the node CLI's pitfalls.

The problem

IOWAP is a distributed capability mesh: the relay routes tasks, nodes execute them. Today, an AI agent that wants to use IOWAP shells out to node-cli --json. That works, but every agent has to relearn the same pitfalls itself: response envelopes that must be unwrapped, node IDs vs. names, the global flag position, which commands are safe and which mutate the node. Knowledge ends up in one agent's skill file instead of in code.

Related MCP server: Codex Harness MCP

The answer

iowap-mcp is an MCP stdio server that wraps node-cli behind a small, curated toolset:

Tool

Purpose

relay_status

Relay health, queue depth, task counters

node_list

Fleet overview (IDs, status, capabilities, load)

capabilities_list

What the relay can do — including input schemas and the node IDs that own each capability

task_submit

Submit a task against a capability (optional short wait)

task_result

Poll a task result

artifact_download

Fetch a task artifact to a local path

docs

Read the live relay documentation

The node CLI remains the source of truth for authentication and execution — the server adds zero credential handling of its own. Destructive commands (register, update, daemon control, capability publishing) are deliberately not exposed.

Future: a Streamable HTTP variant for remote agents, running under a dedicated service node identity.

Install

pip install "iowap-client-mcp[mcp]"

Requires a node installation of IOWAP on the same host (see iowap-node) — the server shells out to the installed node-cli.

Wire it into an MCP client

Example for Hermes Agent (~/.hermes/config.yaml):

mcp_servers:
  iowap:
    command: "iowap-mcp"

Or: hermes mcp add iowap --command iowap-mcp

Development

python -m venv .venv && .venv/bin/pip install -e ".[mcp,dev]"
.venv/bin/pytest

License

MIT — see LICENSE.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Codex Harness MCP

    2091k
    F
    license
    Not graded
    quality
    A
    maintenance
    Enables MCP-compatible AI clients to invoke CLI-driven agent tools over Streamable HTTP, including shell execution, file operations, patching, image viewing, web search, and nested agent tasks, with permission modes and real-time progress streaming.
    -

  • ChatGPT Gateway MCP Nyan

    wada-qualia
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
    MIT

  • Terminal Session Manager

    danieldoalto
    F
    license
    B
    quality
    B
    maintenance
    Enables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.
    15
    -