pixl.directory
Neon logo

Neon

Access and manage your Neon serverless PostgreSQL databases through MCP tools, enabling direct database operations and management from Cursor.

Installation Instructions →

How to Use Model Context Protocol (MCP) in Cursor

What is MCP?

Model Context Protocol (MCP) is an open protocol that allows you to provide custom tools to agentic LLMs (Large Language Models) in Cursor's Composer feature.

Installation Steps

  1. Open Cursor Settings
    • Navigate to Cursor Settings > Features > MCP
    • Click the "+ Add New MCP Server" button
  2. Configure the Server
    • Name: Give your server a nickname
    • Type: Select the transport type (stdio or sse)
    • Command/URL: Enter either:
      • For SSE servers: The URL of the SSE endpoint
      • For stdio servers: A valid shell command to run the server

Example Configurations

For stdio Server (Neon Example):

Command: node ~/mcp-quickstart/neon-server/build/index.js --api-key $NEON_API_KEY --project-id $NEON_PROJECT_ID

For SSE Server:

URL: https://console.neon.tech/api/v2/sse

Using MCP Tools

Tool Availability

  • • After adding a server, it will appear in your MCP servers list
  • • You may need to click the refresh button to populate the tool list

Using Tools in Composer

  • • The Composer Agent automatically uses MCP tools when relevant
  • • You can explicitly prompt tool usage by:
    • Referring to the tool by name
    • Describing the tool's function

Tool Execution Process

  • • Displays a message in chat requesting approval
  • • Shows tool call arguments (expandable)
  • • Executes the tool upon user approval
  • • Displays the tool's response in the chat

Important Notes

  • • MCP tools may not work with all models
  • • MCP tools are only available to the Agent in Composer
  • • For Neon integration, you need to set up NEON_API_KEY and NEON_PROJECT_ID environment variables
  • • Generate an API key from your Neon dashboard (Settings > API Keys)
  • • Find your project ID in the project settings or URL
  • • For security, use a wrapper script that sets the environment variables before running the server
  • • Ensure your API key has the necessary permissions for database operations
  • • Consider using read-only API keys for query-only operations
  • • Be aware of connection limits and database branch lifecycle
← Back to Home