Skip to main content
Glama
J3n5en

impart-mcp

by J3n5en
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to impart-mcp

No user-submitted related servers found.

    Related Servers

    • agentforge

      Soulcynics404
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides 300+ MCP tools for orchestrating AI agents — including swarm coordination, self-learning memory, and task management — enabling MCP clients like Claude Code and Cursor to spawn, coordinate, and learn from specialist agents across sessions.
      18,049 npm
      1
      MIT

    • all-agents-mcp

      Dokkabei97
      A
      license
      B
      quality
      F
      maintenance
      Enables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.
      14
      3 npm
      14
      MIT

    • slop-mcp

      standardbeagle
      A
      license
      B
      quality
      A
      maintenance
      An MCP orchestration layer that aggregates multiple MCP servers while exposing only 8 meta-tools, dramatically reducing context window usage, and provides SLOP scripting, event monitoring, and tool customization.
      10
      19 PyPI
      MIT

    • OpenAI Agents MCP Server

      lroolle
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.
      4
      10
      -

    • LightsOut

      filipeagg
      F
      license
      Not graded
      quality
      A
      maintenance
      Agent orchestration system that runs coding-agent sessions (Claude Code, Codex) with policy mediation and exposes tools via MCP.
      -
    Deploy Server
    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

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are functionally distinct by execution model (sync, async, batch, result retrieval), but call_agent_async and call_agents_batch overlap in parallel execution capability, requiring extensive warnings to steer usage. The descriptions clarify intent, but the ambiguity is notable enough to deduct a point.

    Naming Consistency4/5

    All tools follow a snake_case verb_noun pattern with clear prefixes (call_, get_). However, the distinction between call_agent, call_agent_async, and call_agents_batch is subtle, and pluralization is inconsistent, slightly reducing predictability.

    Tool Count5/5

    Four tools is an appropriate scope for an agent orchestration server, covering the essential sync, async, batch, and result retrieval patterns without bloat or redundancy. Each tool serves a distinct purpose in the workflow.

    Completeness4/5

    The surface covers the core lifecycle of launching and retrieving agent results, including synchronous and asynchronous execution. Missing cancellation or task listing is a minor gap, but the main workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources