Skip to main content
Glama
Arneld18

Backforms MCP

by Arneld18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Backforms MCP

No user-submitted related servers found.

    Related Servers

    • ironxyz

      ironxyz
      A
      license
      A
      quality
      C
      maintenance
      Official MCP (Model Context Protocol) server for Iron.xyz API, designed to work with Claude Desktop, Cursor IDE and other MCP compatible clients.
      3
      14 npm
      2
      MIT

    • Cogniz Memory Platform MCP

      cognizonline
      A
      license
      Not graded
      quality
      D
      maintenance
      Official Model Context Protocol (MCP) server for Cogniz Memory Platform. Enables AI assistants like Claude to store and retrieve memories across conversations.
      MIT

    • contextforge-mcp

      alfredoizdev
      A
      license
      A
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based, Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based organization, and team collaboration via Model Context Protocol.
      11
      88 npm
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (create/list/update/delete form, get submissions, get details, test submission, workspace usage). Minor overlap exists between update_form_settings and setup_webhook (both tweak a form's configuration), and between get_form_details and get_form_submissions, but descriptions clearly separate config from data and add a slight risk of misselection.

    Naming Consistency5/5

    All nine tools use a consistent snake_case verb_noun pattern (create_form, list_forms, get_form_submissions, update_form_settings, delete_form, get_form_details, setup_webhook, send_test_submission, check_workspace_usage). The convention is predictable and readable throughout.

    Tool Count5/5

    Nine tools is well-scoped for a serverless form backend, covering the create/read/update/delete lifecycle plus submissions, webhooks, testing, and usage. Each tool earns its place with no obvious redundancy.

    Completeness4/5

    Full form CRUD, submissions retrieval, webhook/email setup, test submission, and usage checking are covered, giving solid lifecycle support. The main gap is submission-level management (e.g., fetching or deleting an individual submission by ID/export), which agents may want but can partly work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources