innoslate-mcp
Related Servers
Alternatives to innoslate-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets AI assistants control your real Chrome browser to perform web tasks like reading pages, taking screenshots, clicking, and typing, using your existing logged-in sessions.132MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to control and automate your Chrome browser directly, leveraging existing login states and configurations for tasks like content analysis, semantic search across tabs, screenshots, network monitoring, and interactive operations.12MIT
- AlicenseAqualityBmaintenanceEnables an AI assistant to read and control your real, logged-in Safari browser tabs, with a local model gating every write action for safety.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables a browser-based AI assistant to read code, edit files, run tests, inspect failures, and keep task checkpoints on a local project.22 npmMIT
- AlicenseNot gradedqualityDmaintenanceTransforms Chrome browser into an AI-controlled automation tool that allows AI assistants like Claude to access browser functionality, enabling complex automation, content analysis, and semantic search while preserving your existing browser environment.MIT
- FlicenseNot gradedqualityDmaintenanceUnlimited, session-authenticated web search and fetch for AI tools using your own browser. Supports authenticated/paywalled pages without API keys.-
TDQS
Scored across 18 tools
Most tools have clearly distinct purposes (search vs. get, local files vs. workspace files, schema vs. survey). The main potential confusion is innoslate_apply (bulk create/update) versus innoslate_update (single entity by id), though the descriptions distinguish them well.
Nearly all tools use a consistent innoslate_ prefix with readable verb/noun forms. The two local-file tools (list_local_files, read_local_file) drop the prefix, a minor but noticeable deviation from the otherwise consistent convention.
18 tools is on the heavier side but each maps to a distinct capability (auth, survey, read, search, write, lint, quality, report). The set is well-scoped for a full project-management workflow rather than padded.
The surface covers the full lifecycle: login/status, project survey, schema discovery, search/read, document trees, comments, lint, quality check, reports, file attachment, and verified bulk/single writes. Deletion is intentionally excluded, but no meaningful read or write operation appears to be missing.