mesh-mcp-bridge
Bidirectional bridge between MCP servers and the MARS protocol network. It publishes MCP server capabilities as mesh descriptors and exposes mesh capabilities to MCP-compatible agents as standard MCP tools.
Install
pip install mesh-mcp-bridge
Live Network
Connect your gateway to any MARS hub:
| Hub | Address | Location |
|---|---|---|
| us-east | 5.161.53.251:4433 |
Ashburn, VA |
| us-west | 5.78.197.92:4433 |
Hillsboro, OR |
| eu-central | 46.225.55.16:4433 |
Nuremberg, DE |
| ap-southeast | 5.223.69.128:4433 |
Singapore |
# Start a gateway connected to the live mesh
./target/release/mesh-gateway --seed 5.161.53.251:4433 --listen 0.0.0.0:3000
Usage
Publish MCP server tools to the mesh
mesh-mcp-bridge publish \
--gateway http://localhost:3000 \
--mcp-server "python my_mcp_server.py" \
--name "my-tools"
This connects to the MCP server, lists its tools, and registers each one as a
mesh descriptor (type mcp/tool/{tool_name}).
Discover mesh capabilities via MCP
mesh-mcp-bridge serve \
--gateway http://localhost:3000 \
--transport stdio
Or over HTTP:
mesh-mcp-bridge serve \
--gateway http://localhost:3000 \
--transport http \
--port 8080
Any MCP-compatible agent can then connect to this server and see all
mcp/tool/* descriptors on the mesh as standard MCP tools.
Architecture
┌──────────────┐ ┌──────────────────┐ ┌──────────────┐
│ MCP Server │◄───────►│ mesh-mcp-bridge │◄───────►│ Mesh Gateway │
│ (tools) │ stdio │ │ HTTP │ /v1/publish │
└──────────────┘ │ publish mode: │ │ /v1/discover│
│ MCP → mesh │ └──────┬───────┘
│ │ │
│ serve mode: │ ▼
┌──────────────┐ │ mesh → MCP │ ┌──────────────┐
│ MCP Client │◄───────►│ │ │ Mesh DHT │
│ (agent) │ stdio/ └──────────────────┘ │ Network │
└──────────────┘ HTTP └──────────────┘
Publish mode — scans an MCP server's tool listing and registers each tool as a mesh descriptor so any mesh participant can discover it.
Serve mode — queries the mesh for mcp/tool/* descriptors and presents
them as MCP tools. When an agent invokes a tool the bridge forwards the call
to the endpoint recorded in the descriptor.
Links
Metadata
Release files for mesh-mcp-bridge 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mesh_mcp_bridge-0.1.0.tar.gz | 5.9 kB | Without provenance | Details for mesh_mcp_bridge-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mesh_mcp_bridge-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mesh_mcp_bridge-0.1.0-py3-none-any.whl |
Total release size: 14.1 kB
Release files / mesh_mcp_bridge-0.1.0.tar.gz
| Download URL | mesh_mcp_bridge-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
adeb6a49034686f3a6a16fe848465117bd8c628a158e4f1da005f9ebed8317e3
|
|
BLAKE2b-256 checksum How to use checksums |
983098a3784404cdf0558942e7a502af25da6936c9bd4944c309f8d56c758514
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / mesh_mcp_bridge-0.1.0-py3-none-any.whl
| Download URL | mesh_mcp_bridge-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82fde96670f5e57b36d24e20238cd7fc7a259f0b24bd4881911f849b0b4c3614
|
|
BLAKE2b-256 checksum How to use checksums |
a976151b849f9ef508e3df188a25ce64dfa6342f62d8bb42c024ffb5f1514b7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for mesh-mcp-bridge 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.