BioMapper MCP Server

What the code does

We read the source, 9 h ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      "image/png": "iVBORw0KGgoAAAANSUhEUgAAAvQAAAFPCAYAAAAiOVo9AAAAOnRFWHRTb2Z0d2FyZQBNYXRwbG90bGliIHZlcnNpb24zLjExLjIsIGh0dHBzOi8vbWF0cGxvdGxpYi5vcmcvgI3uAAAAAAlwSFlzAAAPYQAAD2EBqD+naQAAtrNJREFUeJzs3XdUFEn3N/AvOQcRAVEyCiIqigpGUFAQjDwKCgYUA8Z1xYx5MWLO7rqoK8Y1rIg5h1VWzJhQQQQRJOcM…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add biomapper -- uvx biomapper

{
  "mcpServers": {
    "biomapper": {
      "command": "uvx",
      "args": [
        "biomapper"
      ]
    }
  }
}

[mcp_servers.biomapper]
command = "uvx"
args = ["biomapper"]

{
  "mcpServers": {
    "biomapper": {
      "command": "uvx",
      "args": [
        "biomapper"
      ]
    }
  }
}

{
  "servers": {
    "biomapper": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "biomapper"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: BIOMAPPER_MCP_ROOTS (Folders map_file may read and write, path-separated (needed when the client shares no roots)), BIOMAPPER_API_KEY (Optional API key; the hosted deployment is keyless), BIOMAPPER_BASE_URL (Override the API root (staging or a local engine)), BIOMAPPER_MCP_HOME (Where job state lives (default ~/.cache/biomapper/mcp)).