Skip to main content
Glama
burgeonbot

Seed MCP Server

by burgeonbot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Seed MCP Server

No user-submitted related servers found.

    Related Servers

    • Baserow Streamable MCP

      bitingwaxen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote access to Baserow workspaces over Streamable HTTP, allowing discovery of accessible tables and creation of rows using user-facing field names.
      MIT

    • Express REST API and MCP

      bettychavez
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients such as Claude, ChatGPT, and Cursor to discover and act on generated CRUD services over HTTP through tools like create, update, list, and delete, plus read-only resources for listing and fetching records by ID, with no extra glue code.
      MIT

    • Tableau MCP Server

      LokiMCPUniverse
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading and writing to Tableau Server or Tableau Cloud via the REST API, supporting operations on sites, projects, workbooks, views, and data sources.
      4
      -
    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.4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource and action, but there is some overlap between seed_register_org and seed_create_org, as well as between seed_add_documents and seed_add_mock_data. The descriptions help differentiate them, but an agent could still confuse the subtly different purposes.

    Naming Consistency5/5

    All tools follow a consistent seed_<verb>_<noun> snake_case pattern. The verbs are predictable (list, get, create, update, delete, add) and the nouns correspond to resources. Minor pluralization differences (e.g., delete_frames vs delete_org) do not break the overall pattern.

    Tool Count4/5

    With 25 tools, the server is at the upper boundary of the typical range, but the count is justified by covering multiple resources (orgs, tables, frames, views, documents, permissions). A few tools could be consolidated without loss of clarity, but the scope is still reasonable.

    Completeness3/5

    The tool surface has notable gaps: tables lack update and delete operations, documents lack update and get-by-id, and permissions only support grant without revoke. While the core workflows for frames and views are fully covered, these missing operations will require workarounds and may cause agent failures in common scenarios.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources