Amazon Neptune MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_PROFILE | No | The AWS profile to use for credentials as configured in the AWS CLI. | |
| NEPTUNE_ENDPOINT | Yes | The Amazon Neptune endpoint. For Neptune Database use 'neptune-db://<Cluster Endpoint>'. For Neptune Analytics use 'neptune-graph://<graph identifier>'. | |
| FASTMCP_LOG_LEVEL | No | The log level for the FastMCP server (e.g., INFO, DEBUG). | INFO |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_graph_statusB | Get the status of the currently configured Amazon Neptune graph. |
| get_graph_schemaB | Get the schema for the graph including the vertex and edge labels as well as the (vertex)-[edge]->(vertex) combinations. |
| run_opencypher_queryC | Executes the provided openCypher against the graph. |
| run_gremlin_queryC | Executes the provided Tinkerpop Gremlin against the graph. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GraphStatus | |
| GraphSchema |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_graph_schema retrieves schema information, get_graph_status checks system status, run_gremlin_query executes Gremlin queries, and run_opencypher_query executes openCypher queries. The descriptions make it unambiguous which tool to use for each type of operation.
All tools follow a consistent verb_noun pattern with snake_case: get_graph_schema, get_graph_status, run_gremlin_query, and run_opencypher_query. The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for a graph database server, covering schema, status, and query execution. It might be slightly thin for advanced operations like data manipulation or monitoring, but it's well-scoped for core functionality.
The tools cover schema retrieval, status checks, and query execution for two query languages (Gremlin and openCypher), which is good for basic operations. However, there are notable gaps: no tools for creating/updating/deleting data, managing configurations, or handling transactions, which could limit agent workflows in a database context.