Better Auth MCP Server
Related Servers
Alternatives to Better Auth MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables interaction with AIApp BaaS authentication system through keyword-based document search and automatic generation of framework-specific client code. Supports React, Next.js, Vue, and Vanilla JS with TypeScript integration and automatic project ID injection.332 npmMIT
- AlicenseNot gradedqualityDmaintenanceDelivers curated documentation, quickstart commands, and stack recommendations for modern full stack web development through MCP-enabled AI assistants.MIT
- AlicenseNot gradedqualityAmaintenanceProvides live, clean, LLM-ready markdown documentation for popular fullstack technologies and custom URLs, with built-in presets for React, Next.js, TypeScript, and more.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides instant access to 700+ programming documentation sources and creates isolated Docker containers for safe code testing and experimentation. Combines comprehensive documentation lookup with containerized development environments for enhanced development workflows.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceProvides real-time, up-to-date documentation for major LLM providers (OpenAI, Anthropic, Google Gemini) to prevent hallucinations and outdated code patterns in AI agents.11 npm6MIT
- AlicenseNot gradedqualityDmaintenanceProvides production-ready implementation patterns for features like authentication, payments, and deployments to AI coding assistants. It enables developers to search and retrieve battle-tested code snippets and setup steps for full-stack tasks.MIT
TDQS
Scored across 6 tools
Every tool has a clearly distinct purpose with no ambiguity: list_better_auth_features provides a categorized overview, get_feature_details offers in-depth information on specific items, get_integration_guide focuses on framework/platform integration, get_auth_examples supplies code snippets, get_llms_context delivers comprehensive context via LLMs.txt, and search_better_auth enables keyword-based documentation search. The descriptions clearly differentiate each tool's scope.
All tool names follow a consistent verb_noun pattern with snake_case: get_auth_examples, get_feature_details, get_integration_guide, get_llms_context, list_better_auth_features, and search_better_auth. The naming is predictable and readable throughout, using 'get' for retrieval operations, 'list' for listing, and 'search' for searching, with no deviations in style.
With 6 tools, the count is well-scoped for a documentation and feature exploration server. Each tool earns its place by covering distinct aspects like listing, detailing, integrating, providing examples, offering context, and searching, without being too sparse or bloated. This aligns with typical server scopes of 3-15 tools.
The tool surface is nearly complete for a documentation server, covering core workflows: listing features, getting details, integration guides, examples, context, and search. A minor gap exists in the lack of update or interactive tools (e.g., for modifying or testing configurations), but agents can effectively navigate and retrieve information with the provided tools.