Data Nexus MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_REST_API_URL | Yes | The base URL of the Data Nexus REST API (e.g., http://localhost:8000) | |
| MCP_REST_API_USER | No | Username for basic or OAuth2 authentication (used with MCP_REST_API_PASSWORD) | |
| MCP_REST_API_TOKEN | No | Bearer token for OAuth2 authentication (alternative to username/password) | |
| MCP_REST_API_PASSWORD | No | Password for basic or OAuth2 authentication (used with MCP_REST_API_USER) |
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 |
|---|---|
| query_databaseD | Run a parameterized query on a named database connection. |
| get_schemaC | Retrieve schema information for a named database connection. |
| list_tablesC | List all tables or collections in a named database connection. |
| describe_tableA | Describe the structure of a specific table or collection. |
| execute_sqlB | Execute raw SQL or native database command on a named connection. |
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 5 tools
Tools are mostly distinct: query_database and execute_sql both run queries but one is parameterized and the other raw; get_schema, list_tables, describe_table each target different metadata. Minor potential for confusion between the two query tools, but descriptions clarify the difference.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: query_database, get_schema, list_tables, describe_table, execute_sql. No mixed conventions or irregularities.
5 tools are well-scoped for a database MCP server. The set covers core operations—querying, schema retrieval, table listing, structure description, raw execution—without being overwhelming or too sparse.
The tool surface covers essential query and schema exploration operations. The execute_sql tool can handle DDL, but there are no dedicated create/alter/drop tools; transaction commands are also missing. Overall, it's nearly complete for a typical read-heavy interaction pattern.