MCP Server — Auth from your IDE
The VibeLogin MCP server lets AI coding agents set up authentication for you. Say "add auth to my app" in Cursor, Claude Code, Windsurf, or Cline — it creates your project, configures login methods, and writes all the files. You never leave the editor.
What it does
The MCP server exposes VibeLogin as a set of tools any MCP-capable agent can call. The agent decides when to use them based on your conversation. Under the hood it:
- ✓Creates a VibeLogin project in your org
- ✓Enables email/password, magic links, or OAuth login
- ✓Wires up Google OAuth with the right redirect URIs
- ✓Scaffolds middleware, callback route, and login page into your codebase
- ✓Writes .env.local with your keys
Setup
Add this to your MCP client config. No global install needed — npx handles it.
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):
{
"mcpServers": {
"vibelogin": {
"command": "npx",
"args": ["@vibelogin/mcp"]
}
}
}Claude Code / Claude Desktop
Add to your Claude MCP settings:
{
"mcpServers": {
"vibelogin": {
"command": "npx",
"args": ["@vibelogin/mcp"]
}
}
}Windsurf / Cline / Zed
Same config — every MCP client accepts a command + args pair. Drop the snippet above into your client's MCP settings.
Authentication
The first time a tool runs, it opens a browser window for one-click consent. You approve once and the token is cached for 30 days. No API keys to copy, no env vars to set.
Usage
Once the MCP server is configured, just talk to your AI agent:
you > "add authentication to my app"
vibelogin · Creating project…✓
vibelogin · Enabling email + password✓
vibelogin · Scaffolding auth files…✓
Done. Login, signup, and OAuth are live.
Files written
For a Next.js App Router project, the MCP server writes:
middleware.ts # hostedAuthMiddleware
app/auth/callback/route.ts # createCallbackHandler
app/login/page.tsx # <VibeLogin /> component
.env.local.example # keys (fill in your secret)Existing files are never overwritten. After scaffolding, run:
pnpm add @vibelogin/nextjs
cp .env.local.example .env.local # fill in VIBELOGIN_SECRET_KEY
pnpm devAvailable tools
The MCP server exposes six tools. Your AI agent picks which to call based on your conversation — you don't configure anything.
| Tool | What it does |
|---|---|
list_projects | List all projects in your org |
create_project | Create a new VibeLogin project |
get_project | Look up a project by ID or slug |
configure_auth | Enable login methods, set up Google OAuth, add redirect URLs |
add_auth_to_project | Scaffold auth files into your codebase |
auth | Manually trigger browser login (rarely needed) |
Supported frameworks
- ✓Next.js (App Router) — full scaffolding
- ✓Vite + React — full scaffolding
- ○Remix, Astro, Express — coming soon
npm package
@vibelogin/mcp on npm. Source on GitHub.
Next steps
- →SDK Quickstart— manual setup if you prefer
- →Middleware— customize route protection
- →OAuth setup— add Google and GitHub sign-in
- →Security— what VibeLogin handles for you