Skip to main content
Glama
tealfabric

Tealfabric MCP Server for Cursor

Official
by tealfabric
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Tealfabric MCP Server for Cursor

No user-submitted related servers found.

    Related Servers

    • Deployment.io MCP Server

      deployment-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing and deploying apps to your cloud directly from Cursor through natural language, including environment management, job monitoring, and approval workflows.
      1
      MIT

    • Fledge MCP Server

      Krupalp525
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Fledge functionality to Cursor AI, allowing interaction with Fledge instances via natural language commands.
      MIT

    • Genesys Cloud Function Data

      darbyje
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      2
      MIT

    • Azure DevOps MCP Server

      dhippley
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables 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.
      1
      -

    • TeamCity MCP Server

      hex
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of TeamCity CI/CD operations through natural language commands, including builds, projects, tests, artifacts, and more.
      8 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool maps to a clear resource-and-action pair: connectors, integrations, webapps, processes, process steps, and documents are kept separate. Even the list tools that can fetch specific details remain clearly distinct from the other get/test/execute operations.

    Naming Consistency5/5

    All tools share the tealfabric_ prefix and follow a consistent snake_case verb_noun pattern (list_*, get_*, create_*, update_*, test_*, delete_*). The longer get_connector_oauth2_required name still fits the overall convention.

    Tool Count3/5

    At 26 tools, the surface is on the heavy side and above the typical comfortable MCP range. However, the count reflects five distinct resource domains with focused operations rather than duplicate or random tools, so it feels large but not bloated.

    Completeness2/5

    There are significant lifecycle gaps: integrations, webapps, processes, and process steps have create/update but no delete, and webapps have publish but no unpublish/delete. Agents managing these resources will hit dead ends for teardown or cleanup workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources