otherapi_key

Neon

Postgres, on a serverless platform designed to help you build reliable and scalable applications faster

Verdict

Neon is a serverless Postgres platform that separates storage from compute. In Switchy, @mentioning Neon lets your team provision databases, manage branches, configure compute endpoints, and control project permissions without leaving chat. Developers get instant access to schema details and connection strings; ops teams can spin up ephemeral environments for testing. You'll need an API key from your Neon console (Settings → API Keys). The MCP exposes 50 tools covering projects, branches, roles, and endpoints — enough to script most workflows, though complex migrations still need the web UI.

Common use cases

Provision ephemeral test databases from chat
Fetch connection strings during incident response
Create branch databases for feature work
Audit project permissions across teams
Generate API keys for new environments

Integration

Vendor: Neon
Category: other
Auth: API_KEY
Tools: 50
Composio slug: neon

Tools

Access project details by id
Retrieves detailed information about a specific project within the neon b2b saas integration platform. this endpoint is used to fetch comprehensive data about a project, including its configuration, associated workflows, and current status.
Add new jwks to project endpoint
Adds a new json web key set (jwks) to a specific endpoint of a project in the neon b2b saas integration platform. this endpoint is crucial for setting up secure authentication and authorization mechanisms, allowing seamless integration with
Add project email permission
Adds permissions for a specified email address to a particular project within the neon b2b saas integration platform. this endpoint is used to grant access or specific rights to users for a given project, enabling collaboration and controll
Add role to branch
Creates a new role within a specific branch of a project in the neon b2b saas integration platform. this endpoint allows for fine-grained access control by enabling the creation of custom roles at the branch level. it should be used when se
Create api key for organization
Creates a new api key for the specified organization, with optional project-specific access limitations. this endpoint is used to generate and manage api keys, which are essential for authenticating and authorizing access to neon's b2b saas
Create branch database
Creates a new database within a specified project and branch in the neon platform. this endpoint allows users to set up a new database with a custom name and assign an owner role, facilitating the organization and management of databases wi
Create compute endpoint
Creates a new compute endpoint for a specified branch within a neon project. this endpoint allows for detailed configuration of database resources, including read/write capabilities, regional placement, autoscaling limits, and connection po
Create new api key
Creates a new api key for accessing the neon b2b saas integration platform. this endpoint should be used when setting up new integrations, creating separate keys for different environments (e.g., production, testing), or rotating existing k
Create new project branch
Creates a new branch in a neon project with optional compute endpoints. this endpoint allows you to specify the parent branch, branch name, and various configuration options for both the branch and its compute endpoints. it can be used to c
Create project with quota and settings
Creates a new neon project with specified configuration settings. this endpoint allows you to set up a customized postgresql environment with various options for resource management, networking, and performance optimization. it's ideal for
Create vpc endpoint label
Updates the label of a specific vpc endpoint within a project in the neon b2b saas integration platform. this endpoint allows users to modify the identifier of an existing vpc endpoint, enhancing organization and management of network resou
Create vpc endpoint with label
Updates the label of a specific vpc endpoint within an organization's virtual private cloud (vpc) in a particular aws region. this endpoint allows you to change the descriptive name or identifier associated with a vpc endpoint, which can be
Delete api key by id
destructive
Deletes a specific api key from the neon platform. this endpoint should be used when you need to revoke access for a particular api key, such as when an employee leaves the organization or when you suspect the key has been compromised. the
Delete database from branch
destructive
Deletes a specific database from a designated branch within a project in the neon platform. this endpoint should be used when you need to permanently remove a database and all its associated data from a particular branch of a project. it's
Delete organization api key
destructive
Deletes a specific api key associated with an organization in the neon platform. this endpoint is used to revoke access for a particular api key, enhancing security by removing unused or compromised keys. it should be used when an api key i
Delete organization member
destructive
Removes a specific member from an organization within the neon b2b saas integration platform. this endpoint should be used when an organization administrator needs to revoke a user's membership, such as when an employee leaves the company o
Delete project branch by id
destructive
Deletes a specific branch within a project in the neon b2b saas integration platform. this endpoint permanently removes the specified branch and all associated data from the project. it should be used when a branch is no longer needed, such
Delete project branch role
destructive
Deletes a specific role from a branch within a project in the neon b2b saas integration platform. this endpoint is used to remove access permissions associated with a particular role in a specific project branch. it's particularly useful wh
Delete project by id
destructive
Deletes a specific project from the neon b2b saas integration platform. this endpoint permanently removes all data, configurations, and resources associated with the specified project. it should be used with caution, as the deletion process
Delete project endpoint
destructive
Deletes a specific endpoint within a neon project. this operation permanently removes the endpoint and all associated resources, such as configurations and access points. use this endpoint when you need to decommission or clean up unused en
Delete project jwks by id
destructive
Deletes a specific json web key set (jwks) associated with a given project in the neon b2b saas integration platform. this endpoint is used to remove outdated or unnecessary cryptographic keys from a project's key management system. it shou
Delete project permission
destructive
Deletes a specific permission associated with a project in the neon b2b saas integration platform. this endpoint is used to remove access rights or privileges from a project, which is crucial for maintaining proper access control and securi
Delete vpc endpoint by ids
destructive
Deletes a specific vpc endpoint within a given organization and region in the neon b2b saas integration platform. this endpoint should be used when you need to remove a vpc endpoint that is no longer required, perhaps due to changes in netw
Delete vpc endpoint by project id
destructive
Deletes a specific vpc endpoint within a designated project in the neon platform. this endpoint should be used when you need to remove a vpc endpoint that is no longer required or has become obsolete. the operation is irreversible, so it sh
Fetch database for branch
Retrieves a list of databases associated with a specific project and branch in the neon platform. this endpoint allows developers to view all databases within a particular project and branch context, which is useful for managing different e
Fetch organization members by id
Retrieves a list of all members associated with a specific organization in the neon b2b saas integration platform. this endpoint allows you to fetch detailed information about the users or entities that belong to the organization, which is
Fetch vpcendpoint details by id
Retrieves detailed information about a specific vpc endpoint within an organization's infrastructure in a particular aws region. this endpoint allows developers to access configuration details, status, and other relevant information about t
Get branches for project
Retrieves a list of branches associated with a specific project in the neon b2b saas integration platform. this endpoint should be used when you need to get an overview of all branches within a particular project, which is useful for versio
Get branch roles for project
Retrieves the roles associated with a specific branch within a project in the neon b2b saas integration platform. this endpoint is used to fetch the current role assignments for a given project and branch combination, which is essential for
Get consumption history projects
Retrieves the consumption history for specified projects within the neon platform. this endpoint allows users to fetch detailed metrics about resource usage over time, enabling effective monitoring and analysis of project-level consumption.
Get current user information
Retrieves the profile information for the currently authenticated user. this endpoint should be used when you need to access details about the user making the api request, such as their username, email, or other account-related information.
Get organization api keys
Retrieves a list of all api keys associated with a specific organization in the neon b2b saas integration platform. this endpoint is crucial for administrators to manage and monitor api access within their organization. it provides a compre
Get project branches
Retrieves detailed information about a specific branch within a neon project. this endpoint allows developers to fetch the current state and configuration of a branch, including its name, creation timestamp, and other relevant metadata. it'
Get project branch role
Retrieves detailed information about a specific role within a particular branch of a neon project. this endpoint is used to fetch the current configuration, permissions, and other relevant details associated with the specified role. it's pa
Get project connection uri
Retrieves the connection uri for a specified project within the neon b2b saas integration platform. this endpoint is crucial for establishing connectivity to a project's resources, enabling access to its data and functionalities. use this w
Get project endpoint information
Retrieves a list of all endpoints associated with a specific project in the neon b2b saas integration platform. this endpoint should be used when you need to obtain information about the available integration points or data connections with
Get project operation by id
Retrieves detailed information about a specific operation within a project in the neon b2b saas integration platform. this endpoint is used when you need to fetch the current status, details, or results of a particular operation that has be
Get schema for project branch
Retrieves the schema definition for a specific branch within a project in the neon b2b saas integration platform. this endpoint is crucial for developers and integrators who need to understand the data structure of a particular branch, enab
Get user organizations
Retrieves a list of organizations associated with the currently authenticated user in the neon platform. this endpoint allows users to view all the organizations they are a member of, providing essential information for managing multi-organ
Get vpc region endpoints
Retrieves a list of vpc endpoints for a specified organization within a particular aws region. this endpoint allows developers to obtain information about the virtual network interfaces that enable private communication between a vpc and su
List api keys
Retrieves a list of api keys associated with the authenticated user's neon account. this endpoint allows developers to view and manage their existing api keys, which are crucial for authentication when making requests to the neon api. it pr
List shared projects
Retrieves a list of shared projects accessible to the authenticated user within the neon b2b saas integration platform. this endpoint is used to fetch information about projects that have been shared across different parts of the organizati
Modify branch details in project
Updates the details of a specific branch within a project in the neon platform. this endpoint allows you to modify the name and protection status of an existing branch. it is particularly useful when you need to rename a branch or change it
Patch branch database information
Updates the properties of a specific database within a project branch in the neon platform. this endpoint allows for partial modifications of database attributes, such as changing its name or owner. it should be used when you need to rename
Reset role password for branch
Resets the password for a specific role within a project branch in the neon b2b saas integration platform. this endpoint is used to manage user access and security by allowing administrators to force a password reset for a particular role.
Restart project endpoint
Restarts a specific endpoint within a project in the neon b2b saas integration platform. this endpoint is used to reinitialize or reset the state of an integration endpoint, which can be helpful for applying configuration changes, clearing
Restore project branch
This endpoint restores a branch to a specific state or point in time. use it to recover data, revert changes, or create new branch states based on historical data. the restoration uses either a log sequence number (lsn) or timestamp from th
Retrieve account consumption history
Retrieves the consumption history for a specified account within the neon platform. this endpoint provides detailed information about resource usage and associated costs over a given time period. it's particularly useful for analyzing usage
Retrieve all regions
Retrieves a list of available geographic regions supported by the neon b2b saas integration platform. this endpoint provides crucial information about the different areas where the api is accessible and optimized for service delivery. it sh
Retrieve branch database details
Retrieves detailed information about a specific database within a neon project and branch. this endpoint allows developers to fetch crucial metadata and configuration details for a given database, enabling them to monitor and manage their d

