A
licenseNot graded
qualityD
maintenanceMCP Server for interacting with the Langflow API via a natural language interface. It exposes Langflow functionalities as tools for LLMs.
MIT
@lamatic/mcp
Officialby Lamatic
Related Servers
Alternatives to @lamatic/mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server that initializes, manages, and operates traceable agentic infrastructure across your digital ecosystem, serving as a control plane to know project states, health, and initialize missing setups.371MIT
- AlicenseBqualityBmaintenanceMCP server wrapping Backstage — query service catalog, fetch TechDocs, and scaffold services via AI agents.7Apache 2.0
- AlicenseAqualityCmaintenanceUniversal MCP knowledge server for LLM agents, powered by local RAG, providing domain-specific best practices and playbooks across software engineering, marketing, video editing, and other knowledge areas.3MIT
- FlicenseNot gradedqualityCmaintenanceMulti-model agent orchestration MCP server that enables plan-code-review-deliver pipelines with configurable providers and models.-
- AlicenseNot gradedqualityCmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.1 npmMIT
TDQS
B3/5.0
Scored across 44 tools
Disambiguation4/5
Most tools have clearly distinct purposes, but there is direct overlap between dev_get_flows and dev_list_all_flows, which both list flows. The three auth_login tools are also similar in name though they authenticate different contexts.
Naming Consistency4/5
Tools consistently use prefix_category + verb_noun in snake_case. However, the duplicate dev_get_flows and dev_list_all_flows break the naming pattern, and some verbs are inconsistent (e.g., 'get' vs 'list' for similar operations).
Tool Count2/5
44 tools is excessive for a single MCP server, covering too many subdomains (dev, docs, graph, kit). This high count suggests the server could be split into smaller, more focused servers.
Completeness4/5
The tool surface covers most CRUD operations for projects, flows, contexts, credentials, and deployments. Minor gaps exist, such as missing update for contexts and delete for deployments, but overall it is fairly complete for the domain.
Maintenance
ActivityInactive
ResponsivenessNo issues