Skip to main content
Glama
mohn93

community-ff-mcp

by mohn93
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to community-ff-mcp

No user-submitted related servers found.

    Related Servers

    • flutterflow-mcp

      jamesnocode
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for FlutterFlow that uses a command-palette model to manage projects, inspect UI, and apply safe edits via transactional ChangeSets.
      4 npm
      10
      MIT

    • figma-mcp

      chisanucha-suwan
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only Figma MCP server that enables design-to-code workflows by talking to the Figma REST API with a personal access token, for use with Claude Code and GitHub Copilot.
      1,330 npm
      MIT

    • claudeaibridge

      yemi-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables claude.ai, including free users, to act as a coding agent on your own machine, allowing file edits, shell commands, and git operations within explicitly chosen project folders. It provides a secure local MCP server exposed as a custom connector with OAuth-based consent.
      GPL 3.0
    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

    A4.1/5.0

    Scored across 25 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear separation between listing, reading, searching, and updating. Some overlap exists among the many settings getters and between get_editing_guide and get_yaml_docs, but descriptions are specific enough to avoid major confusion.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun naming with uniform prefixes like list_, get_, find_, validate_, update_, sync_, and search_. The pattern is predictable and makes the toolset easy to navigate.

    Tool Count3/5

    At 25 tools, this is on the heavy side and right at the borderline for what feels reasonable. Each tool covers a specific FlutterFlow feature or settings section, so the count is justifiable, but it is still at the upper edge of appropriateness.

    Completeness4/5

    The tool set covers the full read/update workflow for YAML, including validation, documentation, and reference. Missing explicit tools like list_components or project creation/deletion, but these can be worked around via file listing and YAML updates, so gaps are minor.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources