freshcrate
Skin:/
Home > MCP Servers > mcp-mesh

mcp-mesh

Enterprise-grade distributed AI agent framework | Develop → Deploy → Observe | K8s-native | Dynamic DI | Auto-failover | Multi-LLM | Python + Java + TypeScript

Why this rank:Strong adoptionRecent releaseHealthy release cadence

Description

Enterprise-grade distributed AI agent framework | Develop → Deploy → Observe | K8s-native | Dynamic DI | Auto-failover | Multi-LLM | Python + Java + TypeScript

README

MCP Mesh

Release Python Version Java Version TypeScript Go Version Rust PyPI npm Maven Central Docker Helm Discord YouTube License

The future of AI is not one large model, but many specialized agents working together.

📚 Documentation · 🚀 Quick Start · 🎬 YouTube · 💬 Discord


⚡ Getting Started

# Install the CLI
npm install -g @mcpmesh/cli

# Explore commands
meshctl --help

# Built-in documentation
meshctl man

Python Quick Start → | Java Quick Start → | TypeScript Quick Start →


🎯 Why MCP Mesh?

You write the agent logic. The mesh discovers, connects, heals, and traces — across languages, machines, and clouds.


For Developers 👩‍💻

Stop fighting infrastructure. Start building intelligence.

  • Zero Boilerplate: Simple decorators/functions replace hundreds of lines of networking code
  • Python, Java & TypeScript: Write MCP servers as simple functions in your preferred language - no manual client/server setup
  • Web Framework Integration: Inject MCP agents directly into FastAPI (Python), Spring Boot (Java), or Express (TypeScript) APIs seamlessly
  • LLM as Dependencies: Inject LLMs just like MCP agents - dynamic prompts with Jinja2 (Python), FreeMarker (Java), or Handlebars (TypeScript)
  • Seamless Development Flow: Code locally, test with Docker Compose, deploy to Kubernetes - same code, zero changes
  • kubectl-like Management: meshctl - a familiar command-line tool to run, monitor, and manage your entire agent network
from fastmcp import FastMCP
import mesh

app = FastMCP("TripPlanner")

@app.tool()
@mesh.tool(
    capability="plan_trip",
    dependencies=[
        {"capability": "weather", "tags": ["+claude"]},
        {"capability": "hotels",  "tags": ["+gpt"]},
        {"capability": "flights"},
        {"capability": "budget",  "tags": ["+claude"]},
    ],
)
async def plan_trip(
    destination: str,
    dates: str,
    weather: mesh.McpMeshTool = None,
    hotels:  mesh.McpMeshTool = None,
    flights: mesh.McpMeshTool = None,
    budget:  mesh.McpMeshTool = None,
) -> TripPlan:
    forecast = await weather(destination=destination, dates=dates)
    options  = await hotels(destination=destination, dates=dates)
    routes   = await flights(destination=destination, dates=dates)
    cost     = await budget(routes=routes, options=options)
    return TripPlan(forecast, options, routes, cost)

@mesh.agent(name="trip-planner", auto_run=True)
class TripAgent: pass

Four distributed calls, composed like a local function. Each dependency could live in this process, another machine, another language. Mesh handles discovery, transport, retry, and failover — your function stays a function. Each dep is just another @mesh.tool, defined the same way — in this agent or another.

Any dependency can be a plain tool or an LLM agent — your code can't tell the difference. weather could be a REST API or a Claude-powered reasoning agent returning a typed pydantic forecast. +claude means prefer the reasoning agent; if it dies, mesh auto-rewires to the API. When Claude recovers, mesh rewires back. No deploy, no config, no code change.

Routing stays in Python, not YAML. See how below.

See how the Claude-powered weather agent is built (10 lines)
from fastmcp import FastMCP
import mesh

app = FastMCP("ClaudeWeather")

@app.tool()
@mesh.llm(
    system_prompt="file://prompts/weather.j2",
    provider={"capability": "llm", "tags": ["+claude"]},
)
@mesh.tool(capability="weather", tags=["+claude"])
def weather(destination: str, dates: str,
            llm: mesh.MeshLlmAgent = None) -> Forecast:
    return llm(f"Forecast for {destination} on {dates}")

@mesh.agent(name="claude-weather", auto_run=True)
class Agent: pass
Route by Python if/else, not config
# Two providers of the same capability, wired at runtime
weather = reasoning_weather if user.wants_explanation else api_weather
forecast = await weather(destination, dates)

See the full TripPlanner tutorial →


For Solution Architects 🏗️

Design intelligent systems, not complex integrations.

  • Agent-Centric Architecture: Design specialized agents with clear capabilities and dependencies, not monolithic systems
  • Dynamic Intelligence: Agents get smarter automatically when new capabilities come online - no reconfiguration needed
  • Domain-Driven Design: Solve business problems with ecosystems of focused agents that can be designed and developed independently
  • Composable Solutions: Mix and match agents to create new business capabilities without custom integration code

Example: Deploy a financial analysis agent that automatically discovers and uses risk assessment, market data, and compliance agents as they become available.


For DevOps & Platform Teams ⚙️

AI infrastructure out of the box.

  • Kubernetes-Native: Deploy with Helm charts - horizontal scaling, health checks, and service discovery included
  • Enterprise Observability: Built-in Grafana dashboards, distributed tracing, and centralized logging for complete system visibility
  • Zero-Touch Operations: Agents self-register, auto-discover dependencies, and gracefully handle failures without network restarts
  • Standards-Based: Leverage existing Kubernetes patterns - RBAC, network policies, service mesh integration, and security policies

Scale from 2 agents to 200+ with the same operational complexity.


For Support & Operations 🛠️

Complete visibility and zero-downtime operations.

  • Real-Time Network Monitoring: See every agent, dependency, and health status in live dashboards
  • Intelligent Scaling: Agents scale independently based on demand - no cascading performance issues
  • Graceful Failure Handling: Agents degrade gracefully when dependencies are unavailable, automatically reconnect when services return
  • One-Click Diagnostics: meshctl status provides instant network health assessment with actionable insights

For Engineering Leadership 📈

Transform AI experiments into production revenue.

  • Accelerated Time-to-Market: Move from PoC to production deployment in weeks, not months
  • Cross-Team Collaboration: Enable different departments to build agents that automatically enhance each other's capabilities
  • Risk Mitigation: Proven patterns help ensure reliable AI deployments that scale with your business
  • Future-Proof Architecture: Add new AI capabilities without disrupting existing systems

Turn your AI strategy from "promising experiments" to "competitive advantage in production."


Architecture Overview

MCP Mesh Architecture

MCP Mesh handles the complexity so you don't have to:

  • Zero Boilerplate: Just add @mesh.tool() - networking handled automatically
  • Dynamic Everything: Add/remove/upgrade services without touching other code
  • Complex Apps Made Simple: Financial services example shows 6+ interconnected agents
  • Production Ready: Built-in resilience, distributed observability, and scaling

The Magic: Write simple functions in Python, Java, or TypeScript, get distributed systems.


Key Features

Distributed Dynamic Dependency Injection (DDDI)

  • Distributed — dependencies span machines, clouds, and runtimes (Python/TypeScript/Java)
  • Dynamic — services discovered and injected at runtime, not compile time
  • Hot-swappable — dependencies update without restarts via heartbeat-driven re-resolution
  • Pull-based discovery with runtime function injection — no networking code required
  • Smart resolution with version constraints, capability matching, and tag scoring
  • LLM as a dependency — treat LLMs as first-class injectable services with automatic tool discovery

Resilience

  • Registry as facilitator - agents communicate directly with fault tolerance
  • Self-healing architecture - automatic reconnection when services return
  • Graceful degradation - agents work standalone when dependencies unavailable
  • Background orchestration - mesh coordinates without blocking business logic

Observability

  • Complete observability stack - Grafana dashboards, Tempo tracing, Redis session management
  • Distributed tracing with OTLP export and cross-agent context propagation
  • Real-time trace streaming for multi-agent workflow monitoring
  • Advanced session management with Redis-backed stickiness across pod replicas

Developer Experience & Operations

  • Near-complete MCP protocol support for distributed networks
  • Enhanced proxy system with kwargs-driven auto-configuration for timeouts, retries, streaming
  • meshctl CLI for lifecycle management and network insights
  • Kubernetes native with scaling, health checks, and comprehensive observability

MCP Mesh vs Other AI Agent Frameworks

Feature Other Frameworks MCP Mesh
Zero-config Dependency Injection
Dynamic Agent Discovery & Hot Join/Leave
Cross-language Support ✅ Python + Java + TypeScript
Same Code: Local → Docker → K8s ❌ Rewrite needed
Developer CLI (scaffold, trace, status) meshctl
Kubernetes-native (Helm) ❌ DIY
Distributed Tracing (OpenTelemetry) ❌ DIY ✅ Grafana/Tempo
Auto-failover & Graceful Degradation
LLM as Dependency (Discovery + Failover)
Zero-config Testing (Topology Mocking)
Standard Protocol ❌ Custom ✅ MCP
Framework Lock-in High (classes) Low (decorators)
Lines of Code per Agent ~50+ ~10

See full comparison →


Contributing

We welcome contributions from the community! MCP Mesh is designed to be a collaborative effort to advance the state of distributed MCP applications.

How to Contribute

  1. Check the Issues - Find good first issues or suggest new features
  2. Join Discussions - Share ideas and get help from the community
  3. Submit Pull Requests - Contribute code, documentation, or examples
  4. Follow our development guidelines - See project structure and coding standards below

Community & Support


License

This project is open source. License details will be provided in the LICENSE file.


Acknowledgments

  • Anthropic for creating the MCP protocol that inspired this project
  • FastMCP for providing excellent MCP server foundations
  • Kubernetes community for building the infrastructure platform that makes this possible
  • All the contributors who help make MCP Mesh better

📚 Learn More

  1. 📚 Full Documentation - Complete guides and reference
  2. ⚡ Quick Tutorial - Build your first distributed MCP agent
  3. 💬 Join Discord - Connect with the community
  4. 🔧 Contribute - Help build the future of AI orchestration

Star the repo if MCP Mesh helps you build better AI systems! ⭐

Release History

