Read one page of application or role metadata from your own Auth0 tenant with a customer machine-to-machine app. Explicit read scopes, no client secrets, user exports, grants or tenant changes.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List clients summaries — auth0management.clients.list |
Read |
List roles summaries — auth0management.roles.list |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Auth0 Management API, then enter the issued values in the connection form below.
- In your Auth0 Dashboard, create a Machine to Machine application for this integration, authorize the Auth0 Management API and grant only read:clients and read:roles. Copy the Client ID, Client Secret and canonical tenant Domain from its Settings. In Tooluse.net Tools → Auth0 Management API → Connect with your credentials, enter those three values and save. Domain is the hostname only, such as example.us.auth0.com; URLs, custom domains and Management API Explorer test tokens are not supported. Tooluse.net derives the audience, requests only those read scopes and reuses tokens until expiry; M2M token issuance and Management API requests consume your Auth0 plan quotas. Start with page 0 and per_page 20. API output excludes client secrets and user data. Revoke the app grant or rotate its secret in Auth0 to revoke source access.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Client ID | Required |
| Client secret | Required |
| Auth0 tenant domain | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"page": 0,
"per_page": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List clients summaries — auth0management.clients.list
Read one explicit zero-based page of application IDs, names, types and first-party flags; client secrets and other settings are never requested. Requires read:clients and read:roles on the customer M2M grant. per_page is 1–100; no automatic pagination or user-controlled field selection.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.page |
integer | Required | Zero-based page number. | minimum: 0; maximum: 9007199254740991 |
query.per_page |
integer | Required | Maximum records in this page. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"query": {
"page": 0,
"per_page": 20
}
}
At most 2 provider requests per invocation; timeout: 30 seconds.
List roles summaries — auth0management.roles.list
Read one explicit zero-based page of role IDs, names and descriptions; no role membership or user export. Requires read:clients and read:roles on the customer M2M grant. per_page is 1–100; no automatic pagination or user-controlled field selection.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.page |
integer | Required | Zero-based page number. | minimum: 0; maximum: 9007199254740991 |
query.per_page |
integer | Required | Maximum records in this page. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"query": {
"page": 0,
"per_page": 20
}
}
At most 2 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.