quillink-mcp

An MCP server exposing read-only access to your Quillink notes, folders, and tags to AI tools like Claude Desktop, Claude Code, and other MCP-compatible clients.

Requires a Pro Quillink plan (API Access is a Pro-only feature).

Not published to PyPI -- build and run it locally from source.

Build

git clone https://github.com/dagistankaradeniz/gcp-note-taking-mcp.git
cd gcp-note-taking-mcp
python3 -m venv .venv
.venv/bin/pip install -e .

This installs the quillink-mcp command into .venv/bin/. Note the full path to that binary (e.g. /Users/you/gcp-note-taking-mcp/.venv/bin/quillink-mcp) -- MCP clients launch it directly, not through an activated shell, so they need the absolute path.

Related MCP server: Bruin

Authenticate

Two options:

Option A — OAuth device login (recommended for interactive use):

.venv/bin/quillink-mcp login

Opens a device code + verification URL; approve it in your browser. The token is stored in your OS keyring (or ~/.config/quillink-mcp/credential as a fallback).

Option B — Personal Access Token:

Create one in Quillink under Settings → Developer → Tokens (scopes: notes:read, folders:read, tags:read), then set it as an environment variable:

export QUILLINK_TOKEN=qlk_pat_...

QUILLINK_TOKEN always takes priority over a stored OAuth login.

Use with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "quillink": {
      "command": "/absolute/path/to/gcp-note-taking-mcp/.venv/bin/quillink-mcp"
    }
  }
}

If using a PAT instead of login, pass it as an env var in the config:

{
  "mcpServers": {
    "quillink": {
      "command": "/absolute/path/to/gcp-note-taking-mcp/.venv/bin/quillink-mcp",
      "env": { "QUILLINK_TOKEN": "qlk_pat_..." }
    }
  }
}

Restart Claude Desktop after editing the config.

Use with other MCP clients

Any client that can launch a local stdio MCP server works the same way: point it at the absolute path to .venv/bin/quillink-mcp (with QUILLINK_TOKEN set, or after running quillink-mcp login once so the credential is already stored). This includes Claude Code (claude mcp add quillink -- /absolute/path/to/.venv/bin/quillink-mcp) and any OpenAI-compatible agent runtime that supports the MCP stdio transport.

Tools

All read-only — this server cannot create, edit, or delete anything.

Vault notes are never accessible here — they're end-to-end encrypted client-side, so no server (including this one) can read them. Organization tools 404 for a caller who isn't on a Team-plan organization.

Configuration (environment variables)

Running it directly (for testing)

.venv/bin/quillink-mcp login
.venv/bin/quillink-mcp   # runs the server on stdio -- an MCP client normally launches this for you