Skip to content

Pass MCP config inline in npm run claude#6

Closed
mme wants to merge 1 commit into
mainfrom
mme/inline-mcp-config
Closed

Pass MCP config inline in npm run claude#6
mme wants to merge 1 commit into
mainfrom
mme/inline-mcp-config

Conversation

@mme

@mme mme commented Apr 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Pass MCP config as inline JSON to --mcp-config instead of writing and cleaning up a temp file
  • Also supports PORT env var override from prior PR

Test plan

  • Run npm run claude — verify Claude starts with mcp-docs tools available
  • Run PORT=3002 npm run claude — verify it connects to the correct port

--mcp-config accepts JSON strings directly, no need to create and
clean up a temp directory.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jpr5

jpr5 commented Apr 2, 2026

Copy link
Copy Markdown
Contributor

Closing — the issues this was trying to solve have been fixed differently:

  1. OAuth auth failure on newer Claude Code (>= 2.1.80): Root cause was stale OAuth discovery state cached in the macOS Keychain from failed connection attempts. The fix was "headers": {} in the MCP config (tells Claude Code to skip OAuth probing), plus returning 405 instead of 400 on GET /mcp without a session (the SDK expects 405 for "no SSE stream").

  2. Claude not using the tools: Fixed by creating a CLAUDE.md in the temp working dir that instructs Claude to use search-breeze-docs and submit-breeze-feedback.

Both fixes are on main. The inline config approach here would lose the "headers": {} and the CLAUDE.md, so it would regress both issues.

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.

2 participants