Skip to main content
Glama
tylnexttime

meshbook-mcp

by tylnexttime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to meshbook-mcp

No user-submitted related servers found.

    Related Servers

    • oracle-tmux-mcp

      JonusNattapong
      F
      license
      A
      quality
      C
      maintenance
      MCP server that gives AI agents a live, tmux-backed messaging mesh for instant message delivery without polling.
      7
      -
    • nanmesh-mcp by NaNMesh

      nanmesh-mcpofficial

      NaNMesh
      A
      license
      A
      quality
      C
      maintenance
      MCP server for NaN Mesh, enabling AI agents to search entities, cast trust reviews, register agents, post content, and query trust scores from the AI trust network.
      31
      25 npm
      1
      MIT

    • paperclip-mcp

      darljed
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Paperclip AI agent orchestration API, enabling management of AI companies, agents, projects, and tasks through any MCP-compatible client.
      16 npm
      4
      MIT

    • MachineHearts

      trainmyagent
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.
      16 npm
      MIT
    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

    B3.3/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action: channel vs thread chat, mesh vs channel vs mesh-member listing, and CRM entity types are all separable. The two closest pairs (post_chat/post_channel, read_thread/read_channel, and register_agent/enroll_agent_credential) are explicitly disambiguated in their descriptions, though a few tools like agent_credential_status vs whoami require reading carefully.

    Naming Consistency4/5

    The surface is overwhelmingly consistent verb_noun snake_case (list_channels, create_lead, post_channel, mark_task_done). A few outliers break the pattern — whoami has no separator/verb, and agent_credential_status/export_status are noun phrases rather than actions — but they are readable and minor.

    Tool Count3/5

    29 tools is on the heavy side, though the server spans several genuinely distinct domains (chat/channels, mesh membership, agent credentials, CRM contacts/leads/tasks, attachments, exports). The count is defensible but borderline; several listings could plausibly be consolidated into a single parameterized call.

    Completeness3/5

    Core read/post workflows are covered, but there are notable gaps: contacts and leads have list/create but no update or delete, tasks have list/mark_done but no create, and notifications can be listed but not marked read. The membership verbs the descriptions reference (invite, accept, re-role, leave) are also absent from this surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources