fix: correct Claude Code and Cursor MCP install steps#46
Merged
Conversation
lhagenWP
reviewed
Jun 11, 2026
| "type": "http", | ||
| "url": "https://api.whitepages.com/mcp", | ||
| "headers": { | ||
| "x-api-key": "YOUR_API_KEY_HERE" |
Collaborator
There was a problem hiding this comment.
This header is not correct - it is case sensitive
https://api.whitepages.com/docs/documentation/making-your-first-request#add-your-api-key
Collaborator
Author
There was a problem hiding this comment.
it is not case sensitive, I confirmed this myself, but I will fix it here to be consistent.
lhagenWP
reviewed
Jun 11, 2026
| "WHITEPAGES_API_KEY": "YOUR_API_KEY_HERE" | ||
| "url": "https://api.whitepages.com/mcp", | ||
| "headers": { | ||
| "x-api-key": "YOUR_API_KEY_HERE" |
The Claude Code tab shipped a CLI command missing its transport and URL (it errored on run) and an unnecessary mcp-remote stdio bridge in both the Claude Code and Cursor JSON configs. Both clients support remote HTTP servers with custom headers natively. Replace with the working one-liner and native http configs, and soften the restart note to the in-session /mcp reconnect. Claude Desktop and Zed keep mcp-remote — they require the bridge.
060f40d to
7b2f4d7
Compare
lhagenWP
approved these changes
Jun 12, 2026
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
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
The MCP setup page shipped install instructions that don't work for Claude Code and route Cursor through an unnecessary bridge. The Claude Code CLI command was missing its transport and URL (it errors on run), and both the Claude Code and Cursor JSON configs used an
npx mcp-remotestdio bridge — but both clients support remote HTTP servers with custom headers natively.Changes
content/docs/documentation/mcp/index.mdx— Claude Code tab: replace the brokenclaude mcp add whitepages --scope userwith the workingclaude mcp add --transport http whitepages https://api.whitepages.com/mcp --header "x-api-key: …" --scope user, and themcp-remoteJSON with a native{type: http, url, headers}config.mcp-remotebridge with a native{url, headers}config./mcpreconnect (full restart only needed when hand-editing the JSON).mcp-remotestdio bridge.The
x-api-keyheader config stays correct under the upcoming anonymous + bring-your-own-key MCP model, so this won't need re-touching.