Which mesh networking SDKs have an MCP server?

The Model Context Protocol (MCP) is an open protocol for connecting AI applications, such as coding agents and chat assistants, to external tools and data. An MCP server exposes tools that the agent can call. A server can run on your machine and talk to the agent over standard input and output, or run remotely and talk over HTTP.

For an SDK vendor, an MCP server is a way to give coding agents accurate, current information instead of whatever the model remembers from training. That matters most for young or fast-moving SDKs, where an agent’s memory is likely to be out of date or wrong.

Servers published by SDK vendors tend to fall into three kinds:

• Documentation search. The agent can search and read the vendor’s docs.
• Integration and scaffolding. The agent can look up packages, read integration guidance, plan an app, and generate project files.
• Device control. The agent can talk to real hardware, for example to send a test message or read a device’s state.

Checked on 1 October 2026 against each vendor’s own documentation and GitHub organisation.

Offline Protocol. Three ways to connect, documented on its CLI and MCP page:

• Local MCP. Started with npx -y @offline-protocol/cli@0.2.6 mcp serve. It runs on your machine over standard input and output, needs no login or API key, and provides 18 tools for packages, capabilities, workflows, examples, skills, templates, planning, and scaffolding. Three of them write project files.
• Hosted MCP at https://mcp.offlineprotocol.com/mcp. It takes an application API key as a bearer token and the matching App ID in an x-app-id header, offers 15 read-only tools, and cannot write files.
• Public read-only endpoint at https://mcp.offlineprotocol.com/public/mcp. It needs no account, key, or headers, offers 15 read-only tools for package, workflow, guide, and template lookup, planning, and scaffold preview, and is the one to use in Claude.ai and Claude Desktop, either as a custom connector or through the Offline Protocol connector in Claude’s connector directory.

None of the three runs the mesh or talks to devices. They are for building the integration. A separate docs MCP server at https://www.offlineprotocol.com/docs/mcp searches and reads the documentation only.

Meshtastic. The Meshtastic project publishes meshtastic-mcp under its GitHub organisation, licensed GPL-3.0. It is a device-control server: its README describes tools to discover, drive, observe, and test Meshtastic radios over a serial or TCP connection, such as listing nodes and sending a text, with optional capabilities for building and flashing firmware. It needs a Meshtastic device, which is LoRa hardware rather than a phone.

Ditto. Ditto, an offline-first sync database with peer-to-peer mesh replication, documents an MCP server at https://docs.ditto.live/mcp that lets Claude and other assistants search and reference its API documentation.

No vendor server found. We found no MCP server published by Bridgefy in its GitHub organisation, or by Google for Nearby Connections in its documentation. Community projects sometimes fill gaps like this; check who maintains one before trusting it with your code.

This list will date. Before relying on it, check the vendor’s docs and GitHub organisation, and public MCP registries.

Each MCP client has its own setup, but the shape is the same: give the client a command to start a local server, or a URL for a remote one.

For a local server in Claude Code:

claude mcp add offline-protocol -- npx -y @offline-protocol/cli@0.2.6 mcp serve

For a remote server with no authentication, such as a public read-only endpoint, add the URL as a custom connector in Claude.ai or Claude Desktop, or as an HTTP server in your client’s MCP configuration.

Offline Protocol’s docs ask for one mode per client under the offline-protocol name, not the local and hosted modes side by side.

• Who publishes it? A server from the vendor’s own organisation is more likely to track the current release than a community one.
• What can it change? Read-only servers cannot modify your project. Local scaffolding tools write files and run package-manager commands with your permissions, so keep your client’s approval prompts on.
• What does it send? A hosted server receives the tool arguments your agent sends. Check the vendor’s privacy statement.
• Is it pinned? A server started from a pinned version gives repeatable results. An unpinned one changes when the package does.
• Does it touch hardware? A device-control server can send real traffic over the air. Use test devices.