You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OAuth sign-in for the hosted server. With --http, the server is now an
OAuth 2.1 resource server per the MCP authorization spec (revision
2026-07-28): protected-resource metadata at /.well-known/oauth-protected-resource, a 401 + WWW-Authenticate: Bearer resource_metadata="…" challenge for
unauthenticated requests, access-token validation by introspection with an
audience check, and no token passthrough. Clients that support remote MCP
authorization (Claude, ChatGPT, Cursor, Gemini CLI, VS Code) can connect to https://mcp.planpo.st/mcp with no key. Enabled by PLANPOST_MCP_PUBLIC_URL + PLANPOST_MCP_SERVICE_SECRET; without them the
server behaves exactly as before.
Tool annotations on all 49 tools: title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint.
Agent bundles in the repository: skills/planpost/SKILL.md
(npx skills add), gemini-extension.json + GEMINI.md (Gemini CLI
extension), .claude-plugin/ (Claude Code plugin and marketplace) and .cursor-plugin/ + mcp.json (Cursor plugin).
Tests for hosted OAuth mode and for manifest consistency; npm test now
builds first.
Changed
server.json: the hosted remote's Authorization header is optional
(omit it to sign in with OAuth).
API-key authentication (Authorization: Bearer pk_… over HTTP, PLANPOST_API_KEY over stdio) is unchanged.