palace-tools
Related Servers
Alternatives to palace-tools
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables an MCP client to drive CST Studio Suite 2026 through its official Python automation API, covering 3D modelling, materials, ports, boundaries, mesh and solver configuration, solver runs, and result reading. Also provides verification and export tools — S11, reference impedance, port diagnostics, energy budget and model audit — plus Touchstone/ASCII/JSON evidence output and parameter sweeps, all locally over stdio.844MIT
- AlicenseNot gradedqualityBmaintenanceExposes 21 civ_* tools over a zero-dependency JSON-RPC stdio layer so AI agents can create worlds, open deterministic simulation sessions, advance turns, inspect chronicles/states, export, and replay-verify results. It also enables AI monarch rounds, DM/petty-event adjudication, configurable and tile-level field plugins, and a local browser viewer for maps, decisions, and logs.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run three-stage drone logistics site selection, load CSV/Excel data, retrieve domain knowledge, reverse-geocode coordinates, and receive progress heartbeats for long-running tasks over stdio JSON-RPC.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables MCP-compatible clients such as Claude Desktop, Cursor, and Antigravity to invoke deterministic mathematical modeling and System 2 agent capabilities through a native STDIO JSON-RPC 2.0 server with zero external dependencies.MIT

specmd-mcpofficial
AlicenseCqualityBmaintenanceEnables authoring, validating, inspecting, blackbox-inventorying, tracing, and capability-querying SPEC.md documents through MCP tools over stdio JSON-RPC. Each tool wraps the same command modules the CLI uses and returns identical JSON envelopes.9Apache 2.0- AlicenseNot gradedqualityBmaintenanceExposes 14 tools that let an agent query charter clauses, route and execute an 8-stage collaboration pipeline, arbitrate conflicts with cited clause IDs, enforce safety gates, run receipt self-checks, deposit and recall memory, solve symbolic anchoring constraints, and mine a 330-entry knowledge base plus semantic-field analysis. It also diagnoses image-generation prompts against a formal feature-cluster grammar, all over a zero-dependency stdio JSON-RPC interface.1MIT
TDQS
Scored across 13 tools
Tools mostly target distinct actions (build, lint, mesh, run, results), so selection is usually clear. However, palace_lint_rules and palace_gotchas overlap in content because gotchas includes lint rules plus workflow lessons, which could cause confusion about which to call.
All tools use consistent snake_case with a palace_ prefix and a predictable verb_noun pattern (e.g., palace_build_config, palace_lint_config, palace_mesh_report). Naming is highly coherent and easy to infer.
The 13 tools map cleanly onto the multi-step Palace workflow—config creation, linting, meshing, running, result summary, cost estimation, status, and sanity checks. Each tool appears to earn its place without obvious redundancy.
Core lifecycle coverage from config building through meshing, running, and result summarization is strong, with diagnostic and check tools rounding out the set. Minor gaps exist in case/folder management (e.g., listing, deleting, or comparing runs), but these are workaround-able.