302AI File Parser MCP Server
Related Servers
Alternatives to 302AI File Parser MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Claude Desktop with persistent task management, file operations, document generation, and PDF indexing.221 npm1MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Claude Desktop that connects to 302AI's API services, allowing users to integrate and leverage 302AI capabilities through a structured communication interface.915 npm21MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that bypasses Claude's context by routing file processing to local or cloud AI, saving token costs. It reads files from disk and returns distilled results without Claude seeing the raw content.1-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets you switch between different MCP configuration profiles directly from inside Claude Desktop.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables Claude Desktop to search and read local documents via full-text and fuzzy search, providing direct access to indexed files without chunking.MIT
- FlicenseBqualityDmaintenanceAn MCP server that provides tools for searching and analyzing Claude Code conversation history.84-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the sole operation available.
The single tool name follows a clear verb_noun pattern (parseFileToText), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is generally too few for a server named 'File Parser', as this suggests a domain that might include operations like parsing different file types, handling errors, or extracting metadata. The scope feels incomplete with just one basic parsing function.
The server's name implies a broader file parsing capability, but the tool set only includes parsing files to text. Obvious gaps include support for different file formats (e.g., PDF, DOCX), structured data extraction, or error handling, making the surface severely incomplete for the apparent purpose.