A
licenseA
qualityA
maintenanceEnables LLM clients to read batches, recipes, fermentation readings, and inventory, and to perform routine writes such as updating batch status, logging measurements, and adjusting stock.
13
46 PyPI
MIT
Tulip MCP Server
Officialby tulip
Related Servers
Alternatives to Tulip MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables agentic LLMs to interact with the Rapid Platform API, supporting list operations, CRUD items, and webhook creation.-
- FlicenseNot gradedqualityFmaintenanceEnables LLMs to access Jenkins job data, trigger builds, and manage Jenkins tasks through a standardized interface.5-
- AlicenseNot gradedqualityCmaintenanceProvides read and write access to Airtable databases, enabling LLMs to inspect schemas, search, create, update, and delete records, tables, and fields, as well as manage comments on records.2,607 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to programmatically control n8n via natural language for automated workflow creation, modification, and execution management.1-
- FlicenseAqualityBmaintenanceEnables an LLM to read and write NetBox data through its REST API, supporting listing endpoints, inspecting schemas, and creating, updating, or deleting objects.7-
TDQS
A3.7/5.0
Scored across 30 tools
Disambiguation5/5
Every tool has a clearly distinct purpose targeting specific resources and actions. Tools are organized by domain (tables, stations, users, machines) with no overlapping functionality - for example, getTableRecord retrieves a single record while listTableRecords retrieves multiple, and countTableRecords provides a count. The descriptions clearly differentiate each tool's scope.
Naming Consistency5/5
The naming follows a consistent verb_noun pattern throughout all 30 tools. All tools use camelCase with clear action prefixes (get, list, count, run, retrieve) followed by specific resource names. This creates a predictable and readable naming convention across the entire toolset.
Tool Count3/5
With 30 tools, this is borderline heavy for an MCP server. While the tools cover multiple domains comprehensively, the count approaches the upper limit of what's typically manageable. The server covers tables, stations, users, and machines, but 30 tools might be overwhelming compared to more focused servers with 10-15 tools.
Completeness2/5
The tool surface is severely incomplete as all tools are read-only operations. There are no create, update, or delete operations for any resources, creating significant gaps that will cause agent failures when trying to perform full lifecycle management. While the read operations are comprehensive within their scope, the lack of write capabilities represents a major limitation.
Maintenance
ActivityMaintained
ResponsivenessNo issues