Skip to main content
Glama
dabhivijay2478

Better Auth MCP Server

list_better_auth_features

Browse available authentication plugins and features by category to configure production-ready authentication for modern web frameworks.

Instructions

Get a list of all available Better Auth plugins and features organized by category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional category filter: authentication, databases, integrations, or plugins

Implementation Reference

  • The main handler function that implements the list_better_auth_features tool logic. It checks the cache for features list, loads from docs if needed, filters by optional category, and returns the results in a standardized response.
    private async handleListFeatures(args?: any) {
      try {
        if (!this.featuresListCache) {
          await this.loadFeaturesFromDocs();
        }
        
        let features = this.featuresListCache || [];
        
        // Filter by category if specified
        if (args?.category) {
          features = features.filter(feature => feature.category === args.category);
        }
        
        return this.createSuccessResponse({
          total: features.length,
          features: features,
          categories: Object.keys(this.FEATURE_CATEGORIES),
        });
      } catch (error) {
        this.handleAxiosError(error, "Failed to fetch Better Auth features");
      }
    }
  • src/index.ts:134-148 (registration)
    Registration of the tool in the ListToolsRequestSchema response, defining its name, description, and input schema.
    {
      name: "list_better_auth_features",
      description: "Get a list of all available Better Auth plugins and features organized by category",
      inputSchema: {
        type: "object",
        properties: {
          category: {
            type: "string",
            description: "Optional category filter: authentication, databases, integrations, or plugins",
            enum: ["authentication", "databases", "integrations", "plugins"],
          },
        },
        required: [],
      },
    },
  • src/index.ts:223-224 (registration)
    Switch case dispatcher in CallToolRequestSchema handler that routes calls to list_better_auth_features to its handler function.
    case "list_better_auth_features":
      return await this.handleListFeatures(request.params.arguments);
  • Input schema defining the optional 'category' parameter for filtering features.
    inputSchema: {
      type: "object",
      properties: {
        category: {
          type: "string",
          description: "Optional category filter: authentication, databases, integrations, or plugins",
          enum: ["authentication", "databases", "integrations", "plugins"],
        },
      },
      required: [],
    },
  • Static feature categories and lists used by the handler and loaders to generate the complete features list.
    private readonly FEATURE_CATEGORIES = {
      authentication: [
        "email-password", "social-sign-on", "apple", "discord", "facebook", 
        "github", "google", "hugging-face", "kick", "microsoft", "slack", 
        "notion", "tiktok", "twitch", "twitter", "dropbox", "linear", 
        "linkedin", "gitlab", "reddit", "roblox", "spotify", "vk", "zoom"
      ],
      databases: [
        "mysql", "sqlite", "postgresql", "ms-sql", "drizzle", "prisma", "mongodb"
      ],
      integrations: [
        "astro", "remix", "next", "nuxt", "sveltekit", "solidstart", 
        "tanstack-start", "hono", "fastify", "express", "elysia", "nitro", "nestjs", "expo"
      ],
      plugins: [
        "two-factor", "username", "anonymous", "phone-number", "magic-link", 
        "email-otp", "passkey", "generic-oauth", "one-tap", "sign-in-with-ethereum",
        "admin", "api-key", "mcp", "organization", "enterprise", "oidc-provider", 
        "sso", "bearer", "captcha", "have-i-been-pwned", "multi-session", 
        "oauth-proxy", "one-time-token", "open-api", "jwt", "stripe", "polar", 
        "autumn-billing", "dodo-payments", "dub"
      ]
    };
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a list organized by category but doesn't mention whether this is a read-only operation, if there are rate limits, authentication requirements, pagination behavior, or what the return format looks like. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that clearly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every part of the sentence contributing directly to understanding what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one optional parameter) and high schema coverage, the description is somewhat complete but lacks critical context. Without annotations or an output schema, it doesn't address behavioral aspects like safety, performance, or return format. The description adequately covers the basic purpose but doesn't compensate for the missing structured data about tool behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the single parameter 'category' fully documented in the schema including its optional nature, type, description, and enum values. The description adds minimal value beyond the schema by implying category-based organization, but doesn't provide additional syntax or format details. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('Better Auth plugins and features'), and mentions organization by category. However, it doesn't explicitly differentiate from sibling tools like 'search_better_auth' or 'get_feature_details', which could provide similar or overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'search_better_auth' and 'get_feature_details' available, there's no indication of when this list-focused tool is preferred over search or detail-oriented tools, nor any mention of prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dabhivijay2478/better-auth-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server