auth0-mcp-server
Auth0 developer tools for Claude Code and any MCP-compatible AI assistant.
Decode JWTs, diagnose OAuth errors, validate tokens, and look up the right Auth0 flow — all without leaving your chat.
Installation
Add this to ~/.claude/settings.json:
{
"mcpServers": {
"auth0-local": {
"command": "uvx",
"args": ["auth0-mcp-server"]
}
}
}
Requires uv. No other setup needed — uvx fetches and runs the server automatically.
Tools
decode_token
Decode and explain a JWT. Shows the header, all claims, expiry status, and what each standard claim means. Does not verify the signature.
"Decode this token: eyJhbGci..."
validate_token
Verify a JWT's signature against an Auth0 tenant's public JWKS endpoint.
"Validate this token against my-app.us.auth0.com"
diagnose_auth_error
Explain an Auth0 or OAuth error code — what it means, why it happens, and how to fix it.
"What does invalid_grant mean?"
explain_flow
Recommend the right Auth0 / OAuth 2.0 flow for your app type and use case.
"What flow should I use for a React SPA that calls an API?"
get_tenant_config
Fetch and summarize an Auth0 tenant's OIDC discovery document — issuer, JWKS URI, supported scopes, grant types, and more.
"Show me the config for my-app.us.auth0.com"
Usage
Just describe what you need in plain English — Claude picks the right tool automatically:
- "Decode this JWT: eyJhbGci..."
- "Why am I getting server_error on my callback URL?"
- "What Auth0 flow should I use for a mobile app?"
- "Validate this token against compass-os.us.auth0.com with audience https://my-api"
Requirements
- Python 3.10+
- uv
Metadata
Release files for auth0-diagnostics-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| auth0_diagnostics_mcp-0.1.0.tar.gz | 8.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auth0_diagnostics_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.1 kB
Release files / auth0_diagnostics_mcp-0.1.0.tar.gz
| Download URL | auth0_diagnostics_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53ab3f6ad766bb49775b8f5aa8be9072a805afa3c9d89633f23f74bf29c8eb1b
|
|
BLAKE2b-256 checksum How to use checksums |
67fc6436a151e45885d6da83d4234f27df461df50117401c55b1ee9552ee1033
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.16 {"installer":{"name":"uv","version":"0.11.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / auth0_diagnostics_mcp-0.1.0-py3-none-any.whl
| Download URL | auth0_diagnostics_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
505c8d23b31d6a1eb221fe5f62465b3420c0ea5315157e2fdf0924ec209ad6a3
|
|
BLAKE2b-256 checksum How to use checksums |
cac2322c3aae9f59b59ac8d259ac6b1184861a8db46cd211461d263d98980d3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.16 {"installer":{"name":"uv","version":"0.11.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for auth0-diagnostics-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.