create_projectLABSCO 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
USE CASES
01
Adding sign-in to an app that has none
Create the project, configure the auth methods, and have the sign-in flow scaffolded into the code you are already in.
02
Avoiding a duplicate project
List what the org already has before creating anything new.
03
Keeping staging and production separate
Create the project against the environment you mean — production, development or staging — rather than sorting it out later.
04
Turning on Google sign-in
Configure Google OAuth and the redirect URLs on an existing project.
05
Finding a project's keys again
Look it up by id, slug or oauthSlug to get its publishable key and environment back.
5 tools
Listed in project docs. Your client may show a different list.
list_projectsget_projectconfigure_authadd_auth_to_projectBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
bunx on PATH
Where it runs
All 5 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
bunx @vibelogin/mcpMCP Clients
Claude Desktop, Claude Code, Cursor, Windsurf, Cline
JSON
{
"mcpServers": {
"vibelogin": {
"command": "bunx",
"args": [
"@vibelogin/mcp"
]
}
}
}
