pa-code-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Server mode: 'readonly' (default) or 'readwrite' | readonly |
| TM1_USER | Yes | TM1 username | |
| TM1_BASE_URL | Yes | Base URL of the TM1 / Planning Analytics server (e.g., https://host:port) | |
| TM1_PASSWORD | Yes | TM1 password | |
| TM1_AUTH_MODE | Yes | Authentication mode: 'basic', 'cam', or 'apikey' | |
| MCP_HTTP_TOKEN | No | Bearer token required for the HTTP MCP transport | |
| TM1_CAM_NAMESPACE | No | CAM namespace (required when TM1_AUTH_MODE is 'cam') | |
| TM1_SSL_REJECT_UNAUTHORIZED | No | Set to 'false' to disable TLS validation (dev only) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tm1_list_cubesC | List cubes. |
| tm1_list_dimensionsC | List dimensions. |
| tm1_list_processesB | List TI processes. |
| tm1_get_cube_dimensionsC | Ordered dimensions of a cube. |
| tm1_get_cube_rulesC | Rules text of a cube. |
| tm1_get_process_codeC | Full source of a TI process. |
| tm1_list_dimension_elementsB | List elements of a dimension hierarchy (capped). |
| tm1_list_hierarchiesB | List hierarchies of a dimension. |
| tm1_list_viewsA | List views on a cube. |
| tm1_list_subsetsC | List subsets of a dimension. |
| tm1_execute_mdxA | Run a read-only MDX query (capped). |
| tm1_get_cube_gridA | Build a rows × columns value grid for an editable data-entry table. Returns JSON (rows, columns, values, updateable) that maps each cell back to a write tuple. |
| tm1_get_server_infoA | Static server configuration. |
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 13 tools
Each tool maps to a distinct TM1 object or action: list_* enumerates resources, get_* retrieves specific detail, and execute_mdx/get_cube_grid cover querying versus grid-building. There is no meaningful overlap between tools.
All tools follow the consistent tm1_<verb>_<object> pattern. List is used for collection enumeration, get for detail retrieval, and execute for running a query, so the verb choice is predictable and uniform.
Thirteen tools is well within the ideal range for a domain-specific server. Each tool covers a meaningful part of browsing and querying a TM1 environment without unnecessary redundancy.
The read/exploration surface is strong: cubes, dimensions, hierarchies, processes, rules, MDX, and grid data are all covered. However, there are no write/update or process-execution tools, and the updateable grid has no corresponding save/commit tool, which is a notable gap for typical TM1 workflows.