Centia MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_TOKEN | No | Static personal access token. Bypasses the stored gc2-cli session. | |
| API_BASE_URL | No | Base URL for the Centia API. Default: https://api.centia.io |
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 |
|---|---|
| postCallB | Call a JSON-RPC method. The method must exist (see /api/v4/methods). |
| postCallDryA | Dry-run an RPC call to infer and store input/output types. Dry-runs do not modify the database. Run this before requesting TypeScript types from /api/v4/interfaces. |
| getClientB | Get OAuth client(s). |
| deleteClientC | Delete OAuth client(s). |
| patchClientC | Update existing OAuth client(s). |
| postClientB | Create new OAuth client(s). |
| getColumnC | Get column(s). |
| deleteColumnC | Delete column(s). |
| postColumnC | Create new column(s). |
| patchColumnB | Update existing column(s). |
| postCommitB | Commit schema changes to Git and push to the remote repository. |
| getConstraintC | Get constraint(s). |
| deleteConstraintC | Delete constraint(s). |
| postConstraintC | Create constraint(s). |
| getEventsB | Check if event trigger is enabled. |
| postEventsC | Install event trigger. |
| postFileUploadC | Upload file(s) via multipart/form-data and stage them on the server. |
| postFileProcessA | Import a staged file into a target schema/table. Supports dry-run, append, SRS, and more. |
| getRuleC | Get rule(s). |
| deleteRuleB | Delete rule(s). |
| patchRuleC | Update existing rule(s). |
| postRuleD | Create rule(s). |
| postGraphQLC | Run a GraphQL query or mutation. |
| getIndexC | Get index(es). |
| deleteIndexD | Delete index(es). |
| postIndexC | Create index(es). |
| getMetaDataC | Get relation metadata |
| patchMetaDataC | Update relation metadata |
| getRpcB | Get JSON-RPC method definitions. |
| deleteRpcB | Delete JSON-RPC method(s). |
| patchRpcB | Update existing JSON-RPC method definitions. |
| postRpcB | Create JSON-RPC method definitions. |
| postOauthC | Create token. |
| postDeviceC | Start device flow. |
| getPrivilegesC | Get privileges. |
| patchPrivilegesC | Update privileges. |
| getTypeScriptA | Get TypeScript interfaces for RPC methods inferred from /api/v4/call/dry. |
| getSchemaC | Get schema(s). |
| deleteSchemaC | Delete schema(s). |
| patchSchemaB | Rename an existing schema. |
| postSchemaD | Create schema(s). |
| getSequenceC | Get sequence(s). |
| deleteSequenceC | Delete sequence(s). |
| patchSequenceC | Update existing sequence(s). |
| postSequenceD | Create sequence(s). |
| postSqlB | Execute SQL statements. |
| postSqlNoTokenB | Run SQL statements without a token. |
| getStatsC | Get database statistics. |
| getTableC | Get table(s). |
| deleteTableC | Delete table(s). |
| patchTableA | Rename or move existing table(s). |
| postTableC | Create table(s). |
| getUserC | Get sub-user(s). |
| deleteUsersC | Delete sub-user(s). |
| patchUserC | Update existing sub-user(s). |
| postUserB | Create new sub-user(s). |
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 56 tools
Every tool name uniquely pairs a verb (delete, get, patch, post) with a resource (client, column, etc.), leaving no ambiguity. Even with 56 tools, each combination is distinct and clearly indicates the resource and action.
All tool names follow a strict verb_noun pattern using PascalCase and HTTP verbs (delete, get, patch, post). This consistency makes the tool set predictable and easy to navigate.
With 56 tools, the count far exceeds the recommended range (3-15). While the domain may require many operations, this volume is likely to overwhelm agents and suggests an overly broad scope.
The tool set covers CRUD for most major resources (tables, schemas, columns, etc.) and includes file handling, SQL, GraphQL, and OAuth. Minor gaps exist (e.g., no delete for events or devices), but the core database operations are well-covered.