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 服务器：

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
    ResponsivenessNo recent community issues

    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