VersionChangesUrgencyDate
v2.4.0## LLM contract maturity across the polyglot trilogy — `response_model`, server-enforced structured output, and Java `@mesh.llm` parity. v2.3 completed the MeshJob lifecycle surface; v2.4 turns to the `@mesh.llm` contract. The schema the model is asked to emit is now cleanly separable from a tool's own return type, structured output is enforced natively by the provider instead of a brittle re-prompt fallback, and Java's `@mesh.llm` reaches feature parity with Python and TypeScript. Spring useHigh6/4/2026
v2.3.0## v2.3.0 (2026-05-23) Lifecycle facades across the polyglot trilogy + unified dependency-injection contract. v2.2 introduced the MeshJob substrate; v2.3 completes the lifecycle surface so callers that hold only a `job_id` can drive cancel / status / wait through DDDI-clean module-level facades — the same shape `post_event` and `subscribe_events` already had. The DI rules for `McpMeshTool` and `MeshJob` parameters are unified under a single positional contract, eliminating a silent wrong-proxyHigh5/23/2026
v2.2.4## v2.2.4 (2026-05-21) Cross-loop affinity fix for v2.2 adopters using FastAPI lifespan patterns. Apps that create loop-bound resources (`asyncpg.Pool`, `redis.asyncio.Redis`, `aiohttp.ClientSession`) in `lifespan` startup and use them from tool bodies hit "Future attached to a different loop" errors in v2.2.0 — the documented `MCP_MESH_TOOL_WORKERS=1` "escape hatch" did not actually solve it. v2.2.4 fixes the topology so standard FastAPI patterns work as expected. ### 🪢 Loop topology fix (#1High5/21/2026
v2.0.0## The 2.x major release. Two new flagship surfaces — **MeshJob** (a registry-backed substrate for long-running tasks across the mesh) and **A2A v1.0** (cross-runtime Agent-to-Agent protocol bridge, both producer and consumer sides) — plus a **schema registry** that makes capability matching type-safe across Python, TypeScript, and Java with cross-runtime hash equality. The LLM provider stack moves from direct-mode SDK calls to mesh-delegated providers backed by native vendor SDKs (Anthropic, High5/14/2026
v1.4.1Reliability + provider expansion. The marquee item is a clean-cutover redesign of meshctl's process lifecycle that eliminates a class of bugs around orphaned registry/UI servers, same-name agent re-starts, and watch-mode races. Vertex AI joins the LLM provider lineup across all three runtimes with IAM-based auth instead of API keys. Python and TypeScript agents no longer have their health endpoints blocked by long-running tool calls (k8s pod-restart fix). Claude structured output goes HINT-firstHigh4/28/2026
v1.3.4### Hardening + Spring AI M4. - Closes an audit-derived security pass (registry agent_id validation, header-propagation allowlist tightened from prefix-by-default to exact match, TLS auto fail-fast, proxy error sanitization), error-visibility improvements across Python/Java SDKs, meshctl signal handler leak fix, and stale doc/version cleanups. Spring AI upgraded to 2.0.0-M4 — brings the Java integration suite to parity, 5 previously-disabled Java tests re-enabled.High4/18/2026
v1.3.3Release v1.3.3High4/16/2026
v1.3.2### Patch release. - Agent `name` and `agent_id` are now distinct fields across Python, TypeScript, and Java SDKs — previously all three collapsed `name == agent_id`, making replicas behind a K8s Service indistinguishable. The topology dashboard now groups replicas of the same base name into a single node with a ×N badge and an accordion drawer for per-replica details. meshctl `list` / `call` / `status` display and filter by full agent ID so replicas are individually addressable; registry `/prHigh4/15/2026
v1.3.1### Patch release. - Tutorial download artifacts (zips, tutorial-complete.html/txt) now generate and deploy in CI (#775). - Version bump script refactored to a handler-based design — catches 363 files per bump vs 184 previously, eliminating the manual cleanup toil from #753. High4/14/2026
v1.3.0### Reliability and production-readiness release. meshctl stop works reliably across all scenarios, timeouts propagate through multi-hop agent chains, and the TripPlanner tutorial ships end-to-end from first agent to production deployment. ### 🔗 X-Mesh-Timeout Propagation - **Header propagation across all SDKs** (#769): Python/TypeScript/Java SDKs set and propagate `X-Mesh-Timeout` header on outgoing mesh calls. Multi-hop LLM chains (gateway → planner → specialist → provider) now respect High4/14/2026
v1.2.0Observability and dashboard reliability release. Distributed tracing now works end-to-end across all runtimes, the dashboard is faster and lighter, and SQLite stability is improved. ### Observability - **Fix parent_span linkage** (#745): Python `ExecutionTracer` was publishing all spans as root spans, breaking cross-agent edge detection. Per-Edge Traffic and Total Calls now work correctly on the dashboard - **Total Calls metric** (#745): Counts every finalized trace once (single-agent andHigh4/9/2026
v1.1.0The dashboard release. Real-time monitoring, parallel tool execution, per-service TLS, and production-grade Kubernetes deployment with Helm charts. ### 🖥️ Web Dashboard - **Dashboard UI** (#665, #668, #669, #673, #677, #695): Real-time agent monitoring with 5 pages — Dashboard overview (stats, traffic, events), Agents (table with capabilities), Topology (dependency graph), Traffic (per-edge metrics, token usage, latency), and Live (trace streaming) - **Docker image** (`mcpmesh/ui`) (#722High4/5/2026
v1.1.0-beta.6Release v1.1.0-beta.6Medium4/5/2026
v1.1.0-beta.5Release v1.1.0-beta.5Medium4/5/2026
v1.1.0-beta.4Release v1.1.0-beta.4Medium4/4/2026
v1.1.0-beta.3Release v1.1.0-beta.3Medium4/2/2026
v1.1.0-beta.2Release v1.1.0-beta.2Medium4/2/2026
v1.1.0-beta.1Release v1.1.0-beta.1Medium4/1/2026
v1.0.1### ✨ New Features - **download_media API** (#660): Added `mesh.download_media(uri)` / `downloadMedia(uri)` / `MeshMedia.downloadMedia(uri, store)` across all three SDKs for reading media back from MediaStore ### 🐛 Bug Fixes - **Registry proxy timeout** (#657): `meshctl call --timeout` now propagates to the registry proxy via `X-Mesh-Timeout` header (was hardcoded 60s, capped at 600s) - **Helm scaffold env/secrets override** (#660): Commented out `env: []` and `secrets: []` in scaffolMedium3/29/2026
v1.0.0The first stable release of MCP Mesh. This milestone brings production-grade security with mutual TLS everywhere, first-class multimodal/media support across all three SDKs, and provider-side tool execution for single-round-trip agentic workflows. ### 🔒 Security & Trust - **Registration Trust — Phase 1** (#599): Registry validates agent identity via X.509 certificates before allowing registration. Entity-level trust model with pluggable trust backends (LocalCA, FileStore, K8s Secrets, SPIMedium3/25/2026
v1.0.0-beta.3Release v1.0.0-beta.3Medium3/24/2026
v1.0.0-beta.2Release v1.0.0-beta.2Medium3/23/2026
v1.0.0-beta.1Release v1.0.0-beta.1Low3/22/2026
v0.9.12Provider-side tool execution, Gemini supportLow3/15/2026
v0.9.11multi-function LLM provider_proxy loss — additive tool updatesLow3/10/2026
v0.9.10### 🐛 Bug Fixes - **Python SDK — LLM agent injector KeyError crash for filtered agents **Low3/10/2026
v0.9.9### 🐛 Bug Fixes - **Java SDK — Flat trace spans in Grafana** (#595): Java agent traces appeared flat — all downstream agent spans at the same level under the handler span — while Python and TypeScript showed proper nested hierarchy. Added `proxy_call_wrapper` intermediate spans around outgoing tool/proxy calls in `McpMeshToolProxy.call()` and `ToolInvoker.invokeLocal()`, matching the span nesting behavior of Python and TypeScript SDKs. Also added `TraceContext.wrapSupplier()` for async traceLow3/5/2026
v0.9.8### 🐛 Bug Fixes - **Java SDK — Orphan spans in trace graph** (#589): `TraceInfo.forPropagation()` generated a phantom spanId when no parent span was provided (e.g., `meshctl call --trace`), creating a span reference that was never published — downstream spans appeared as orphans with no root. Removed phantom generation so the first tool span is correctly a root span - **Java SDK — Header propagation returning empty `{}`** (#589): `MeshMcpServerConfiguration` used default `immediateExecutionLow2/22/2026
v0.9.7### ✨ New Features - **Language-agnostic Helm chart** (#580): `mcp-mesh-agent` chart now supports Python, TypeScript, and Java agents natively — added `agent.runtime` field and `isPython` helper for conditional Python env var injection; removed dead `agent.script` and `agent.python` fields; rewrote README with multi-language examples - **Arbitrary namespace support** (#579): Helm charts deploy into any namespace — replaced hardcoded FQDN hostnames with short names, added `networkPolicy.allowLow2/22/2026
v0.9.6New Features - Per-call custom headers (#575): Inject headers like x-audit-id on individual tool invocations across all three SDKs — tool(headers={"x-audit-id": "abc"}) (Python), tool({}, { headers }) (TypeScript), tool.call(args, headers) (Java). Per-call headers merge with session-propagated headers (per-call wins). Improvements - Header allowlist prefix matching (#575): MCP_MESH_PROPAGATE_HEADERS now uses case-insensitive prefix matching — x-audit matches x-audit-id, x-auditLow2/19/2026
v0.9.5### ✨ New Features - **Java SDK — `/health` endpoint** (#561): Added `GET` and `HEAD` `/health` endpoint to Java SDK for parity with Python and TypeScript runtimes ### 🔧 Improvements - **Header propagation decoupled from distributed tracing** (#564): `MCP_MESH_PROPAGATE_HEADERS` now works across all SDKs (Python, Java, TypeScript) even when tracing is disabled — previously gated behind `MCP_MESH_DISTRIBUTED_TRACING_ENABLED`, silently dropping custom headers (auth tokens, tenant IDs) -Low2/18/2026
v0.9.4### 🐛 Bug Fixes - **Java SDK — `List<Record>` @Param deserialization** (#548) - `@MeshTool` methods accepting `List<Record>` parameters (e.g., `List<TeamMember>`) received `List<LinkedHashMap>` at runtime due to Java type erasure — `MeshToolWrapper.ParamInfo` stored erased `Class<?>` instead of the full generic `Type` from `Method.getGenericParameterTypes()`; switched to `Type` and used Jackson `TypeFactory.constructType()` for proper parameterized type deserializationLow2/11/2026
v0.9.3### 🐛 Bug Fixes - **Java SDK — JavaTimeModule and isError guard in McpHttpClient** (#544) - `MeshMcpServerConfiguration` lacked `JavaTimeModule` — `@MeshTool` methods returning `java.time` types (`LocalDate`, `LocalTime`, `LocalDateTime`) threw `InvalidDefinitionException`; registered `JavaTimeModule` with `WRITE_DATES_AS_TIMESTAMPS=false` so java.time types serialize as ISO-8601 strings - `McpHttpClient.deserializeResult()` didn't check the MCP `isError` flag before attempting typed dLow2/10/2026
v0.9.2### 🐛 Bug Fixes - **meshctl start -w — Go fsnotify watch mode** (#533) - Replaced buggy bash-based watch mode with Go-native `AgentWatcher` using fsnotify, eliminating infinite restart cycles for Java agents and removing `watchfiles` pip dependency for Python - Event-driven file watching with debounce, process group termination, and automatic subdirectory watching — compiled into meshctl with zero runtime dependencies - TypeScript unchanged (`tsx --watch` works natively) - **JavaLow2/10/2026
v0.9.1### 🐛 Bug Fixes - **Release pipeline — PyPI indexing wait** (#526) - Docker builds could fail due to a race condition where `mcp-mesh-core` or `mcp-mesh` packages weren't indexed on PyPI yet when `pip install` ran - Added PyPI indexing wait steps to `publish-rust-core` and `publish-python` jobs, completing registry wait coverage for all 5 published packages (PyPI, npm, Maven Central) - **meshctl scaffold — missing Java FreeMarker template** (#528) - `meshctl scaffold --lang java Low2/8/2026
v0.9.0### ✨ New Features - **Java SDK — Full Runtime Support** (#491) - New `mcp-mesh-spring-boot-starter` built on Spring Boot 4.0.2 + Spring AI 2.0.0-M2 - Java agents participate as tool agents, LLM consumers, and LLM providers - Full cross-runtime interoperability (Java ↔ Python ↔ TypeScript) - Spring Boot auto-configuration for mesh registration, heartbeat, and discovery - MCP protocol support (tool listing, invocation, prompt handling) - Mesh delegation with `@MeshLlmProviderLow2/8/2026
v0.9.0-beta.11Release v0.9.0-beta.11Low2/6/2026
v0.9.0-beta.10Release v0.9.0-beta.10Low2/4/2026
v0.9.0-beta.9Release v0.9.0-beta.9Low2/4/2026
v0.9.0-beta.8Release v0.9.0-beta.8Low2/4/2026
v0.9.0-beta.7Release v0.9.0-beta.7Low2/4/2026
v0.9.0-beta.6Release v0.9.0-beta.6Low2/4/2026
v0.9.0-beta.5Release v0.9.0-beta.5Low2/4/2026
v0.9.0-beta.4Release v0.9.0-beta.4Low2/4/2026
v0.9.0-beta.3Release v0.9.0-beta.3Low2/4/2026
v0.9.0-beta.2Release v0.9.0-beta.2Low2/4/2026
v0.9.0-beta.1v0.9.0-beta.1Low2/4/2026
v0.8.1### 🔧 Improvements - **TypeScript SDK - MESH*LLM*\* environment variables** (#484) - `MESH_LLM_PROVIDER`: Override LLM provider (direct mode only) - `MESH_LLM_MODEL`: Override model at runtime - `MESH_LLM_MAX_ITERATIONS`: Override max iterations - `MESH_LLM_FILTER_MODE`: Override tool filter mode - **Python 3.13/3.14 support** (#485) - Updated pyproject.toml classifiers - Release workflow now builds wheels for Python 3.14 - Added scaffold test matrix (tc04-tc07) for lLow1/29/2026
v0.8.0### ✨ New Features - **Full TypeScript SDK** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - Express integration via `mesh.route()` for dependency injection (#396) - LLM agent support with `mesh.llm()` and provider plugin architecture (#398, #400) - Vercel AI SDK v6 compatibility (#412) - meshctl TypeScript support - start, watch, and manage TS agents (#406) - **Gemini (Google AI) support** - New LLM provider alongside Claude/OpenAI (#416) ### 🔧 Improvements Low1/28/2026
v0.8.0-beta.9## v0.8.0-beta.9 (2026-01-20) ### 🎯 TypeScript SDK (Major) - **Full TypeScript support** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - **Rust core runtime** for multi-language FFI support (#388, #394) - **Express integration** via `mesh.route()` for dependency injection (#396) - **LLM agent support** with `mesh.llm()` and provider plugin architecture (#398, #400) - **Vercel AI SDK v6 compatibility** (#412) - **meshctl TypeScript support** - start, watch, and manageLow1/20/2026
v0.8.0-beta.8### 🎯 TypeScript SDK (Major) - **Full TypeScript support** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - **Rust core runtime** for multi-language FFI support (#388, #394) - **Express integration** via `mesh.route()` for dependency injection (#396) - **LLM agent support** with `mesh.llm()` and provider plugin architecture (#398, #400) - **Vercel AI SDK v6 compatibility** (#412) - **meshctl TypeScript support** - start, watch, and manage TS agents (#406) ### ✨ New FeLow1/19/2026
v0.8.0-beta.7### 🎯 TypeScript SDK (Major) - **Full TypeScript support** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - **Rust core runtime** for multi-language FFI support (#388, #394) - **Express integration** via `mesh.route()` for dependency injection (#396) - **LLM agent support** with `mesh.llm()` and provider plugin architecture (#398, #400) - **Vercel AI SDK v6 compatibility** (#412) - **meshctl TypeScript support** - start, watch, and manage TS agents (#406) ### ✨ New FeLow1/19/2026
v0.8.0-beta.6### 🎯 TypeScript SDK (Major) - **Full TypeScript support** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - **Rust core runtime** for multi-language FFI support (#388, #394) - **Express integration** via `mesh.route()` for dependency injection (#396) - **LLM agent support** with `mesh.llm()` and provider plugin architecture (#398, #400) - **Vercel AI SDK v6 compatibility** (#412) - **meshctl TypeScript support** - start, watch, and manage TS agents (#406) ### ✨ New FeLow1/17/2026
v0.8.0-beta.5### 🎯 TypeScript SDK (Major) - **Full TypeScript support** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - **Rust core runtime** for multi-language FFI support (#388, #394) - **Express integration** via `mesh.route()` for dependency injection (#396) - **LLM agent support** with `mesh.llm()` and provider plugin architecture (#398, #400) - **Vercel AI SDK v6 compatibility** (#412) - **meshctl TypeScript support** - start, watch, and manage TS agents (#406) ### ✨ New FeLow1/17/2026
v0.8.0-beta.4### 🎯 TypeScript SDK (Major) - **Full TypeScript support** with `@mcpmesh/sdk` npm package (#391, #398, #400, #403, #406) - **Rust core runtime** for multi-language FFI support (#388, #394) - **Express integration** via `mesh.route()` for dependency injection (#396) - **LLM agent support** with `mesh.llm()` and provider plugin architecture (#398, #400) - **Vercel AI SDK v6 compatibility** (#412) - **meshctl TypeScript support** - start, watch, and manage TS agents (#406) ### ✨ New FeLow1/17/2026

Dependencies & License Audit

Loading dependencies...

Similar Packages

agentic-ai🤖 Explore AI agent architectures with agentic-ai, featuring ReAct agents, reflection-based designs, and modular LLM integrations using LangChain and LangGraph.main@2026-06-05
Ollama-Terminal-AgentAutomate shell tasks using a local Ollama model that plans, executes, and fixes commands without cloud or API dependencies.main@2026-06-04
mcp-audit🌟 Track token consumption in real-time with MCP Audit. Diagnose context bloat and unexpected spikes across MCP servers and tools efficiently.main@2026-06-06
mcp-rag-agent🔍 Build a production-ready RAG system that combines LangGraph and MCP integration for precise, context-aware AI-driven question answering.main@2026-06-06
atmosphereReal-time transport layer for Java AI agents. Build once with @Agent — deliver over WebSocket, SSE, gRPC, and WebTransport/HTTP3. Talk MCP, A2A and AG-UI. atmosphere-4.0.50

More in MCP Servers

AstrBotAgentic IM Chatbot infrastructure that integrates lots of IM platforms, LLMs, plugins and AI feature, and can be your openclaw alternative. ✨
agentscopeBuild and run agents you can see, understand and trust.
claude-plugins-officialOfficial, Anthropic-managed directory of high quality Claude Code Plugins.
langchain4jLangChain4j is an open-source Java library that simplifies the integration of LLMs into Java applications through a unified API, providing access to popular LLMs and vector databases. It makes impleme