analyze_current_auth
Detect and analyze existing auth.js/next-auth implementation
LABSCO SUMMARY
The migration is the use case.
Analysing the existing auth.js or next-auth setup and producing a plan from it is the part that is hard to do by hand and easy to get wrong halfway through. The testing tools matter for the same reason: after a migration the failure mode is a flow that still works for the happy path and silently broke password reset or 2FA, and those are exactly the flows this exercises.
What it is
An MCP server aimed at projects moving onto Better-Auth. It reads a project's structure and its existing auth.js or next-auth implementation, produces a step-by-step migration plan, configures providers, and then tests the resulting flows and checks them against OWASP-aligned rules.
What you get
- A project read for what its auth setup should be, and the auth it already has detected in place —
analyze_project,analyze_current_auth - A step-by-step path off the current implementation, taking the current auth type as input —
generate_migration_plan - Auth providers configured against a project id and API key —
setup_better_auth - Login, register, reset and 2FA flows exercised, and OWASP-aligned security checks run over the result —
test_auth_flows,test_security - Auth system logs reviewed for problems, and authentication activity watched as it happens —
analyze_logs,monitor_auth_flows - Two resources to read directly: the current configuration at
better-auth://configand the logs atbetter-auth://logs
Requirements
A Better-Auth project id and API key, supplied as BETTER_AUTH_PROJECT_ID and BETTER_AUTH_API_KEY. BETTER_AUTH_ENV selects development, staging or production and LOG_LEVEL sets verbosity; both are optional. The npm package name is better-auth-mcp-server (0.1.0) and it is marked private, so install from a clone with npm install and npm run build. Use a different API key per environment, since the same key reaches whatever that environment's auth configuration is.
Setup effort
Build from source — git clone https://github.com/jamesjohnsdev/better-auth-mcp-server.git
USE CASES
01
Working out what auth a codebase is actually running
Point it at the project and get back the existing auth.js or next-auth implementation it found, before deciding whether to change anything.
02
Planning a move off next-auth
Generate a step-by-step migration path from the current auth type, then configure the new providers against your project id.
03
Checking the flows nobody tests by hand
Exercise login, register, password reset and 2FA together, so the flows that only break for a subset of users get caught in the same pass.
04
Finding out why sign-ins are failing in production
Review the auth logs for the pattern behind the failures and watch authentication activity while you reproduce it.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
analyze_logs
Analyze Better-Auth logs for issues
analyze_project
Analyze project structure and dependencies to recommend Better-Auth setup approach
generate_migration_plan
Create step-by-step migration plan from existing auth to Better-Auth
monitor_auth_flows
Real-time monitoring of authentication processes
setup_better_auth
Install and configure Better-Auth in the project
test_auth_flows
Test authentication workflows
test_security
Run security tests on Better-Auth setup
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected.
Requires
- Node.js with npm
- A Better-Auth project ID and API key (BETTER_AUTH_PROJECT_ID, BETTER_AUTH_API_KEY)
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/jamesjohnsdev/better-auth-mcp-server.git
cd better-auth-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop — Local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"better-auth-mcp-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_BETTER_AUTH_MCP_SERVER>/build/index.js"
],
"env": {
"BETTER_AUTH_PROJECT_ID": "<YOUR_BETTER_AUTH_PROJECT_ID>",
"BETTER_AUTH_API_KEY": "<YOUR_BETTER_AUTH_API_KEY>"
},
"disabled": false,
"alwaysAllow": []
}
}
}<YOUR_PATH_TO_BETTER_AUTH_MCP_SERVER> is the full path of your clone (build/index.js appears after npm run build). BETTER_AUTH_ENV (development, staging or production) and LOG_LEVEL are optional.
The server needs BETTER_AUTH_PROJECT_ID and BETTER_AUTH_API_KEY; the Local build block passes them in its env section.
