keyline

keyline runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/keyline-dev/keyline/releases/download/v0.7.0/keyline-mcp-0.7.0.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.

keyline runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/keyline-dev/keyline-mcp:0.7.0. 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 ghcr.io/keyline-dev/keyline-mcp:0.7.0.

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

{
  "mcpServers": {
    "keyline": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/keyline-dev/keyline-mcp:0.7.0"
      ]
    }
  }
}

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