How flamey3t1/tm1-mcp-server works
This is an MCP server that lets an MCP-compatible client inspect and manage an IBM Planning Analytics/TM1 model. The principal workflow is a client tool request, registered by the server, handled by a domain tool, and executed through the TM1 client against the server; read-only MCP resources and workflow prompts provide alternate entry points. Separate tool domains cover model structure, data, TI processes and operations, while analysis tools add code-graph and model-audit capabilities. The map follows documented capabilities; several tool-to-service details are inferred only at the documented category level because their source was not sampled.
Main entry points: tools TM1 tools · index.ts Server entry · analysis Analysis tools · tm1-client.ts TM1 client
Components 23
MCP interface
- Server entry
src/index.ts - HTTP transport
src/http-transport.ts - Tool registry
src/tools/index.ts - TM1 tools
src/tools - Read resources
src/resources/index.ts - Workflow prompts
src/prompts/index.ts
TM1 access
- TM1 client
src/tm1-client.ts - Session manager
src/session-manager.ts - REST dispatcher
src/tm1-client/dispatcher.ts - Domain services
src/tm1-client/services
Model lifecycle
- Metadata and dimensions
src/tools/metadata - Cubes and subsets
src/tools/model-building - Cell and view tools
src/tools/celldata - TI development
src/tools/ti-development - Chore scheduling
src/tools/scheduling - Security tools
src/tools/security - Operations and files
src/tools/operations
Analysis and audits
- Analysis tools
src/tools/analysis - Code graph and metrics
src/lib/callgraph - Feeder analysis
src/lib/feeders - Complexity analysis
src/lib/complexity
Other components
- MCP client
- TM1 server
Connections 25
- MCP client → Server entry: stdio requests
- Server entry → HTTP transport: starts HTTP
- MCP client → HTTP transport: HTTP requests
- Server entry → Tool registry: registers tools
- Tool registry → TM1 tools: registers
- Server entry → Read resources: registers resources
- Server entry → Workflow prompts: registers prompts
- TM1 tools → TM1 client: handles TM1 calls
- Read resources → TM1 client: reads TM1
- TM1 client → Session manager: authenticates
- TM1 client → Domain services: uses services
- Session manager → REST dispatcher: sends auth requests
- Domain services → REST dispatcher: sends REST requests
- REST dispatcher → TM1 server: REST traffic
- Metadata and dimensions → TM1 tools: registered by
- Cubes and subsets → TM1 tools: registered by
- Cell and view tools → TM1 tools: registered by
- TI development → TM1 tools: registered by
- Chore scheduling → TM1 tools: registered by
- Security tools → TM1 tools: registered by
- Operations and files → TM1 tools: registered by
- Analysis tools → TM1 tools: registered by
- Analysis tools → Code graph and metrics: analyzes code
- Analysis tools → Feeder analysis: checks feeders
- Analysis tools → Complexity analysis: audits complexity