Pursers MCP Server

Pursers is an MCP integration. Coordinate AI-agent work on a local-first, owner-controlled MCP board.

Packages and local setup

The published pypi package is pursers-central, version 0.1.8. Its declared MCP transport is streamable-http.

The package declares ONBOARD_CENTRAL_HOST: Loopback bind host used by the packaged runtime; ONBOARD_CENTRAL_PORT: Loopback bind port used by the packaged runtime; ONBOARD_CENTRAL_DATA_DIR: Private Central data directory; --data-dir/--data-root is the equivalent CLI input; ONBOARD_CENTRAL_LOG_LEVEL: Packaged runtime log level; ONBOARD_CENTRAL_ALLOWED_HOSTS: Optional comma-separated bare Host names accepted in addition to the bind host; ONBOARD_CENTRAL_TLS_CERTFILE: Optional TLS certificate path; requires ONBOARD_CENTRAL_TLS_KEYFILE; ONBOARD_CENTRAL_TLS_KEYFILE: Optional TLS private-key path; requires ONBOARD_CENTRAL_TLS_CERTFILE; CENTRAL_ADMISSION: Central admission policy; Pursers supports invite-only admission; CENTRAL_AUTH_MODE: Central authentication mode; Pursers supports JWT authentication; CENTRAL_JWKS_PATH (required): Path to the issuer public JWKS used to verify seat credentials; CENTRAL_JWT_AUDIENCE: MCP resource URL in audience and resource claims; defaults to the loopback bind URL; CENTRAL_JWT_CLOCK_SKEW: Allowed JWT clock skew in seconds; CENTRAL_JWT_ISSUER (required): Exact issuer URL in every accepted seat credential; CENTRAL_PRINCIPAL_STREAM_CAP: Maximum concurrent event streams accepted per principal; CENTRAL_REAPER_INTERVAL_S: Interval in seconds between expired-lease reaper sweeps; CENTRAL_REQUEST_STATE_KEY_FILE: Optional restart-safe request-state keyring path; PURSERS_LEGACY_TOOLS: String flag: use 1 to expose deprecated coordination tools; use 0 to keep them hidden; STORE_BACKEND: Central storage backend; Pursers supports SQLite.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

The published pypi package is pursers-client, version 0.1.9. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 5.2.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.