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):

~/.cursor/mcp.json
{
  "mcpServers": {
    "vibelogin": {
      "command": "npx",
      "args": ["@vibelogin/mcp"]
    }
  }
}

Claude Code / Claude Desktop

Add to your Claude MCP settings:

claude_desktop_config.json
{
  "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:

Chat

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:

Scaffolded files
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:

Terminal
pnpm add @vibelogin/nextjs
cp .env.local.example .env.local   # fill in VIBELOGIN_SECRET_KEY
pnpm dev

Available tools

The MCP server exposes six tools. Your AI agent picks which to call based on your conversation — you don't configure anything.

ToolWhat it does
list_projectsList all projects in your org
create_projectCreate a new VibeLogin project
get_projectLook up a project by ID or slug
configure_authEnable login methods, set up Google OAuth, add redirect URLs
add_auth_to_projectScaffold auth files into your codebase
authManually 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