fix: MCP_API_KEY to avoid Railway shared variable conflict#286
Conversation
Railway shares env vars across services in the same project. The backend's API_KEY (dev-secret-key) was overriding the MCP service's ci_ key at runtime, causing 401 on every tool call. MCP_API_KEY takes precedence over API_KEY when both are set.
|
@DevanshuNEU is attempting to deploy a commit to the Dev's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe change modifies the API key configuration logic in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Railway shares env vars across services in the same project. The backend's API_KEY was overriding the MCP server's ci_ key at runtime.
Fix: MCP server now reads MCP_API_KEY first, falls back to API_KEY.
After merge, add MCP_API_KEY on Railway MCP service with the ci_ key value.
Summary by CodeRabbit