pa-code-mcp-server
Related Servers
Alternatives to pa-code-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that connects AI assistants to Anaplan's Integration API v2, enabling users to browse workspaces, manage model data, and execute bulk operations like imports and exports. It provides 25 structured tools to navigate model hierarchies and perform transactional tasks through natural language.707MIT
- FlicenseAqualityBmaintenanceEnables LLM clients to interact with IBM MQ by exposing management and messaging REST APIs as 15 MCP tools, covering queue manager queries, MQSC commands, object inspection, and message send/receive operations.15-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with IBM OpenPages GRC platform through a standardized MCP interface, supporting both remote HTTP and local stdio modes.-
- FlicenseNot gradedqualityCmaintenanceEnables an LLM to dynamically discover and call tools across multiple MCP servers (file, GitHub, SQL, Python execution) with authentication, rate limiting, and observability, supporting parallel execution and secure deployment.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to read and modify Mendix application models through MCP tools for creating modules, entities, pages, microflows, deploying, and querying runtime data.1-
- AlicenseCqualityBmaintenanceMCP server for IBM Concert Operate that exposes the full v2 REST API as callable tools, enabling AI assistants to manage alerts, incidents, policies, runbooks, and more.975 npm1MIT
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.