Setup

Setup guide

11. Open your Switchy workspace and navigate to Settings → Integrations → Add MCP Server. 2. Select Neon from the catalog and click Connect. 3. In a new tab, log into your Neon console at console.neon.tech and go to Account Settings → API Keys. 4. Click Generate New Key, give it a descriptive name (e.g. 'Switchy Workspace'), and copy the key immediately — Neon shows it only once. 5. Paste the API key into Switchy's connection dialog and click Authorize. 6. Return to any Space in Switchy and type '@Neon list my projects' to confirm the connection works. 7. If you see project data, the integration is live; if you get an error, double-check the key wasn't truncated during paste. 8. To invoke a tool, @mention Neon in a message and describe what you need — the AI will map your request to the appropriate endpoint.

What teammates see: by default, memories from Neon are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List Active Projects

@Neon show me all active projects in our account, including their region and current compute status

Open in a Space →

Create Feature Branch DB

@Neon create a new database called 'feature_search_v2' on the 'dev' branch of project proj_abc123, owned by role 'app_user'

Open in a Space →

Add Teammate to Project

@Neon add permissions for engineer@example.com to project proj_abc123 so they can manage branches and endpoints

Open in a Space →

Generate Staging API Key

@Neon create a new API key for our organization, limited to project proj_staging456, named 'CI Pipeline Staging'

