Seedfast MCP Server
OfficialRelated Servers
Alternatives to Seedfast MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server providing backend access to PostgreSQL, Storage (Supabase/S3), Iceberg data lake, and SQL seeds. It offers 32 tools for database queries, storage operations, seed management, and more.313MIT
- AlicenseNot gradedqualityDmaintenanceAn open-source MCP server for PostgreSQL schema introspection and guarded read-only queries. It enables MCP clients to discover schemas, tables, columns, indexes, relationships, and safe queryable data from a configured PostgreSQL database.21 npmMIT
- AlicenseAqualityCmaintenanceFull-featured MCP server that exposes 36 tools for interacting with PostgreSQL databases, covering schema introspection, query execution, data exploration, performance monitoring, security auditing, and maintenance.366 npmMIT
- AlicenseAqualityBmaintenanceMCP server for PostgreSQL that enables schema exploration, safe SQL execution, EXPLAIN analysis, health checks, and index recommendations across multiple databases.10203 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for PostgreSQL, providing schema discovery, catalog introspection, read-only querying, and optional safe write operations to AI assistants.30 npmPolyForm Noncommercial 1.0.0
- AlicenseAqualityDmaintenanceRead-only PostgreSQL database MCP server for safely exploring schema, tables, relationships, and sample data without modification.1055 npmMIT
TDQS
Scored across 13 tools
Each tool maps to a distinct step in the seeding workflow: environment health, connectivity, schema inspection, plan CRUD, and run management. The only mild ambiguity is between seedfast_plan and seedfast_plan_create, but their descriptions clearly separate backend-generated plans from manually stored ones.
All tools share the seedfast_ prefix and mostly follow a predictable <resource>_<action> pattern such as plan_get, plan_delete, run_status, and run_cancel. A few core tools break that pattern (seedfast_doctor, seedfast_plan, seedfast_run, seedfast_schema_info), but they are recognizable primary actions rather than a chaotic mix.
13 tools is well within the ideal range and each one fills a distinct role across preflight checks, schema introspection, plan management, and run lifecycle. There is no redundant or padding tool.
The set covers the full seeding workflow: diagnose, test connectivity, inspect schema, generate/manage plans, execute runs, monitor progress, cancel, and answer interactive prompts. The only notable gap is the lack of a run-listing tool, but run IDs are returned at creation and seedfast_run_status covers monitoring.