mesh-connector
Related Servers
Alternatives to mesh-connector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables 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.45131 npmMIT
- AlicenseAqualityAmaintenanceCross-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.91,591 npm797Apache 2.0
- AlicenseAqualityDmaintenanceConnects AI coding agents to the SkillsMP marketplace, allowing users to search, read, and install over 8,000 community-made skills. It enables agents to gain new capabilities either through on-the-spot instruction or permanent installation without requiring an API key.57 npm10MIT
- AlicenseAqualityDmaintenanceEnables AI agents to discover, subscribe to, and call paid agent services from the AgentStorefront marketplace directly within MCP-aware clients like Claude or Cursor.428 npmMIT
- AlicenseBqualityBmaintenanceEnables Claude Code and OpenCode agents to delegate tasks to peer machines over a self-hosted A2A mesh, using mTLS identity and executing via local CLIs or scripts.8Apache 2.0
TDQS
Scored across 28 tools
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.
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.
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.
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.