Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.npmjs.com/package/@auth0/auth0-mcp-server below:

@auth0/auth0-mcp-server - npm

📚 Documentation • 🚀 Getting Started • 💻 Supported Tools • 💬 Feedback

MCP (Model Context Protocol) is an open protocol introduced by Anthropic that standardizes how large language models communicate with external tools, resources or remote services.

⚠ Beta Feature Notice: This feature is currently in Beta. Please use with caution when calling tools, as functionality may be unstable or subject to change.

The Auth0 MCP Server integrates with LLMs and AI agents, allowing you to perform various Auth0 management operations using natural language. For instance, you could simply ask Claude to perform Auth0 management operations:

• Create a new Auth0 app and get the domain and client ID

• Create and deploy a new Auth0 action to generate a JWT token

• Could you check Auth0 logs for logins from 192.108.92.3 IP address?

Prerequisites:

• Node.js v18 or higher
• Claude Desktop or any other MCP Client
• Auth0 account with appropriate permissions

Install Auth0 MCP Server and configure it to work with your preferred MCP client. The --tools parameter specifies which tools should be available (defaults to * if not provided).

Claude Desktop with all tools

npx @auth0/auth0-mcp-server init

Claude Desktop with read-only tools

npx @auth0/auth0-mcp-server init --tools 'auth0_list_*,auth0_get_*'

Windsurf

npx @auth0/auth0-mcp-server init --client windsurf

Cursor

npx @auth0/auth0-mcp-server init --client cursor

With limited tools access

npx @auth0/auth0-mcp-server init --client cursor --tools 'auth0_list_applications,auth0_get_application'

Other MCP Clients

To use Auth0 MCP Server with any other MCP Client, you can manually add this configuration to the client and restart for changes to take effect:

{
  "mcpServers": {
    "auth0": {
      "command": "npx",
      "args": ["-y", "@auth0/auth0-mcp-server", "run"],
      "capabilities": ["tools"],
      "env": {
        "DEBUG": "auth0-mcp"
      }
    }
  }
}

You can add --tools '<pattern>' to the args array to control which tools are available. See Security Best Practices for recommended patterns.

Your browser will automatically open to initiate the OAuth 2.0 device authorization flow. Log into your Auth0 account and grant the requested permissions.

[!NOTE] Credentials are securely stored in your system's keychain. You can optionally verify storage through your keychain management tool. Checkout Authentication for more info.

Restart your MCP Client(Claude, Windsurf, Cursor, etc...) and ask it to help you manage your Auth0 tenant

The Auth0 MCP Server provides the following tools for Claude to interact with your Auth0 tenant:

When configuring the Auth0 MCP Server, it's important to follow security best practices by limiting tool access based on your specific needs. The server provides flexible configuration options that let you control which tools AI assistants can access.

You can easily restrict tool access using the --tools flag when starting the server:

# Enable only read-only operations
npx @auth0/auth0-mcp-server run --tools 'auth0_list_*,auth0_get_*'

# Limit to just application-related tools
npx @auth0/auth0-mcp-server run --tools 'auth0_*_application*'

# Restrict to only log viewing capabilities
npx @auth0/auth0-mcp-server run --tools 'auth0_list_logs,auth0_get_log'

# Run the server with all tools enabled
npx @auth0/auth0-mcp-server run --tools '*'

This approach offers several important benefits:

1. Enhanced Security: By limiting available tools to only what's needed, you reduce the potential attack surface and prevent unintended modifications to your Auth0 tenant.

2. Better Performance: Providing fewer tools to AI assistants actually improves performance. When models have access to many tools, they use more of their context window to reason about which tools to use. With a focused set of tools, you'll get faster and more relevant responses.

3. Resource-Based Access Control: You can configure different instances of the MCP server with different tool sets based on specific needs - development environments might need full access, while production environments could be limited to read operations only.

4. Simplified Auditing: With limited tools, it's easier to track which operations were performed through the AI assistant.

For most use cases, start with the minimum set of tools needed and add more only when required. This follows the principle of least privilege - a fundamental security best practice.

The Auth0 MCP Server implements the Model Context Protocol, allowing Claude to:

1. Request a list of available Auth0 tools
2. Call specific tools with parameters
3. Receive structured responses from the Auth0 Management API

The server handles authentication, request validation, and secure communication with the Auth0 Management API.

[!NOTE] The server operates as a local process that connects to Claude Desktop, enabling secure communication without exposing your Auth0 credentials.

The Auth0 MCP Server uses the Auth0 Management API and requires authentication to access your Auth0 tenant.

To authenticate the MCP Server:

npx @auth0/auth0-mcp-server init

This will start the device authorization flow, allowing you to log in to your Auth0 account and select the tenant you want to use.

[!IMPORTANT] The init command needs to be run whenever:

• You're setting up the MCP Server for the first time
• You've logged out from a previous session
• You want to switch to a different tenant
• Your token has expired