Open in a Space →

Inspect Compute Endpoint

@Neon get the full configuration for compute endpoint ep_xyz789, including region, autoscaling settings, and connection string

Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@neon list all active projects in our organization and show their current compute endpoint status

Output

Based on your Neon organization, here are 4 active projects: 1. **prod-api-db** (ID: proud-meadow-12345) — Compute endpoint running in us-east-1, autoscaling enabled (0.25-2 CU), currently active 2. **staging-analytics** (ID: quiet-forest-67890) — Compute endpoint suspended, last active 3 days ago 3. **dev-playground** (ID: bold-river-11223) — Compute endpoint running in eu-central-1, fixed 0.5 CU 4. **test-migrations** (ID: calm-lake-44556) — No compute endpoint configured This is an illustrative example showing typical project metadata and compute states your team might see.

Notes

This example demonstrates read-only project inspection, useful for infrastructure audits. Requires an API key with organization-level read permissions. The MCP retrieves live project configurations, so output reflects your current Neon account state—project names, regions, and compute settings will vary.

Prompt

@neon create a new branch called 'feature-user-auth' from our prod-api-db project's main branch, then set up a compute endpoint in us-west-2

Output

Branch **feature-user-auth** created successfully from **prod-api-db/main**. Compute endpoint provisioned: - Region: us-west-2 - Type: read_write - Autoscaling: 0.25–1 CU (default) - Status: Initializing (typically ready in 30-60 seconds) - Connection string: `postgres://user@ep-feature-user-auth-12345.us-west-2.aws.neon.tech/dbname` This is an illustrative example of the branch-and-compute workflow. Actual connection strings and endpoint IDs will differ.

Notes

This example shows Neon's core branching capability—creating isolated database environments from production snapshots. The MCP executes two write operations in sequence. Be aware: new branches consume storage quota, and compute endpoints incur usage charges when active. Requires API key with project-level write permissions.

Prompt

