Skip to main content
Glama
schmelli

Debeka MCP Server

by schmelli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Debeka MCP Server

No user-submitted related servers found.

    Related Servers

    • form-auto-mcp

      jayounglee92
      A
      license
      A
      quality
      D
      maintenance
      Automates internal system form submissions by reading data from Excel/CSV or Google Sheets and using Playwright to navigate menus and fill form fields, with support for both visible and headless modes.
      1
      4 npm
      MIT

    • mcp-tmobile

      markswendsen-code
      A
      license
      A
      quality
      D
      maintenance
      Automates T-Mobile account interactions such as viewing usage, paying bills, and checking upgrade eligibility using Playwright browser automation.
      5
      19 npm
      MIT

    • Digital Invoice Web MCP

      Muhammad-Usman-Tariq
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables authenticated MCP clients to automate UI-only operations on Digital Invoicing Software via Playwright, including login/session checks, navigation, dashboards, invoice validation/edit/duplication/export, reporting, screenshots, and user management with per-tenant isolation.
      -

    • Lemonade MCP Server

      markswendsen-code
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Lemonade's insurance services for renters, homeowners, pet, and car insurance using Playwright browser automation. Users can retrieve quotes, manage existing policies, file claims, and access policy documents through natural language.
      7
      10 npm
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the form automation workflow: opening, filling, uploading, inspecting, screenshotting, submitting, and closing. There is no meaningful overlap that would cause an agent to select the wrong tool for a given step.

    Naming Consistency4/5

    Tool names consistently use snake_case with a debeka_ prefix and mostly follow a verb_noun pattern like debeka_open_page and debeka_fill_credentials. Minor deviations like debeka_submit and debeka_close omit an explicit object, but the pattern remains predictable.

    Tool Count5/5

    Seven tools is well-scoped for the server's stated purpose of automating a single form submission workflow. Each tool maps to a necessary step or useful utility, with no redundant or excessive additions.

    Completeness4/5

    The tool set covers the full lifecycle from opening the page, filling credentials, uploading documents, submitting, and closing the browser, plus debugging aids like screenshot and page info. Minor gaps exist around post-submission verification or waiting for confirmation, but agents can generally complete the core workflow without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources