Vibelogin Mcp

io.github.snrniranjan由 GitHub 帳號 snrniranjan 發布v0.1.2更新於 Oct 24, 2026

Add authentication to your app without leaving your IDE.

已驗證STDIO僅桌面開發者工具安全與監控

概覽

AI 產生的概覽

一個本機 MCP 伺服器,讓助理建立 VibeLogin 驗證專案、設定登入方式,並把可用的登入流程 scaffold 進你的程式碼庫。

可以做什麼
建立、列出並查詢組織內的 VibeLogin 專案,包含金鑰與環境資訊。切換驗證方式、設定重新導向 URL 並設定 Google OAuth 憑證。將登入流程 scaffold 進 Next.js 或 Vite + React 專案,以非破壞性方式產生檔案並印出後續步驟。
適用情境
當你想在編輯器對話中讓助理為 Next.js 或 Vite + React 應用程式加入託管驗證,而不想手動設定驗證時使用。對其他框架沒有幫助,它會拒絕並提供指引。
執行需求
透過 bunx 在本機執行,因此機器上需要安裝 Bun。不需要環境變數。第一次呼叫工具會開啟瀏覽器進行一鍵授權,權杖會快取 30 天。需要 VibeLogin 帳號與組織。
安裝前請注意
第一次呼叫會開啟瀏覽器進行 OAuth 授權,並把權杖存放在磁碟上的憑證檔案中。create_project 會回傳只顯示一次的金鑰,configure_auth 需要接收 Google OAuth 用戶端密鑰。傳入 redirectUrls 時 configure_auth 會覆寫專案的重新導向 URL 清單。add_auth_to_project 會將檔案寫入專案目錄,但會略過已存在的檔案。專案與驗證設定的變更發生在遠端服務上。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Vibelogin Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

@vibelogin/mcp

Add authentication to your app without leaving your IDE. MCP server for Cursor, Claude Code, Windsurf, and Cline.

Just say "add authentication to my app" — the agent creates your project, configures auth methods, wires up Google OAuth, and scaffolds a working sign-in flow into your codebase. All from your editor's chat.


Install

No global install needed. Wire it into your MCP client config once and it runs on demand via bunx.


Client configuration

One snippet works in every client. Paste this into your MCP settings and you're done.

json
{  "mcpServers": {    "vibelogin": {      "command": "bunx",      "args": ["@vibelogin/mcp"]    }  }}

The first tool call opens a browser for one-click consent. After that, tokens are cached under ~/.vibelogin/credentials.json — you won't be asked to log in again for 30 days.

Claude Desktop / Claude Code

~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

json
{  "mcpServers": {    "vibelogin": {      "command": "bunx",      "args": ["@vibelogin/mcp"]    }  }}

Cursor

~/.cursor/mcp.json (or per-project .cursor/mcp.json):

json
{  "mcpServers": {    "vibelogin": {      "command": "bunx",      "args": ["@vibelogin/mcp"]    }  }}

Windsurf / Cline / Zed

Same shape — every MCP client accepts a command + args block. The one-liner above works in all of them.

That's it — no environment variables needed. Defaults point to production automatically.


Authentication

On first use, a browser window opens for one-click consent. After that, you're authenticated for 30 days — no further prompts.


Tools

The agent picks the right tools automatically based on your conversation. Just say what you need.

create_project

Creates a new VibeLogin project in your org. Returns the project's id, slug, oauthSlug, environment, publishable key, and secret key (shown once).

ParamTypeRequiredDescription
namestringyesHuman-readable project name.
slugstringnoURL-safe slug; auto-generated from name if omitted.
environmentenumnoproduction | development | staging (default production).

list_projects

Lists every project in your org. Use this when the agent needs to discover what already exists before creating something new.

No parameters.

get_project

Look up a single project by id, slug, or oauthSlug.

ParamTypeRequiredDescription
idOrSlugstringyesProject id, slug, or oauthSlug.

configure_auth

