M
Meshkit

Configuration

Environment variables for the Meshkit MCP server.

Configure the MCP server through environment variables set in your client's config file.

Environment variables

VariableDefaultDescription
MESHKIT_NODEShttp://127.0.0.1:5001Comma-separated Kubo RPC URLs, in priority order.
MESHKIT_HEADERSJSON object for RPC auth headers, e.g. {"Authorization":"Bearer token"}.
MESHKIT_LOCAL_NODEfalseStart or attach to a local Kubo daemon. Accepts true, 1, or yes. Requires ipfs on PATH.

Multiple nodes

{
  "env": {
    "MESHKIT_NODES": "http://127.0.0.1:5001,https://backup.example.com:5001"
  }
}

With authentication

{
  "env": {
    "MESHKIT_NODES": "https://kubo.example.com:5001",
    "MESHKIT_HEADERS": "{\"Authorization\":\"Bearer your-token\"}"
  }
}

Local daemon auto-start

{
  "env": {
    "MESHKIT_LOCAL_NODE": "true"
  }
}

When MESHKIT_LOCAL_NODE is set, you do not need to set MESHKIT_NODES — the local node (http://127.0.0.1:5001) is used automatically. You can still set MESHKIT_NODES to add failover nodes alongside the local daemon.

On this page