docs(readme): document OAuth install path for hosted MCP#4
Merged
Conversation
After noticedso/noticed#107 deploys, mcp.noticed.so/api/mcp accepts OAuth 2.1 alongside the existing API-key Bearer path. Document the OAuth path as the recommended option for claude.ai web custom connectors (which don't support custom Authorization headers), and keep the API-key path documented for Claude Code / Cursor / etc. that prefer header-based auth. The stdio CLI itself is unchanged — it remains API-key-only since it runs on the user's machine with NOTICED_API_KEY in their config. Bump 0.3.1 → 0.3.2 to trigger the auto-release workflow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
After noticedso/noticed#107 (the OAuth 2.1 authorization server) deploys,
mcp.noticed.so/api/mcpwill accept OAuth alongside the existingnk_live_API-key Bearer path. This PR documents the OAuth install option in the README, which unblocksclaude.ai's web custom-connector flow (whose UI has no field for a customAuthorizationheader).Important: do not merge until
noticedso/noticed#107is merged AND deployed to production. If this README ships first, users following the OAuth instructions will hit a 401 because the OAuth endpoints don't exist yet.What changed
claude.ai,ChatGPT MCP, and anything that does OAuth discovery + DCR. claude.ai users just paste the URL into the connector dialog; the consent flow handles the rest. Connected applications are visible/revocable at/dashboard/oauth-grants.NOTICED_API_KEY, no OAuth flow needed.0.3.1 → 0.3.2. The release workflow (PR #2) auto-publishes onpackage.jsonversion change merging to main.No code changes
The cli code (
src/api-client.ts,src/mcp-server.ts, etc.) is untouched. The stdio CLI is a pure API-key client ofnoticed.so's REST endpoints — it never talks tomcp.noticed.soand never participates in an OAuth flow. The cli will continue working exactly as today.Test plan
npm run lintcleannpm run check-typescleannpm test32/32 passingnoticedso/noticed#107→ smokemcp.noticed.so/api/mcpOAuth flow against the production deploy → merge this PR → auto-publish workflow ships@noticed/cli@0.3.2🤖 Generated with Claude Code