Skip to main content
Glama
Sign In
enesjakozh
Better Auth MCP Server

Better Auth MCP Server

by jamesjohnsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

better-auth-mcp-server MCP サーバー

鍛冶屋のバッジ

認証管理用のMCPサーバー

以下を提供するエンタープライズ グレードの認証ソリューション:

  • 🔐 AES-256暗号化による安全な認証情報管理

  • ⚙️ マルチプロトコル認証 (OAuth2、SAML、LDAP)

  • 🛡️ リアルタイムの脅威検出と防止

特徴

コアツール

  • analyze_project - 認証設定の推奨事項のためにプロジェクト構造を分析する

  • setup_better_auth - プロジェクトIDとAPIキーを使用して認証プロバイダーを構成する

  • analyze_current_auth - 既存の auth.js/next-auth 実装を検出する

  • generate_migration_plan - ステップバイステップの移行パスを作成する

テストとセキュリティ

  • test_auth_flows - ログイン/登録/リセット/2FAフローを検証する

  • test_security - OWASP準拠のセキュリティチェックを実行する

  • analyze_logs - 認証システムログで問題を確認する

  • monitor_auth_flows - リアルタイム認証監視

利用可能なリソース

  • better-auth://config - 現在のBetter-Auth構成設定

  • better-auth://logs - 認証システムログ

Related MCP server: Secure MCP Server

発達

クローンしてインストール:

git clone https://github.com/better-auth-mcp-server/better-auth-mcp-server.git
cd better-auth-mcp-server
npm install

サーバーを構築します。

npm run build

自動リビルドを使用した開発の場合:

npm run watch

構成

環境変数

# Required
BETTER_AUTH_PROJECT_ID=your-project-id
BETTER_AUTH_API_KEY=your-api-key

# Optional
BETTER_AUTH_ENV=development|staging|production
LOG_LEVEL=info|debug|error

セキュリティのベストプラクティス

  1. APIキー管理

    • APIキーを環境変数に保存する

    • 定期的にキーをローテーションする

    • 環境ごとに異なるキーを使用する

  2. アクセス制御

    • レート制限を実装する

    • IP許可リストを設定する

    • 最小権限の原則を使用する

  3. 監視

    • 監査ログを有効にする

    • 認証失敗を監視する

    • 不審なアクティビティに関するアラートを設定する

インストール

Smithery経由でインストール

Smithery経由で Claude Desktop 用の Better Auth MCP Server を自動的にインストールするには:

npx -y @smithery/cli install @nahmanmate/better-auth-mcp-server --client claude

Claude Desktop で使用するには、サーバー設定を追加します。

MacOS の場合: ~/Library/Application Support/Claude/claude_desktop_config.json Windows の場合: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "better-auth-mcp-server": {
      "command": "node",
      "args": ["/path/to/better-auth-mcp-server/build/index.js"],
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

デバッグ

MCPサーバーはstdio経由で通信するため、デバッグが困難になる場合があります。パッケージスクリプトとして提供されているMCP Inspectorの使用をお勧めします。

npm run inspector

インスペクターは、ブラウザでデバッグ ツールにアクセスするための URL を提供します。

使用例

プロジェクトのセットアップ

// Initialize Better-Auth in your project
await mcp.useTool('setup_better_auth', {
  projectPath: './my-next-app',
  config: {
    projectId: process.env.BETTER_AUTH_PROJECT_ID,
    apiKey: process.env.BETTER_AUTH_API_KEY
  }
});

// Test core authentication flows
await mcp.useTool('test_auth_flows', {
  flows: ['login', 'register', '2fa']
});

Auth.js/NextAuthからの移行

// Analyze current auth implementation
await mcp.useTool('analyze_current_auth', {
  projectPath: './my-next-app'
});

// Generate migration steps
await mcp.useTool('generate_migration_plan', {
  projectPath: './my-next-app',
  currentAuthType: 'next-auth'
});

Available Tools

8 tools
analyze_current_authC

Detect and analyze existing auth.js/next-auth implementation

Inputs: projectPath (required).

analyze_logsC

Analyze Better-Auth logs for issues

Inputs: timeRange (required).

analyze_projectC

Analyze project structure and dependencies to recommend Better-Auth setup approach

Inputs: projectPath (required).

generate_migration_planB

Create step-by-step migration plan from existing auth to Better-Auth

Inputs: projectPath (required), currentAuthType (required).

monitor_auth_flowsC

Real-time monitoring of authentication processes

Inputs: duration (required).

setup_better_authC

Install and configure Better-Auth in the project

Inputs: projectPath (required), config (required).

test_auth_flowsC

Test authentication workflows

Inputs: flows (required).

test_securityC

Run security tests on Better-Auth setup

Inputs: tests (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between analyze_current_auth, analyze_project, and analyze_logs, which all involve analysis and could potentially be confused for similar tasks. However, their descriptions clarify specific focuses (existing implementation, project structure, logs), reducing ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as analyze_current_auth, setup_better_auth, and test_auth_flows. This predictability makes it easy for agents to understand and select tools based on their naming conventions.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose of migrating to and managing Better-Auth. Each tool serves a clear role in the migration and monitoring process, from analysis and setup to testing and monitoring, without being overly sparse or bloated.

    Completeness4/5

    The tool set covers key aspects of migration (analysis, setup, testing, monitoring) but lacks explicit tools for updating or deleting configurations, which might be needed for ongoing maintenance. However, core workflows are well-covered, allowing agents to handle most migration tasks effectively.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Better Auth MCP Server

      LexiconAlex
      A
      license
      B
      quality
      D
      maintenance
      Enterprise-grade authentication solution that provides secure credential management with encryption, multi-protocol authentication (OAuth2, SAML, LDAP), and real-time threat detection for applications.
      8
      1
      AGPL 3.0

    • Secure MCP Server

      perfecxion-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides an enterprise-grade Model Context Protocol implementation with advanced security features including multi-factor authentication, encryption, and RBAC. Enables secure tool management and context handling for production deployments with comprehensive monitoring and high availability.
      60 npm
      2
      AGPL 3.0

    • vault-mcp

      gwanghun-choi
      F
      license
      Not graded
      quality
      C
      maintenance
      Centralized credential management for servers, websites, and APIs with HashiCorp Vault integration. Provides authentication, authorization, and audit logging for secure access to secrets.
      2
      -

    • mkeys

      WinFactorAI
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to securely manage local credentials, obtain short-lived tokens for authenticated API access, and audit every use by purpose.
      9
      MIT

    Appeared in Searches