To see information about your current authentication session:

npx @auth0/auth0-mcp-server session

For security best practices, always use the logout command when you're done with a session:

npx @auth0/auth0-mcp-server logout

This ensures your authentication tokens are properly removed from the system keychain.

The server uses OAuth 2.0 device authorization flow for secure authentication with Auth0. Your credentials are stored securely in your system's keychain and are never exposed in plain text.

When encountering issues with the Auth0 MCP Server, several troubleshooting options are available to help diagnose and resolve problems.

Start troubleshooting by exploring all available commands and options:

npx @auth0/auth0-mcp-server help

• More detailed logging
• Enable by setting environment variable: export DEBUG=auth0-mcp

[!TIP] Debug mode is particularly useful when troubleshooting connection or authentication issues.

The server provides an interactive scope selection interface during initialization:

• Interactive Selection: Navigate with arrow keys and toggle selections with spacebar

• No Default Scopes: By default, no scopes are selected for maximum security

• Glob Pattern Support: Quickly select multiple related scopes with patterns:

  # Select all read scopes
  npx @auth0/auth0-mcp-server init --scopes 'read:*'
  
  # Select multiple scope patterns (comma-separated)
  npx @auth0/auth0-mcp-server init --scopes 'read:*,create:clients,update:actions'

[!NOTE] Selected scopes determine what operations the MCP server can perform on your Auth0 tenant.

To use Auth0 MCP Server with any other MCP Client, you can add this configuration to the client and restart for changes to take effect:

{
  "mcpServers": {
    "auth0": {
      "command": "npx",
      "args": ["-y", "@auth0/auth0-mcp-server", "run"],
      "capabilities": ["tools"],
      "env": {
        "DEBUG": "auth0-mcp"
      }
    }
  }
}

[!NOTE]
You can manually update if needed or if any unexpected errors occur during the npx init command.

1. Authentication Failures

   • Ensure you have the correct permissions in your Auth0 tenant
   • Try re-initializing with npx @auth0/auth0-mcp-server init

2. Claude Can't Connect to the Server

   • Restart Claude Desktop after installation
   • Check that the server is running with ps aux | grep auth0-mcp

3. API Errors or Permission Issues

   • Enable debug mode with export DEBUG=auth0-mcp
   • Check your Auth0 token permissions and expiration
   • Reinitialize with specific scopes: npx @auth0/auth0-mcp-server init --scopes 'read:*,update:*,create:*'
   • If a specific operation fails, you may be missing the required scope

[!TIP] Most connection issues can be resolved by restarting both the server and Claude Desktop.

Enable debug mode to view detailed logs:

Get detailed MCP Client logs from Claude Desktop:

# Follow logs in real-time
tail -n 20 -F ~/Library/Logs/Claude/mcp*.log

For advanced troubleshooting, use the MCP Inspector:

npx @modelcontextprotocol/inspector -e DEBUG='auth0-mcp' @auth0/auth0-mcp-server run

For detailed MCP Server logs, run the server in debug mode:

DEBUG=auth0-mcp npx @auth0/auth0-mcp-server run

# Clone the repository
git clone https://github.com/auth0/auth0-mcp-server.git
cd auth0-mcp-server

# Install dependencies
npm install

# Build the project
npm run build

# Initiate device auth flow
npx . init

# Configure your MCP client(Claude Desktop) with MCP server path
npm run local-setup

# Restart MCP client, in this case claude desktop app

[!NOTE] This server requires Node.js v18 or higher.

The Auth0 MCP Server prioritizes security:

• Credentials are stored in the system's secure keychain
• No sensitive information is stored in plain text
• Authentication uses OAuth 2.0 device authorization flow
• No permissions (scopes) are requested by default
• Interactive scope selection allows you to choose exactly which permissions to grant
• Support for glob patterns to quickly select related scopes (e.g., read:*)
• Easy token removal via logout command when no longer needed

[!IMPORTANT] For security best practices, always use npx @auth0/auth0-mcp-server logout when you're done with a session or switching between tenants. This ensures your authentication tokens are properly removed from the system keychain.

[!CAUTION] Always review the permissions requested during the authentication process to ensure they align with your security requirements.

Anonymized data points are collected during the use of this MCP server. This data includes the MCP version, operating system, timestamp, and other technical details that do not personally identify you.

Auth0 uses this data to better understand the usage of this tool to prioritize the features, enhancements and fixes that matter most to our users.

To opt-out of this collection, set the AUTH0_MCP_ANALYTICS environment variable to false.

We appreciate feedback and contributions to this project! Before you get started, please see:

• Auth0's general contribution guidelines
• Auth0's code of conduct guidelines

To provide feedback or report a bug, please raise an issue on our issue tracker.

Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.

This project is licensed under the MIT license. See the LICENSE file for more info.

Auth0 is an easy to implement, adaptable authentication and authorization platform. To learn more checkout Why Auth0?

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4