Skip to content

feat(mcp): connect via OAuth instead of API token - #3

Open
elek-hmd wants to merge 1 commit into
hackmdio:mainfrom
elek-hmd:feat/oauth-mcp
Open

feat(mcp): connect via OAuth instead of API token#3
elek-hmd wants to merge 1 commit into
hackmdio:mainfrom
elek-hmd:feat/oauth-mcp

Conversation

@elek-hmd

@elek-hmd elek-hmd commented Sep 4, 2026

Copy link
Copy Markdown

Summary

  • Point .mcp.json at https://mcp.hackmd.io/ with URL-only OAuth. Remove mcp-remote and Bearer token interpolation from the MCP path.
  • Update README, setup-hackmd, and the workflow rule so Cursor agents complete the browser OAuth flow instead of asking for HMD_API_ACCESS_TOKEN.
  • Leave CLI login / API token on the hackmd-cli skill only, with an explicit boundary that those credentials are not for MCP.

Test plan

  • Merge the new .mcp.json into a Cursor user config (or load the plugin) and fully quit/reopen Cursor
  • Invoke a HackMD MCP tool and complete the browser OAuth prompt
  • Confirm list-notes (or equivalent) succeeds with no API token in MCP config
  • Confirm README / setup-hackmd no longer show mcp-remote@0.1.38 or Authorization:Bearer as the MCP setup
  • Optional: hackmd-cli login still works independently of MCP OAuth

Made with Cursor

Agents following this repo were still copying mcp-remote plus a Bearer token. Point .mcp.json at the hosted OAuth server and drop token setup from the MCP path.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant