Neon MCP Server

Created By
amxva year ago
Lightweight MCP server to give your Cursor Agent access to the Neon API
Overview

What is Neon MCP Server?

Neon MCP Server is a lightweight Model Control Protocol (MCP) server that provides access to the Neon API, deployed on Cloudflare Workers.

How to use Neon MCP Server?

To use the Neon MCP Server, run the automated setup script to clone the worker and deploy it to your Cloudflare account, then upload your Neon API key to your worker secrets.

Key features of Neon MCP Server?

  • Lightweight and easy to deploy on Cloudflare Workers
  • Interfaces with the Neon REST API
  • Automated setup script for quick deployment

Use cases of Neon MCP Server?

  1. Integrating with the Neon API for data management.
  2. Developing applications that require real-time data access through MCP.
  3. Simplifying the deployment of serverless applications using Cloudflare Workers.

FAQ from Neon MCP Server?

  • Is Neon MCP Server free to use?

Yes! Neon MCP Server is free to use as it is open-source.

  • What programming language is used?

The server is developed using TypeScript.

  • How do I deploy changes?

You can deploy changes by running the command bun run deploy after making your updates.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
amxv
Star
1
Language
TypeScript
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.

a day ago