F
licenseNot graded
qualityD
maintenanceEnables file system operations, web scraping, and AI-powered search through MCP tools for use by LLM agents.
1
-
rigid-pipeline-mcp
by jansc4
Related Servers
Alternatives to rigid-pipeline-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables users to access local files, manage persistent notes via CRUD, fetch URLs, inspect system information, and analyze or transform text through MCP tools.11-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.-
- AlicenseNot gradedqualityDmaintenanceProvides a set of MCP tools to let AI assistants like Claude, Cursor, and VS Code Copilot interact with SQLite databases, supporting querying, schema management, and data import/export.17 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables PostgreSQL querying and schema retrieval, NLP/LLM intent classification and SQL generation, tool-intent resolution, and file listing through MCP tools.-
- AlicenseAqualityDmaintenanceProvides LLMs with local filesystem operations (read/write files, list directories) and command execution via MCP, enabling file management and task automation within AI clients.714 npmISC
TDQS
A4/5.0
Scored across 14 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, and the domain prefixes (files_, db_, llm_, fs_, meta_) make separation immediate. Even the closely paired preview/execute file operations are unambiguous, and read_file vs get_metadata vs analyze_folder are clearly delineated.
Naming Consistency4/5
Names mostly follow a predictable prefix + verb_noun pattern and are consistently snake_case. Minor deviations like db_schema, files_file_hash, and run_pipeline (no prefix) break the pattern slightly, but the overall convention remains readable and navigable.
Tool Count5/5
14 tools is well within the ideal range, and each tool earns its place by covering a distinct operation: file I/O, file operations, DB access, LLM prompting, metadata, folder analysis, and pipeline orchestration. The count feels proportionate to the server's broad but coherent scope.
Completeness4/5
The core pipeline lifecycle is well covered: producing items, processing them with LLM/DB/files, and orchestrating for_each steps. Minor gaps exist, such as no file copy operation and no multi-statement transaction support in db_execute, but agents can work around these without major dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues