Skip to main content
Glama
Meshtool

mesh-connector

by Meshtool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mesh-connector

No user-submitted related servers found.

    Related Servers

    • MeshAI MCP Server

      meshailabs-org
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Claude Code and other MCP-compatible tools to leverage MeshAI's multi-agent orchestration capabilities for code review, refactoring, debugging, documentation, architecture analysis, and feature development. Automatically selects appropriate AI agents based on task content and works with agents built on LangChain, CrewAI, AutoGen, and other frameworks.
      MIT

    • SandBase

      Rachel8917
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI clients such as Claude Code, Cursor, Codex, ChatGPT, Hermes, and OpenClaw to 2,000+ AI models and data APIs through a local MCP bridge, letting an agent discover, inspect, price, and run tools after a single browser-approved OAuth sign-in. Backed by a read-only catalog, run history, and rollback so calls can be audited and reverted without managing individual API keys.
      556,724 npm
      MIT

    • Finch MCP

      finchagentic
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to retain persistent, searchable memory and versioned vaults, spawn and recall named agents with state and audit history, run automations, monitors, and deep research, and execute on-chain and web tasks across sessions. It can be installed alongside Claude Code, Cursor, Windsurf, Zed, Hermes, and other MCP clients, with vault and memory optionally run entirely on the user's machine.
      45
      56 npm
      MIT

    • SandBase

      RichardCastillo79
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP bridge that connects AI clients such as Claude Code, Cursor, Codex, ChatGPT, and Hermes to 2,000+ models and APIs, letting agents discover, inspect, and run search, social, scraping, finance, LLM, image, video, and audio capabilities behind a single browser sign-in. It keeps spending verifiable by exposing live schemas, pricing, run status, account balance, and rollback before anything executes.
      556,724 npm
      MIT

    • memorix

      AVIDS2
      A
      license
      A
      quality
      A
      maintenance
      Cross-agent memory bridge for AI coding assistants. Persistent knowledge graph shared across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. 22 tools including team collaboration, auto-cleanup, mini-skills, session management, and workspace sync. 100% local, zero API keys required.
      9
      943 npm
      873
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 28 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes: task-analysis, task-orchestrate, and biz-analyze all produce plans/recommendations, while search, mesh_discover, and fetch all serve discovery of market capabilities. Agent-brain and agent-memory also blur memory and reasoning roles. Descriptions help, but an agent could easily select the wrong tool.

    Naming Consistency2/5

    The set mixes hyphenated names (task-analysis, safety-scrub, cam-forge) with underscore-prefixed mesh_* tools, and bare verbs like search, fetch, and personalize. While each name is readable, the overall pattern is inconsistent and gives no reliable clue about which convention to expect.

    Tool Count2/5

    28 tools is a heavy surface for a connector, and the set bundles unrelated third-party capabilities (CAM fabrication, OBS migration, receptionist app creation) alongside core mesh platform operations. It feels bloated rather than well-scoped; most of the tools could live in separate servers.

    Completeness3/5

    The core mesh lifecycle is mostly present: signup, discover, search, publish, delegate, balance, profile, follow, and subscribe. However, publishing is one-directional—there is no update or unpublish/edit capability for listed tools, and there is no generic explicit "call capability" primitive beyond relying on tools being exposed directly.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources