Summary
Auth set up from the editor, including the code.
The distinction worth noticing is the last step: it does not just create the project and hand you docs, it scaffolds the sign-in flow into the codebase. Creation returns a secret key exactly once, so capture it when it appears.
What it is
An MCP server for VibeLogin that creates and configures authentication projects and wires a sign-in flow into the codebase you are working in, published as @vibelogin/mcp.
What you get
- A project created in your org, returning its id, slug, oauthSlug, environment, publishable key and a secret key shown once
- Environments chosen at creation: production, development or staging
- Every project in the org listed, so the agent checks what exists before creating a duplicate
- A single project looked up by id, slug or oauthSlug
- Auth methods configured on a project, including Google OAuth and redirect URLs
- Auth scaffolded into the project you have open, rather than left as instructions to follow
Requirements
A VibeLogin account. The first tool call opens a browser for one-click consent, after which tokens are cached under ~/.vibelogin/credentials.json and reused until they expire. Bun, since it runs via `bunx`. No environment variables to set.
Setup effort
One command — bunx @vibelogin/mcp