A
licenseNot graded
qualityD
maintenanceEnables natural language interaction with the Labguru laboratory management system, providing 63 tools across experiments, protocols, inventory, and more.
MIT
eLabFTW MCP
Related Servers
Alternatives to eLabFTW MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to LabArchives electronic lab notebooks, enabling querying, semantic search, page navigation, and file uploads with provenance tracking.6MIT
- FlicenseNot gradedqualityBmaintenanceExposes SciNote ELN bench workflows as MCP tools so an AI assistant can drive them by voice or chat, including ticking checklist items, completing steps, consuming inventory stock, and adding result notes through the SciNote REST API with the user's own credentials.-
Elnora MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceConnects AI agents to the Elnora bioprotocol optimization platform, enabling generation, management, and optimization of wet-lab protocols through natural language.210 npm3Apache 2.0- AlicenseAqualityCmaintenanceConnects to wetlab protocol resources such as protocols.io, enabling users to access and manage experimental protocols via natural language.22Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Edison Scientific platform's AI agents for scientific research, chemistry, and literature search, supporting tasks like synthesis planning, literature reviews, and data analysis.5MIT
TDQS
A3.5/5.0
Scored across 41 tools
Disambiguation4/5
Most tools target a distinct resource+action and descriptions clarify boundaries well. However, the link family (ensure_link, ensure_link_by_query, bulk_ensure_links, delete_link, bulk_delete_links) and the info family (get_connection_info, get_current_user_capabilities, refresh_team_caps) have overlapping purposes that could cause misselection, and resolve_entity_by_query overlaps with the list_* searches.
Naming Consistency4/5
The dominant pattern is consistent verb_noun snake_case (get_item, list_experiments, create_experiment, update_step, delete_link, bulk_ensure_links). A few names deviate slightly (review_experiment, refresh_team_caps, expand_links_network) but remain readable and predictable.
Tool Count2/5
41 tools is heavy for a single MCP server and pushes well past the comfortable 3-15 range. While the eLabFTW domain is broad, the count is high enough to burden tool selection and discovery.
Completeness3/5
Strong read/link/step/update coverage, but notable lifecycle gaps: no delete for experiments, items, uploads, templates, or metadata. Read+create+update are covered while destructive/cleanup operations are largely absent, and there is no direct tag-list or item-type management.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive