Footnote MCP Server

What the code does

We read the source, 2 d 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.

  $('answer').innerHTML = html;

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 footnote -- npx -y @brick-byte/footnote

{
  "mcpServers": {
    "footnote": {
      "command": "npx",
      "args": [
        "-y",
        "@brick-byte/footnote"
      ]
    }
  }
}

[mcp_servers.footnote]
command = "npx"
args = ["-y", "@brick-byte/footnote"]

{
  "mcpServers": {
    "footnote": {
      "command": "npx",
      "args": [
        "-y",
        "@brick-byte/footnote"
      ]
    }
  }
}

{
  "servers": {
    "footnote": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@brick-byte/footnote"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: DATABASE_URL (Postgres connection string. Omit to use the built-in SQLite sample database), PROVENANCE_DB (Path to the SQLite provenance log. Defaults to in-memory, which discards the trail on exit), PROVENANCE_ACTOR (Identity recorded against each provenance record. In production this comes from the request's auth).