mcpField
B
better-auth-mcp-server MCP Server

better-auth-mcp-server MCP Server

Local
github.com/nahmanmateDeveloper Tools41Updated 89w ago

About better-auth-mcp-server MCP Server

better-auth-mcp-server is an MCP server for authentication management, aimed at projects that use or plan to adopt Better Auth. It provides tools to analyze projects, set up Better Auth, plan migrations from auth.js or NextAuth, and test authentication flows.

Key features

  1. 01Analyze project structure for auth recommendations
  2. 02Configure Better Auth providers
  3. 03Detect existing auth.js or next-auth implementations
  4. 04Generate step-by-step migration plans
  5. 05Test login, registration, reset and 2FA flows

Use cases

  1. 01Migrating a next-auth project to Better Auth
  2. 02Checking authentication flows and security settings
  3. 03Reviewing auth logs and monitoring authentication events

MCP support

This project is an MCP server that exposes analysis, setup, testing and monitoring tools, plus better-auth://config and better-auth://logs resources, to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"better-auth": {
"command": "npx",
"args": [
"-y",
"@smithery/cli"
]
}
}
}
Run commandnpx -y @smithery/cli

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@smithery/cli

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

better-auth-mcp-server MCP Server

smithery badge

MCP Server for Authentication Management

Enterprise-grade authentication solution providing:

  • 🔐 Secure credential management with AES-256 encryption
  • ⚙️ Multi-protocol auth (OAuth2, SAML, LDAP)
  • 🛡️ Real-time threat detection and prevention

Better Auth Server MCP server

Features

Core Tools
  • analyze_project - Analyze project structure for auth setup recommendations
  • setup_better_auth - Configure auth providers with project ID and API key
  • analyze_current_auth - Detect existing auth.js/next-auth implementations
  • generate_migration_plan - Create step-by-step migration path
Testing & Security
  • test_auth_flows - Validate login/register/reset/2fa flows
  • test_security - Run OWASP-aligned security checks
  • analyze_logs - Review auth system logs for issues
  • monitor_auth_flows - Real-time authentication monitoring
Available Resources
  • better-auth://config - Current Better-Auth configuration settings
  • better-auth://logs - Authentication system logs

Development

Clone and install:

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

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Configuration

Environment Variables
# 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
Security Best Practices
  1. API Key Management

    • Store API keys in environment variables
    • Rotate keys regularly
    • Use different keys per environment
  2. Access Control

    • Implement rate limiting
    • Configure IP allowlists
    • Use principle of least privilege
  3. Monitoring

    • Enable audit logging
    • Monitor auth failures
    • Set up alerts for suspicious activity

Installation

Installing via Smithery

To install Better Auth MCP Server for Claude Desktop automatically via Smithery:

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

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On 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": []
    }
  }
}
Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Usage Examples

Project Setup
// 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']
});
Migration from 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'
});

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.