← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionUI-TARS Filesystem MCP ServerRestricted filesystem access for MCPSafe Docx MCP ServerAI-native surgical editing of Word and OpenDocument files with formatting preservation
FMRS46 / 100 · D68 / 100 · C
Reliability8 / 208 / 20
Security and permissions8 / 2016 / 20
Maintenance13 / 2014 / 20
Documentation7 / 2018 / 20
Setup experience10 / 2012 / 20
Best for
  • MCP clients that need controlled local file access
  • Developers who want to explicitly constrain filesystem operations
  • Developers who need precise, format-preserving edits to .docx/.odt files via coding agents
  • Workflows that require tracked-changes output for human review
Not for
  • Workflows that require access to unauthorized directories
  • Users seeking a server with documented tool names or broader capabilities
  • Visual editing scenarios needing browser rendering, real-time collaboration, or pixel-level pagination guarantees
  • Using .dotx templates directly (they must be converted to .docx first)
Required permissions
  • The server needs file-operation access to the directories listed in allowed-directories
  • SSE and Streamable HTTP modes require use of the configured local port
  • Filesystem access to read and write local .docx / .odt documents
Risks and side effects
  • An overly broad allowed-directories value may expand the scope of local files that can be exposed or modified
  • When using a local SSE or HTTP endpoint, port and access-scope configuration should be reviewed
  • The source does not specify individual filesystem tools, authentication, or authorization mechanisms
  • Edits apply to local files; incorrect targeted changes could overwrite original content — use the clean/tracked-changes dual output for review
  • The project is not a visual editor or layout engine, so complex layout results should be verified manually
Supported clients
Tools00