Inspect file attributes, read one UTF-8 text chunk or obtain the first directory packet over SFTP. Password and private-key authentication use one integration and the existing pinned SSH transport. Use a restricted server account; no arbitrary shell, file writes, automatic directory traversal or whole-file downloads.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Inspect file attributes — sftp.file.stat |
Read |
Read a bounded UTF-8 text chunk — sftp.file.read-text |
Read |
Read the first directory batch — sftp.directory.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 SFTP, then enter the issued values in the connection form below.
- Create a dedicated SFTP account on your server and restrict it to the intended files, preferably with a server-enforced chroot and read-only filesystem permissions. Tooluse.net does not configure the remote server or enforce a separate folder jail. In Tools → SFTP → Connect enter its public hostname, port and username. Fill exactly one of SSH password or Private key (PEM/OpenSSH), leaving the other blank; use Private key passphrase only with a protected key and install the matching public key on the server. Obtain and independently verify the SHA-256 host-key fingerprint from a trusted administrator/local console before saving. No provider API key is needed. Select only the needed reads, save and use your Tooluse.net API key for the examples. File text reads are explicit UTF-8 byte chunks (at most 32 KiB); choose UTF-8 boundaries and use nextOffset for a later call. Directory reads return only the first server packet and are marked partial unless the directory is immediately empty. Each call opens one pinned SSH connection and closes its handles; no automatic traversal, writes, arbitrary shell, background polling or retries.
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 |
|---|---|
| Public hostname | Required |
| Port | Optional |
| Username | Required |
| SSH password (leave blank with a private key) | Optional |
| Private key (PEM/OpenSSH) | Optional |
| Private key passphrase | Optional |
| Server host-key fingerprint (SHA256:base64) | 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": {
"path": "/reports/example.txt"
}
}'
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
Inspect file attributes — sftp.file.stat
Read the known path’s size, permissions, modification time and type using SFTP STAT. Optional server attributes are null when unavailable. Server account/chroot permissions govern access; no file contents or writes.
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 |
|---|---|---|---|---|
path |
string | Required | Absolute POSIX path within the dedicated server account; no dot/parent segments or backslashes. | minLength: 1; maxLength: 4096; pattern: "^/" |
Full JSON Schema
Example input
{
"path": "/reports/example.txt"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read a bounded UTF-8 text chunk — sftp.file.read-text
Read at most limitBytes from an explicit byte offset in a known file. Use nextOffset for another explicit call; eof is true only after an empty read. Offsets and chunk ends must be valid UTF-8 boundaries; binary or incomplete UTF-8 chunks fail. No whole-file download or automatic retry.
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 |
|---|---|---|---|---|
path |
string | Required | Absolute POSIX path within the dedicated server account; no dot/parent segments or backslashes. | minLength: 1; maxLength: 4096; pattern: "^/" |
offset |
integer | Required | Explicit byte offset, starting at zero. | minimum: 0; maximum: 9007199254740991 |
limitBytes |
integer | Required | Maximum bytes for this call; adapter bound is 32 KiB. | minimum: 1; maximum: 32768 |
Full JSON Schema
Example input
{
"path": "/reports/example.txt",
"offset": 0,
"limitBytes": 1024
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read the first directory batch — sftp.directory.list
Open a directory and read exactly one SFTP NAME response packet, returning at most limit entries. complete=false means the result is partial, even when fewer than limit entries are returned. Only an immediate EOF confirms an empty complete directory. No traversal, sorting or automatic pagination; handles close after each invocation.
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 |
|---|---|---|---|---|
path |
string | Required | Absolute POSIX path within the dedicated server account; no dot/parent segments or backslashes. | minLength: 1; maxLength: 4096; pattern: "^/" |
limit |
integer | Required | Maximum entries returned from the first server packet; adapter bound is 100. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"path": "/reports",
"limit": 20
}
At most 1 provider requests per invocation; timeout: 15 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.