Tealfabric MCP Server for Cursor
OfficialRelated Servers
Alternatives to Tealfabric MCP Server for Cursor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables managing and deploying apps to your cloud directly from Cursor through natural language, including environment management, job monitoring, and approval workflows.1MIT
- FlicenseNot gradedqualityFmaintenanceEnables interaction with Azure DevOps through natural language in Cursor IDE. Supports work item management, pull requests, builds, releases, test management, and guided workflows for development teams, QA testers, and release management.1-
- AlicenseNot gradedqualityDmaintenanceConnects Fledge functionality to Cursor AI, allowing interaction with Fledge instances via natural language commands.MIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to manage Genesys Cloud Function Data Actions through natural language in Cursor, including validating, building, planning, and applying function deployments while enforcing safety controls like plan-before-apply and read-only mode.2MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with Azure DevOps through Cursor chat, providing tools to manage builds, pipelines, work items, sprints, and board operations. Supports secure authentication via Personal Access Tokens and allows natural language-driven DevOps task management.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of TeamCity CI/CD operations through natural language commands, including builds, projects, tests, artifacts, and more.21 npmMIT
TDQS
Scored across 37 tools
Most tools target a distinct resource+action across five clear domains (connectors, integrations, webapps, processes, documents), and delete vs retire process is explicitly differentiated. However, tealfabric_list_documents vs tealfabric_list_document_tree overlap heavily (the latter is just an action variant), and tealfabric_update_webapp vs tealfabric_create_webapp_version vs tealfabric_publish_webapp have fuzzy boundaries around when to use which.
Every tool follows the same tealfabric_verb_noun snake_case pattern, with a stable verb vocabulary (list, get, create, update, delete, execute, publish, unpublish, move, read/write/download/upload). Compound nouns like process_step and webapp_version are used consistently rather than introducing new conventions.
37 tools is well past the 25+ threshold and is more surface than an agent can reliably route among in one context. While five resource domains partially justify the volume, consolidation is clearly possible (e.g. list_documents/list_document_tree as one tool with an action flag, like list_integrations already does).
Integrations, webapps, processes/steps, and documents each have near-full lifecycle coverage, including versioning, publish/unpublish, soft-retire, and binary-safe upload/download. Minor gaps remain: connectors are read/test only with no create/update, and there is no way to list or fetch individual webapp versions.