MCP Tools DirectoryAbout this integration
Provision SaaS services from YAML and inject .env. Supports Clerk, Stripe, Resend and more.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- vibe-provision
- Last compatibility test
- Not independently tested
Connect your agent
vibe-provisionPublisher documentation and the executable manifest were reviewed; no package or provider API was executed. Tools can create external resources and write local environment files, so operators should review provider scopes, costs, YAML changes, and output targets before use.
Capabilities: SaaS resource provisioning, Provisioning status, YAML service configuration, Environment configuration output
Connected profiles
Additional details
io.github.totte-dev/vibe-provision
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17vibe-provision
Source ↗ · Checked 2026-09-200.1.1
Source ↗ · Checked 2026-09-20After one-time provider authentication, the documented MCP configuration launches vibe-provision mcp through npx for client tool calls.
Source ↗ · Checked 2026-09-20Provider access is configured separately through a one-time auth flow using documented API keys or access tokens stored locally.
Source ↗ · Checked 2026-09-20The MCP client starts the package locally with npx and the mcp subcommand.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20