Neon Enterprise MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEON_API_KEY | Yes | Your Neon Enterprise Gateway API key (mcp_live_...). Obtain by purchasing at https://neoninnovationlab.com/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryB | Execute a read-only query against the remote Neon database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another tool. The purpose of execute_query is clear and unambiguous within the tool set.
The single tool uses a clear verb_noun pattern. Although there is only one tool to judge, the naming style is predictable and conventional for a database query operation.
A single tool feels far too thin for a database gateway MCP server, even if it is intentionally read-only. The apparend scope of Neon Enterprise MCP Gateway implies more useful surface area than one query endpoint.
The server provides only read-only querying with no schema discovery, table listing, query planning, or write operations. Agents are left with a very limited surface that will be insufficient for most practical database workflows.