fscp-mcp
Related Servers
Alternatives to fscp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for full lifecycle of 1C binary files (CF/CFE/EPF/ERF) without EDT import: unpack to a temporary directory, read and edit code/forms/help, search, diff, repack, and cleanup. Enables code analysis, patching, and bytecode decompilation of protected modules via natural language.205MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that provides tools for working with 7-Zip archives, enabling archive creation, extraction, item management, and file system operations through a standardized interface.MIT
- FlicenseAqualityAmaintenanceProvides read-only analysis of Mitsubishi GX Works3 PLC projects via MCP, enabling device tracing, cross-referencing, ladder inspection, linting, and report generation without modifying source projects.41552 PyPI6-
- AlicenseAqualityDmaintenanceMCP server that enables searching and reading binary document files (PDF, DOCX, PPTX, XLSX, ODT, ODS, ODP, RTF, EPUB) using regex patterns and retrieving content by sections.2MIT
- AlicenseDqualityDmaintenanceEnables reading, writing, editing, and converting Office documents (ODT, DOCX, ODS, XLSX, PDF, etc.) using MCP tools, with no external dependencies.1132 npmMIT
- AlicenseNot gradedqualityBmaintenanceA local filesystem MCP server providing constrained file operations (read/write, directory management, search, metadata) within configurable directories, with read-only mode and zero runtime dependencies.3 npmMIT
TDQS
Scored across 38 tools
Each tool has a distinct purpose: archive operations (fscp_*), device CRUD, object management, plan editing, logic clauses, and utilities. Even similar actions like remove_plan vs remove_placement vs remove_device are clearly separated by resource type. No two tools appear to do the same thing.
Most tools follow a verb_noun pattern (list_devices, add_device, set_device, remove_device). However, there are deviations: the fscp_ prefix for archive operations (fscp_create, fscp_open, fscp_save) vs. plain add_/set_ for entities, plus a few unique names (device_tree, resolve_uid, read_xml). While readable, the mixed conventions prevent a perfect score.
38 tools exceeds the 25+ threshold for 'too many'. The server covers a broad domain (devices, objects, plans, logic, archives), but the sheer number may overwhelm an agent, and some tools could be consolidated (e.g., plan image tools). The count feels excessive for typical MCP servers, even with this scope.
The surface covers the main lifecycle: create/read/update/delete for devices, objects, and plans, plus logic management and archive operations. There are minor gaps—no raw XML write capability (only read_xml as fallback), no editing of SecurityConfiguration, and no bulk import beyond CSV export—but these are workable or intentional shortcuts.