Toggle auth methods, set redirect URLs, and/or wire up Google OAuth. Field-level updates — anything you don't set is left untouched.

ParamTypeRequiredDescription
projectIdstringyesThe project's id.
methods.emailPasswordbooleannoEnable email + password sign-in.
methods.magicLinkbooleannoEnable magic link emails.
methods.emailOtpbooleannoEnable 6-digit email OTP codes.
methods.passwordResetbooleannoEnable password reset emails.
methods.emailVerificationbooleannoRequire email verification on signup.
google.clientIdstringwith googleGoogle OAuth client ID (from Google Cloud Console).
google.clientSecretstringwith googleGoogle OAuth client secret.
google.enabledbooleannoDefault true.
redirectUrlsstring[]noOverwrites the project's allowed redirect URL list.

If you call this without google, the response includes the exact Google Cloud Console URL + redirect URI you need to set up the credentials.

add_auth_to_project

Scaffold a working sign-in flow into your codebase. Detects the framework from package.json and writes non-destructive files (existing files are skipped, never clobbered).

Supported frameworks today: Next.js (App Router), Vite + React. Refused with guidance: Remix, Astro, Express, unknown.

ParamTypeRequiredDescription
projectDirstringyesAbsolute path to the project root.
slugstringyesThe project's oauthSlug (from create_project).
publishableKeystringyesThe project's publishable key.
appUrlstringyesYour app's origin (e.g. https://myapp.com).
Files written for Next.js
middleware.ts                       # hostedAuthMiddlewareapp/auth/callback/route.ts          # createCallbackHandlerapp/login/page.tsx                  # <VibeLogin />.env.local.example                  # publishable key + secret placeholder

Next steps printed by the tool:

  1. pnpm add @vibelogin/nextjs
  2. Copy .env.local.example → .env.local, fill VIBELOGIN_SECRET_KEY
  3. pnpm dev → open /login
Files written for Vite + React
src/auth/VibeLoginProvider.tsx      # context + useVibeLogin() hooksrc/auth/Login.tsx                  # /login redirect to hosted UIsrc/auth/Callback.tsx               # /auth/callback handler.env.example                        # VITE_-prefixed publishable key

Next steps printed by the tool:

  1. pnpm add @vibelogin/react react-router-dom
  2. Wrap <App/> in <VibeLoginProvider/>
  3. Add routes /login and /auth/callback
  4. Copy .env.example → .env.local
  5. pnpm dev → open /login

Example conversations

You: "Add VibeLogin to this Next.js app. Email + password and Google sign-in."

Agent: (calls create_project { name: "myapp", environment: "production" }) Created myapp (pk_live_…). (calls configure_auth { projectId, methods: { emailPassword: true } }) Email + password enabled. To turn on Google, I need a Client ID and Secret from Google Cloud Console — here's the redirect URI to authorize: https://api.vibelogin.com/oauth/myapp-xyz/google/callback. (after you paste creds:) (calls configure_auth { google: { clientId, clientSecret } }) (calls add_auth_to_project { projectDir: ".", slug: "myapp-xyz", publishableKey: "pk_live_…", appUrl: "https://myapp.com" }) Scaffold complete (next). Wrote middleware.ts, app/auth/callback/route.ts, app/login/page.tsx, .env.local.example. Run pnpm add @vibelogin/nextjs && pnpm dev and open /login.

You: "What projects do I have already?"

Agent: (calls list_projects) You have 3: myapp (production), myapp-staging (staging), internal-tools (development).


Security

  • No secrets in the agent — authentication uses loopback OAuth + PKCE (RFC 8252)
  • Single-use authorization codes with 2-minute TTL
  • Rotated refresh tokens — every refresh invalidates the previous one
  • Credentials stored securely — chmod 600 on ~/.vibelogin/credentials.json

Supported frameworks

FrameworkStatus
Next.js (App Router)Fully supported
Vite + ReactFully supported
Remix, Astro, ExpressComing soon

License

Apache-2.0

來源:README.md,提交 521101c

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。