Evc Mesh MCP

Evc Mesh MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mesh.entire.host/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

It also lists an endpoint on the older SSE transport https://mesh.entire.host/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

The registry entry declares an HTTP header for the connection: X-Agent-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/entire-vc/evc-mesh-mcp:0.1.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e MESH_API_URL -e MESH_AGENT_KEY -e MESH_MCP_PROFILE ghcr.io/entire-vc/evc-mesh-mcp:0.1.5. It reads these environment variables: MESH_API_URL (required), MESH_AGENT_KEY (required, secret) and MESH_MCP_PROFILE; set them in the client's configuration for this server.

It can also run locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/entire-vc/evc-mesh-mcp/releases/download/v0.1.5/evc-mesh-mcp-0.1.5.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: MESH_API_URL (required), MESH_AGENT_KEY (required, secret) and MESH_MCP_PROFILE; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "evc-mesh-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MESH_API_URL",
        "-e",
        "MESH_AGENT_KEY",
        "-e",
        "MESH_MCP_PROFILE",
        "ghcr.io/entire-vc/evc-mesh-mcp:0.1.5"
      ],
      "env": {
        "MESH_API_URL": "<value>",
        "MESH_AGENT_KEY": "<secret>",
        "MESH_MCP_PROFILE": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect