Skip to content

chore: add Neon MCP server configuration#273

Merged
saddlepaddle merged 1 commit into
mainfrom
enthusiastic-porpoise-75c000
Dec 7, 2025
Merged

chore: add Neon MCP server configuration#273
saddlepaddle merged 1 commit into
mainfrom
enthusiastic-porpoise-75c000

Conversation

@saddlepaddle
Copy link
Copy Markdown
Collaborator

@saddlepaddle saddlepaddle commented Dec 6, 2025

Summary

  • Adds .mcp.json with Neon MCP server config for Claude Code
  • Enables Claude Code to interact with Neon databases directly
  • Developers need to set NEON_API_KEY environment variable

Test plan

  • Verify Claude Code picks up the MCP config
  • Test Neon MCP tools work with API key set

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features
    • Added Neon integration: a new MCP server entry to enable running the Neon service and reading NEON_API_KEY from the host environment to authenticate.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link
Copy Markdown

vercel Bot commented Dec 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
website Ready Ready Preview Comment Dec 6, 2025 11:35pm

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Dec 6, 2025

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

📥 Commits

Reviewing files that changed from the base of the PR and between 39f7eee and ea63f70.

📒 Files selected for processing (2)
  • .env.example (1 hunks)
  • .mcp.json (1 hunks)

Walkthrough

Adds a new .mcp.json configuration that defines an MCP server entry named "neon", specifying the npx command and arguments to start the Neon MCP server and declaring NEON_API_KEY sourced from the host environment.

Changes

Cohort / File(s) Summary
MCP Server Configuration
./.mcp.json
New configuration file adding a "neon" MCP server entry that runs npx -y @neondatabase/mcp-server-neon start with NEON_API_KEY mapped from the host environment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Verify command/arguments for npx are correct and compatible with expected MCP server invocation.
  • Confirm NEON_API_KEY is referenced correctly and documented for operator/CI use.

Poem

🐰 I nibble configs, neat and keen,
A neon server, bright and clean.
With key from home and command to start,
I hop and cheer — a tiny art! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description covers the key aspects (Summary and Test plan) but omits several required template sections including Related Issues, Type of Change, Testing details, Screenshots, and Additional Notes. Complete the pull request description by filling in the remaining template sections, particularly specifying the Type of Change and providing detailed Testing steps beyond the checklist.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: adding a Neon MCP server configuration file. It's concise, specific, and directly related to the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 6, 2025

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

  • ✅ Neon database branch

Thank you for your contribution! 🎉

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b757e79 and 143e779.

📒 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

Comment thread .mcp.json
Comment on lines +1 to +11
{
"mcpServers": {
"neon": {
"command": "npx",
"args": ["-y", "@neondatabase/mcp-server-neon", "start"],
"env": {
"NEON_API_KEY": "${NEON_API_KEY}"
}
}
}
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 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 -20

Repository: 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 mcp

Repository: 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 3

Repository: 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 -20

Repository: superset-sh/superset

Length of output: 625


🏁 Script executed:

# Check .env.example for NEON_API_KEY
cat .env.example

Repository: superset-sh/superset

Length of output: 191


🏁 Script executed:

# Check AGENTS.md for Neon documentation
cat AGENTS.md

Repository: superset-sh/superset

Length of output: 9884


🏁 Script executed:

# Check README.md for setup instructions (first 100 lines)
head -100 README.md

Repository: 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 -50

Repository: 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 -10

Repository: 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:

  1. Package version not pinned: npx -y @neondatabase/mcp-server-neon will 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"],
  1. Setup documentation missing: NEON_API_KEY is 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_here

Additionally, 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.

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>
@saddlepaddle saddlepaddle force-pushed the enthusiastic-porpoise-75c000 branch from b3d7eca to ea63f70 Compare December 6, 2025 23:35
@saddlepaddle saddlepaddle merged commit b8fedfd into main Dec 7, 2025
8 checks passed
@Kitenite Kitenite deleted the enthusiastic-porpoise-75c000 branch December 7, 2025 23:52
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