Skip to content

v0.2.0 — sign-in for --http

Choose a tag to compare

@Masterplanner25 Masterplanner25 released this 16 Nov 04:40
· 2 commits to main since this release
be060f9

Sign-in for --http, so the server can sit behind a public URL that claude.ai and ChatGPT reach. Off unless you turn it on. stdio, and --http without --public-url, behave exactly as in 0.1.16.

pipx upgrade nodus-mcp-server
nodus-mcp-server set-passphrase
nodus-mcp-server --http --port 8765 --public-url https://<your-domain>

Then add https://<your-domain>/mcp as a connector in claude.ai (choose DCR) or ChatGPT (OAuth). Your browser opens a consent page on your own server. Pick what the app may do and enter your passphrase.

Added

  • With --public-url (or NODUS_MCP_PUBLIC_URL), the server is its own OAuth 2.1 authorization server, built on the mcp SDK's handlers. It provides:
    • dynamic client registration: open, capped at 50 clients, rate-limited;
    • authorization code with PKCE (S256 only) and a consent page;
    • token, refresh and revocation endpoints, plus both metadata documents.
  • /mcp then needs a bearer token.
  • Scopes per tool: memory.read (the only one ticked by default), memory.write, workflow.run, exec. An app sees and can call only the tools its token allows.
  • nodus_exec is not offered over the public URL unless you pass --allow-remote-exec.
  • Tokens:
    • Opaque, and stored only as hashes.
    • Access tokens last 1 hour. Refresh tokens last 30 days and rotate on every use, and replaying an old one signs the app out.
    • A new passphrase signs every app out.
  • nodus-mcp-server grants list | revoke <id> shows and ends connected apps.
  • With --public-url, the MCP transport checks Host and Origin.

Changed

  • The --http help text says streamable HTTP at /mcp, not SSE.
  • The startup message no longer tells you to point ChatGPT at a localhost URL.

Full details: CHANGELOG.md · PyPI: https://pypi.org/project/nodus-mcp-server/0.2.0/