
Public integration surface for the Seedfast MCP server: client configuration, tool reference and a
Public integration surface for the Seedfast MCP server: client configuration, tool reference and a smoke test
·
Seedfast fills a PostgreSQL database with realistic, relationally valid test data generated from its live schema, so a team that cannot put production data into development still gets an environment that behaves like production.
This repository is the public integration surface for its MCP server. You will find the client configuration, the tool reference and a smoke test here. The engine and the CLI themselves are closed-source and ship through npm and Homebrew.
Published in the official MCP registry as st.seedfa/seedfast.
Nothing separate to install. The MCP server is built into the Seedfast CLI and runs straight from npx:
{
"mcpServers": {
"seedfast": {
"command": "npx",
"args": ["-y", "seedfast@latest", "mcp"],
"env": {
"SEEDFAST_API_KEY": "sfk_live_your_api_key_here"
}
}
}
}That block goes into claude_desktop_config.json for Claude Desktop, .cursor/mcp.json for Cursor, or the equivalent file for VS Code and Claude Code. Client-by-client paths are in the MCP setup guide.
Prefer a local binary? Install the CLI and point command at seedfast with args: ["mcp"] instead:
brew install seedfast-ai/tap/seedfast # macOS, Linux
npm install -g seedfast # any platform with Node.js| Variable | Required | What it does |
|---|---|---|
SEEDFAST_API_KEY | yes | API key created in the Seedfast dashboard |
SEEDFAST_MCP_RUNS_DB | no | Path to a SQLite file. Without it, runs and plans live in memory and disappear when the server exits |
Thirteen tools cover the whole loop of planning a seed, running it and inspecting what happened.
| Tool | What it does |
|---|---|
seedfast_doctor | Checks CLI health and whether authentication is configured |
seedfast_connections_test | Tests a database connection before anything is written |
seedfast_schema_info | Reads the live schema of the target database |
seedfast_plan | Builds a seeding plan from a scope description |
seedfast_run | Executes a seeding run |
seedfast_run_status | Polls a run in progress |
seedfast_run_cancel | Aborts a run |
seedfast_run_answer | Answers a question the run raised while it was waiting for input |
seedfast_plans_list | Lists saved plans |
seedfast_plan_get | Reads one saved plan |
seedfast_plan_create | Saves a new plan |
seedfast_plan_update | Edits a saved plan |
seedfast_plan_delete | Removes a saved plan |
| URI | Media type | Contents |
|---|---|---|
seedfast://runs/{runId}/summary | application/json | Summary of a seeding run |
seedfast://runs/{runId}/log | application/x-ndjson | Event log of a seeding run |
seedfast://runs/{runId}/pending_question | application/json | The question a run is waiting on, while it is in awaiting_input |
seedfast://plans/{planId} | application/json | Details of a saved plan |
Two prompts ship with the server: seed-production-db, which takes a scope and a description of the target database, and scope-examples, which turns a use case into example scopes.
The smoke test starts the published package over stdio, completes an MCP handshake and lists the tools. It needs no API key, since it never reaches the backend:
node scripts/smoke-test.mjsExpected output ends with the protocol version the server negotiated and the number of tools it advertises.
Seedfast works with PostgreSQL today. Going PostgreSQL-first was deliberate, since its constraint and relationship system is the richest one out there and that is exactly where generating believable data gets hard. Support for MySQL, Oracle and SQLite is in development.
MIT for the contents of this repository. The Seedfast CLI is distributed under the same license; its engine runs as a hosted service.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add seedfast -- npx -y seedfast@latest mcp{
"mcpServers": {
"seedfast": {
"env": {
"SEEDFAST_API_KEY": ""
},
"args": [
"-y",
"seedfast@latest",
"mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"seedfast","env":{"SEEDFAST_API_KEY":""},"args":["-y","seedfast@latest","mcp"],"command":"npx"}'[mcp_servers.seedfast]
command = "npx"
args = ["-y", "seedfast@latest", "mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/seedfast-mcp-server to learn what the "Seedfast MCP Server" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
brew install seedfast-ai/tap/seedfastnpm install -g seedfastThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/seedfast-mcp-server)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "seedfast-mcp-server" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.