Tibero MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLASSPATH | Yes | The path to the Tibero JDBC driver (tibero6-jdbc.jar) | |
| TIBERO_SID | No | The SID (System Identifier) of the Tibero database | tibero |
| TIBERO_HOST | No | The hostname of the Tibero database server | localhost |
| TIBERO_PORT | No | The port number of the Tibero database server | 8629 |
| TIBERO_USER | Yes | The username for connecting to the Tibero database | |
| TIBERO_PASSWORD | Yes | The password for connecting to the Tibero database |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sqlC | Execute an SQL query on the Tibero server |
| get_table_infoC | Get detailed information about a table |
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 2 tools
The two tools have clearly distinct purposes: execute_sql handles arbitrary SQL queries, while get_table_info provides metadata about a specific table. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (execute_sql and get_table_info). The naming is predictable and readable throughout the set.
With only 2 tools, the server feels thin for a database interaction domain. Core operations like listing tables, describing schemas, or managing connections are missing, making it under-scoped for typical database workflows.
The tool surface is severely incomplete for a Tibero database server. It lacks basic CRUD lifecycle coverage (e.g., no tools for listing databases/tables, creating/dropping tables, or managing transactions), which will cause significant agent failures in database tasks.