A
licenseNot graded
qualityB
maintenanceEnables remote access to Baserow workspaces over Streamable HTTP, allowing discovery of accessible tables and creation of rows using user-facing field names.
MIT
Seed MCP Server
by burgeonbot
Related Servers
Alternatives to Seed MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceEnables interaction with the AppFlowy Cloud API to manage workspaces, databases, and row operations. It provides tools for authentication, resource discovery, and full row manipulation including creation and upserts.94-
- FlicenseNot gradedqualityDmaintenanceEnables reading and writing to Tableau Server or Tableau Cloud via the REST API, supporting operations on sites, projects, workbooks, views, and data sources.4-
- FlicenseNot gradedqualityDmaintenanceProvides tools to interact with the Attio API, enabling management of resources in an Attio workspace.5-
- AlicenseAqualityDmaintenanceParses Mermaid ER diagrams to create PostgreSQL tables and automatically generates REST and GraphQL CRUD APIs.12MIT
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Airtable bases and tables, allowing schema inspection and record CRUD operations using DAuth authentication.-
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
ActivityStale
ResponsivenessNo issues