Skip to main content
@synthbrew/agent lets MCP-capable agents create Synthbrew projects, validate schema configs, provision generated sources, create source API keys, and return runtime API docs.

Install

Most MCP clients can launch the package directly with npx:

Environment variables

Use a team public API key from Settings > Team > Public API keys. Configure these in your MCP client. When run directly in a terminal, the process stays open and waits for MCP messages over stdio.

MCP config

For client-specific setup, see: For local development, set SYNTHBREW_API_URL to your local API base:

Agent workflow

The calling agent drafts the schema itself, then uses Synthbrew tools to validate and provision resources:
  1. Draft a canonical Synthbrew schemaVersionConfig using schemaConfigVersion: "v1" and formatVersion: 1.
  2. Call synthbrew_validate_schema_config.
  3. Fix validation errors and validate again.
  4. List or create a project.
  5. Create a schema.
  6. Create and populate a source.
  7. Create a source API key.
  8. Get runtime docs and return app integration examples.
  9. Fetch sample rows when the user wants to inspect generated data or needs realistic example payloads.
Source API keys beginning with sb_src_ are runtime secrets. Store them securely and do not commit them to source control.

Schema config v1

The public agent contract is frozen as schemaConfigVersion: "v1". The schema config payload uses formatVersion: 1. Synthbrew may add optional fields, enum values, generation settings, and metadata fields to v1 without a new version. Synthbrew will not remove fields, rename fields, change existing meanings, or make optional fields required without introducing a new contract version. Validation requests can include the contract version explicitly:

Example prompts

Use prompts that describe the product or workflow you are building. The agent will turn the request into a Synthbrew schema, validate it, create the source, and return the details your app needs.

Existing app schema

Point your coding agent at the schema files your app already uses when you want Synthbrew data that matches your local models:
The agent can inspect the files, translate the models into a Synthbrew schema, validate the config, populate a source, and return the connection details. This is useful for local development, demos, QA, and frontend work where you need realistic sample rows without connecting to production-like customer data.

SaaS analytics backend

This should produce a relational dataset for dashboards such as MRR, churn, activation, event funnels, support volume, and account health.

Marketplace demo data

This gives frontend and analytics agents a full commerce workflow to build against without wiring a production database.

CRM and sales pipeline

This is useful when you want to build lead lists, kanban pipeline views, sales forecasts, activity timelines, and account detail pages.

Available tools

  • synthbrew_validate_schema_config
  • synthbrew_list_projects
  • synthbrew_create_project
  • synthbrew_list_schemas
  • synthbrew_create_schema
  • synthbrew_list_schema_versions
  • synthbrew_list_sources
  • synthbrew_create_source
  • synthbrew_regenerate_source
  • synthbrew_get_generation_job
  • synthbrew_list_generation_events
  • synthbrew_list_source_api_keys
  • synthbrew_create_source_api_key
  • synthbrew_get_runtime_docs
  • synthbrew_get_source_sample_data
The package does not call Synthbrew’s AI schema generator. Your agent authors schemas and uses Synthbrew validation to repair them.