Inkwell

Inkwell runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/foreigndmitryi/inkwell-memory:0.14.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 -e INKWELL_DATA_PATH -e INKWELL_ENABLE_DASHBOARD docker.io/foreigndmitryi/inkwell-memory:0.14.0. It reads these environment variables: INKWELL_DATA_PATH and INKWELL_ENABLE_DASHBOARD; set them in the client's configuration for this server. Required arguments: -v.

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

{
  "mcpServers": {
    "inkwell-memory": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "INKWELL_DATA_PATH",
        "-e",
        "INKWELL_ENABLE_DASHBOARD",
        "docker.io/foreigndmitryi/inkwell-memory:0.14.0"
      ],
      "env": {
        "INKWELL_DATA_PATH": "<value>",
        "INKWELL_ENABLE_DASHBOARD": "<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