chore: add Neon MCP server configuration#273
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded@saddlepaddle has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 2 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughAdds a new Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
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 |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
143e779 to
39f7eee
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.mcp.json(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: superset-sh/superset PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-06T18:44:13.277Z
Learning: Use a new Neon branch for creating migrations locally; update `.env` files to point to the Neon branch during development
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Build
| { | ||
| "mcpServers": { | ||
| "neon": { | ||
| "command": "npx", | ||
| "args": ["-y", "@neondatabase/mcp-server-neon", "start"], | ||
| "env": { | ||
| "NEON_API_KEY": "${NEON_API_KEY}" | ||
| } | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Find documentation files and environment setup files
find . -type f \( -name "README.md" -o -name "AGENTS.md" -o -name ".env.example" -o -name ".env" \) 2>/dev/null | head -20Repository: superset-sh/superset
Length of output: 288
🏁 Script executed:
# Check if there are other .mcp.json files or MCP-related configurations
find . -type f -name "*.json" | grep -i mcpRepository: superset-sh/superset
Length of output: 75
🏁 Script executed:
# Search for references to NEON_API_KEY setup or documentation
rg "NEON_API_KEY" --type markdown --type text -A 3 -B 3Repository: superset-sh/superset
Length of output: 92
🏁 Script executed:
# Look for any setup or installation documentation
find . -type f \( -name "*.md" -o -name "SETUP*" -o -name "INSTALL*" \) | head -20Repository: superset-sh/superset
Length of output: 625
🏁 Script executed:
# Check .env.example for NEON_API_KEY
cat .env.exampleRepository: superset-sh/superset
Length of output: 191
🏁 Script executed:
# Check AGENTS.md for Neon documentation
cat AGENTS.mdRepository: superset-sh/superset
Length of output: 9884
🏁 Script executed:
# Check README.md for setup instructions (first 100 lines)
head -100 README.mdRepository: superset-sh/superset
Length of output: 3690
🏁 Script executed:
# Search for NEON references in documentation
rg -i "neon" --type md -A 2 -B 2 | head -50Repository: superset-sh/superset
Length of output: 1433
🏁 Script executed:
# Verify npx version pinning syntax works
echo "Testing if npx supports version pinning in package names..."
# Example: npx -y package-name@1.0.0
# This is standard npm package specification syntax
rg "npx.*@" | head -10Repository: superset-sh/superset
Length of output: 215
Pin package version and add NEON_API_KEY setup documentation.
The .mcp.json configuration is valid, but two improvements are needed:
- Package version not pinned:
npx -y @neondatabase/mcp-server-neonwill always fetch the latest version, risking inconsistent behavior across environments. The codebase already uses version-pinned packages (e.g.,npx shadcn@latest), so pin this package as well:
- "args": ["-y", "@neondatabase/mcp-server-neon", "start"],
+ "args": ["-y", "@neondatabase/mcp-server-neon@1.0.0", "start"],- Setup documentation missing:
NEON_API_KEYis not documented anywhere. Add it to.env.example:
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/superset
VITE_DEV_SERVER_PORT=4927
WEBSITE_URL=http://localhost:3001
+NEON_API_KEY=your_neon_api_key_hereAdditionally, add a section to AGENTS.md explaining MCP server setup under the Database section.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In .mcp.json around lines 1 to 11 the mcp-server command uses an unpinned
package (@neondatabase/mcp-server-neon) and NEON_API_KEY is undocumented; pin
the package by changing the npx invocation to a specific version (e.g.,
@neondatabase/mcp-server-neon@<VERSION>) so builds are deterministic, add
NEON_API_KEY to .env.example with a short comment and placeholder value, and
update AGENTS.md under the Database section with a short subsection describing
how to obtain/set NEON_API_KEY and how to start the MCP server using the pinned
npx command.
39f7eee to
b3d7eca
Compare
Adds .mcp.json with Neon MCP server config so Claude Code can interact with Neon databases. Developers need to set NEON_API_KEY env var. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
b3d7eca to
ea63f70
Compare
Summary
.mcp.jsonwith Neon MCP server config for Claude CodeNEON_API_KEYenvironment variableTest plan
🤖 Generated with Claude Code
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.