@neon review all database roles across our staging-analytics project branches and identify any roles with overly broad permissions that we should audit

Output

Analyzed 3 branches in **staging-analytics**: **Main branch:** - `admin_role` — Full superuser access (expected for ops) - `app_service` — Read/write on all tables - `readonly_analyst` — Read-only, scoped to `analytics` schema **Feature branches (2):** - `temp_migration_role` on **branch-schema-refactor** — Superuser access (⚠️ flag for review: typically unnecessary for feature work) - Standard roles inherited from main **Recommendation:** Audit `temp_migration_role` on the feature branch—superuser privileges may be broader than needed for schema testing. This is an illustrative synthesis combining role enumeration with security reasoning.

Notes

This example pairs the MCP's role-listing tools with the AI's ability to reason about security posture. Useful for compliance reviews or onboarding audits. The MCP fetches role metadata; the AI interprets it. Output depends on your actual role configurations—this example assumes a typical staging setup with mixed permission levels.

Use-case deep-dives

Multi-tenant SaaS database provisioning

When Neon MCP speeds up customer onboarding flows

A 6-person SaaS startup onboards 20-30 new customers a week, each needing an isolated Postgres database. The Neon MCP lets your onboarding agent create branches, spin up compute endpoints, and assign role permissions without your backend team writing custom provisioning scripts. The 50-tool surface covers the full lifecycle: branch creation, database setup, JWKS config for auth, and API key rotation. This works if your onboarding is conversational or ticket-driven and you trust the agent with project-level API keys. If you're provisioning hundreds of databases per hour or need sub-second latency, you'll hit rate limits and should stick to Neon's REST API directly. For teams onboarding at human scale, the MCP turns a 4-step Terraform workflow into a single agent prompt.

Developer environment spin-up

Why this MCP fits ephemeral staging setups

A 10-person engineering team runs feature branches in Neon, and developers ask for fresh staging databases 3-4 times a day. The Neon MCP gives your Slack bot or internal tooling agent the ability to create branches, configure compute endpoints, and grant email-based permissions on demand. The representative tools show strong coverage for branch-level operations and role management, which maps directly to the 'clone prod, give Alice access' pattern. This breaks down if your team is over 30 engineers or you're spinning up more than 50 environments a week—at that scale, the API key management and audit trail get messy. For small teams with bursty staging needs, the MCP removes the bottleneck of waiting on DevOps to provision a database.

Customer support database access

When Neon MCP handles support-tier permission grants

A 4-person support team fields 15-20 tickets a week where customers need temporary read access to their project's analytics database. The Neon MCP lets your support agent add email permissions, create read-only roles, and revoke access after 48 hours—all from a shared Switchy workspace. The 'add project email permission' and 'add role to branch' tools cover the exact scope support needs without handing out admin credentials. This works if your support volume is under 100 tickets a month and you're comfortable with API key-based auth. If you're a larger org with compliance requirements or need granular audit logs, the MCP's flat API key model won't meet your security bar. For small teams with straightforward access patterns, this turns a 10-minute Slack thread into a 30-second agent action.

Frequently asked

What does the Neon MCP let me do in Switchy?

It gives your AI agents direct control over Neon's serverless Postgres infrastructure. Agents can spin up databases, create branches, manage compute endpoints, configure JWKS for auth, and assign project permissions—all without leaving the chat. Think of it as letting your team provision and configure Neon resources conversationally instead of clicking through the console.

Do I need admin access to connect Neon to Switchy?

Yes. You'll need an API key with organization-level permissions to use most of the 50 tools. The MCP uses API_KEY auth, so whoever connects it should have rights to create projects, manage roles, and generate additional keys. If you only have project-scoped access, you'll hit permission errors on org-wide operations like creating new API keys.

Can the Neon MCP run SQL queries against my databases?

No. This integration manages Neon's control plane—projects, branches, endpoints, roles—not the data plane. If you need to query tables or run migrations, use Neon's connection string with a separate Postgres MCP or the native psql tooling. This MCP is for infrastructure provisioning, not data access.

Why use this instead of the Neon console or CLI?

Speed and context. An agent can create a branch, provision a compute endpoint, and assign permissions in one conversational turn—no context-switching between docs, CLI flags, and the web UI. It's faster for exploratory work or repetitive setup tasks. For one-off changes or visual confirmation, the console is still easier.

Who on my team should connect the Neon integration?

Your infrastructure lead or whoever manages database provisioning. They'll need to generate and store the API key securely. Once connected, any Switchy user in your workspace can ask agents to create branches or endpoints, so set clear guardrails if you don't want junior devs spinning up production compute by accident.