neon-mcp

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

what is neon-mcp?

neon-mcp is a lightweight Model Control Protocol (MCP) server that allows agents, such as Cursor, to interface with the Neon REST API. It is designed to facilitate communication between your applications and the Neon API.

how to use neon-mcp?

To use neon-mcp, you need to run an automated install script to clone the server and deploy it to your Cloudflare account. After that, you can configure it in your Cursor settings and upload your Neon API key to your worker secrets.

key features of neon-mcp?

  • Lightweight and easy to deploy on Cloudflare Workers.
  • Interfaces with the Neon REST API for seamless integration.
  • Supports local development and deployment of changes.

use cases of neon-mcp?

  1. Enabling Cursor agents to access and utilize the Neon API.
  2. Facilitating the development of applications that require interaction with the Neon API.
  3. Providing a customizable MCP server for various tools and integrations.

FAQ from neon-mcp?

  • What is the purpose of neon-mcp?

neon-mcp serves as a bridge between your applications and the Neon API, allowing for easier integration and communication.

  • Is neon-mcp free to use?

Yes! neon-mcp is open-source and can be used freely under the MIT license.

  • How do I deploy changes to neon-mcp?

You can deploy changes by running the deploy script and reloading your Cursor window to use the updated tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zueai
Star
3
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago