Loading ToolBench

Reading the current corpus…

neon-mcp MCP server · D · ToolBench

← Browse

neon-mcp

github.com/mcpnexus-registry/neon-mcp

MCP server for Neon database management, providing tools to manage projects, branches, databases, and schemas

2026-07-28+STREAMABLE_HTTP8 tools

50/100

Definition Quality56

Protocol Readiness75

Supportability23

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

neon-mcp provides 8 tools with complete input schemas and basic descriptions. All tools have verb-noun naming (list*, get*, delete*, restore*, compare*, retrieve*) and documented parameters with types. However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool, prerequisites, or return value details. Parameter descriptions are present but terse. No output schemas documented. Error handling is absent, no guidance on retryability, user-fixable errors, or recovery paths. Tools lack idempotency markers and confirmation patterns for destructive operations (deleteBranch, restoreBranch). Composition is sound: tools chain naturally (listProjects → listBranches → getBranch). Security: credentials injected via env.NEON_API_KEY (correct pattern). Overall: functional but minimal, typical of community servers.

Tools (8)

compareSchemasread onlyauth50/100

Compare schemas between branches.

deleteBranchdestructiveauth50/100

Delete a specific branch.

getBranchread onlyauth50/100

Get details of a specific branch.

listBranchesread onlyauth50/100

List all branches for a project.

listDatabasesread onlyauth50/100

List all databases for a branch.

listProjectsread onlyauth50/100

List all projects.

restoreBranchwriteauth50/100

Restore a branch to a specific point.

retrieveDatabaseSchemaread onlyauth50/100

Retrieve the schema of a database.

Issues (5)

HIGHtool-description ↗

Descriptions are too brief (10-50 chars) and lack context. 'List all projects' does not explain WHEN to call this vs other discovery tools, what structure is returned, or how to use results downstream. LLMs need 50-200 char descriptions with purpose, prerequisites, and return hints.

listProjectslistBranchesgetBranchdeleteBranchcompareSchemaslistDatabases

HIGHresponse-shaper ↗

No output schemas documented. Callers cannot know what fields to expect (e.g., does listProjects return project_id, name, status?). This forces LLMs to guess and risks downstream tool failures when chaining results.

listProjectslistBranchesgetBranchdeleteBranchrestoreBranchcompareSchemasretrieveDatabaseSchemalistDatabases

HIGHconfirmation-request ↗

Destructive operations (deleteBranch, restoreBranch) lack confirmation or dry-run patterns. Agents can accidentally delete branches without a safety gate. No error guidance on retryability or recovery.

Recommendations

Expand tool descriptions to 50-200 chars. Example: 'List all projects in your Neon account. Call this first to discover available projects before querying branches. Returns project_id, name, and status for each project.'
Document output schemas for each tool. Specify which fields are returned (e.g., listProjects returns [{project_id: string, name: string, status: string}]). This enables LLMs to chain tools correctly.
Add tool annotations: mark listProjects, listBranches, getBranch, compareSchemas, retrieveDatabaseSchema, listDatabases with readOnlyHint=true; mark deleteBranch with destructiveHint=true; mark restoreBranch with destructiveHint=true.
Implement a confirmation pattern for deleteBranch: add a dry_run parameter or require explicit confirmation before deletion. Return a confirmation token that must be passed to a separate confirm_delete_branch tool.
Enhance parameter descriptions with format and constraint hints. E.g., 'projectId (string, UUID format, e.g. proj_abc123def456), the Neon project identifier. Find it in the Neon dashboard or via listProjects.'
Add error handling guidance: document which errors are retryable (network timeouts) vs user-fixable (invalid projectId) vs fatal. Return actionable error messages like 'Project not found. Call listProjects to see available projects.'

Score history

Overall score trend

First recorded score · v2 rubric

50/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	50	2026-07-28+	v2