Read explicit pages of Company and Item summaries from your public HTTPS ERPNext/Frappe site using a dedicated user’s API key/secret and existing document permissions. Fixed fields only; no arbitrary DocTypes, customer/user records, rich descriptions, writes, automatic paging/retries or managed OAuth. Root-site HTTPS installations only.
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 companies — erpnext.companies.list |
Read |
List items — erpnext.items.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 ERPNext, then enter the issued values in the connection form below.
- In your ERPNext/Frappe site, open the User list, choose a user intended for this integration, open Settings > API Access and click Generate Keys. Copy the API key and the API secret shown once. Prefer a dedicated user whose roles permit only the Company and Item reads you need. Enter the root HTTPS site URL (for example https://example.erpnext.com), ERPNext API key and ERPNext API secret in this integration’s connection form. Root-site public HTTPS installations are supported; private-network, nonstandard-port and subdirectory sites are not supported by this subset. Save and select commands, then use your Tooluse.net API key to call the explicit page examples. The provider header is token key:secret, never your login password. Company/Item permissions and document visibility follow that user. Field selection is fixed; arbitrary DocTypes, filters, rich descriptions and writes are not exposed. No automatic pagination/retry, provider-key creation, managed OAuth or permission elevation.
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 |
|---|---|
| ERPNext HTTPS site URL | Required |
| ERPNext API key | Required |
| ERPNext API secret | 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": {
"limit_start": 0,
"limit_page_length": 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 companies — erpnext.companies.list
Read one explicit page of Company summaries from an ERPNext/Frappe site using the connected user’s permissions. Fixed field selection excludes rich descriptions, user/customer records and arbitrary DocType access. Page length is bounded to 100 by this adapter.
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.limit_start |
integer | Required | Zero-based page offset. | minimum: 0; maximum: 1000000000 |
query.limit_page_length |
integer | Required | Requested page length; adapter bounds this to 100. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"query": {
"limit_start": 0,
"limit_page_length": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List items — erpnext.items.list
Read one explicit page of Item summaries from an ERPNext/Frappe site using the connected user’s permissions. Fixed field selection excludes rich descriptions, user/customer records and arbitrary DocType access. Page length is bounded to 100 by this adapter.
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.limit_start |
integer | Required | Zero-based page offset. | minimum: 0; maximum: 1000000000 |
query.limit_page_length |
integer | Required | Requested page length; adapter bounds this to 100. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"query": {
"limit_start": 0,
"limit_page_length": 20
}
}
At most 1 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.