Skip to content
MCP Bridge Docs

Writing a Recipe

Authoring checklist

Section titled “Authoring checklist”
  1. Create servers/<id>/recipe.json
  2. Define at least one transport
  3. Define auth requirements and env vars
  4. Add install method for stdio transports
  5. Add metadata (category, tags, maturity, toolExamples)
  6. Validate with CLI before submit
Terminal window
npx @aiwerk/mcp-bridge validate-recipe ./recipe.json

Migration from v1

Section titled “Migration from v1”
Terminal window
npx @aiwerk/mcp-bridge migrate-recipe servers/todoist/config.json

This generates a v2 recipe.json. Legacy config.json remains supported during transition.

Security recommendations

Section titled “Security recommendations”
  • Never store credentials in recipe files
  • Avoid preInstall / postInstall; they are security-sensitive and warned by validators
  • Prefer explicit auth.instructions and credentialsUrl for user setup

For publishing behavior, see Catalog tools.