Neon

Created By
a year ago
Interact with the Neon serverless Postgres platform
Overview

What is Neon?

Neon is a serverless Postgres platform that allows users to interact with their databases through natural language commands via the Model Context Protocol (MCP).

How to use Neon?

To use Neon, set up the MCP Server by running a simple initialization command with your Neon API key, and then integrate it with Claude Desktop to communicate with your database.

Key features of Neon?

  • Natural language processing for database management
  • Supported commands for project and branch management
  • Migration support with 'Start' and 'Commit' functionalities to handle schema changes safely
  • Allows CRUD operations on tables and projects

Use cases of Neon?

  1. Create new Postgres databases and manage their schemas using natural language.
  2. Run migrations to alter existing database structures efficiently.
  3. Retrieve summaries and details of various database projects seamlessly.

FAQ from Neon?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol for managing the context between large language models and external systems to facilitate natural language interactions.

  • Do I need a special software to interact with Neon?

You need Claude Desktop and a Neon API key to use the MCP Server with Neon.

  • Is there specific Node.js version requirement for setting up Neon?

Yes, you need Node.js version 18.0.0 or higher to run the server successfully.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
-
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago