Pursers

Pursers runs locally from a Python package published to PyPI: pursers-central version 0.1.7. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names uvx as the runtime). It reads these environment variables: ONBOARD_CENTRAL_HOST, ONBOARD_CENTRAL_PORT, ONBOARD_CENTRAL_DATA_DIR, ONBOARD_CENTRAL_LOG_LEVEL, ONBOARD_CENTRAL_ALLOWED_HOSTS, ONBOARD_CENTRAL_TLS_CERTFILE, ONBOARD_CENTRAL_TLS_KEYFILE (secret), CENTRAL_ADMISSION, CENTRAL_AUTH_MODE, CENTRAL_JWKS_PATH (required), CENTRAL_JWT_AUDIENCE, CENTRAL_JWT_CLOCK_SKEW, CENTRAL_JWT_ISSUER (required), CENTRAL_PRINCIPAL_STREAM_CAP, CENTRAL_REAPER_INTERVAL_S, CENTRAL_REQUEST_STATE_KEY_FILE (secret), PURSERS_LEGACY_TOOLS and STORE_BACKEND; set them in the client's configuration for this server. Required arguments: --data-root.

Pursers runs locally from a Python package published to PyPI: pursers-client version 0.1.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx pursers-client. Required arguments: --central-url, --board and --token-file.

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

{
  "mcpServers": {
    "pursers": {
      "command": "uvx",
      "args": [
        "pursers-client"
      ]
    }
  }
}

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