Read Kit (formerly ConvertKit) account and form summaries using customer OAuth with refresh/revocation. Personal V4 API keys are supported only for own-account automation. No subscriber export, sending or writes.
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 |
|---|---|
Get account summary — kit.account.get |
Read |
List form summaries — kit.forms.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 Kit (ConvertKit), then enter the issued values in the connection form below.
- For reusable integrations use OAuth: create a Kit app, enable API access, keep Secure application enabled for this confidential server flow, and register https://api.tooluse.net/v1/oauth/callback in its Redirect URIs. Fill Kit (ConvertKit) OAuth client ID and secret here, select reads, save and click Sign in to provider. Tooluse.net stores and refreshes the grant and calls Kit's revocation endpoint when disconnected. Kit currently grants the public scope rather than granular read scopes; these Tooluse.net commands remain read-only. App Store publication/approval is a separate provider process and is not completed by this form. For simple automation of your own account only, Settings → Developer → Add a new key creates a named V4 API key shown once; paste it into Personal V4 API key, leaving OAuth/access-token fields empty. Kit does not support public apps using personal keys. V3 secrets do not work here. Use the account example or forms per_page/after example; no subscribers or sends. Use a separate connection when switching credential modes.
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 |
|---|---|
| Access token (optional with OAuth) | Optional |
| Personal V4 API key (optional) | Optional |
| Kit (ConvertKit) OAuth client ID | Optional |
| Kit (ConvertKit) OAuth client secret | Optional |
| Registered OAuth redirect URI (optional) | Optional |
| Return URL after authorization | Optional |
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": {}
}'
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
Get account summary — kit.account.get
Read the connected account ID, name, plan type and creation time. Excludes account/user emails, sending addresses and other personal fields; no sends or account changes.
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.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
List form summaries — kit.forms.list
Read one cursor page of form names, type, creation time and archived state. Excludes subscriber records, embed scripts, email content and sends. Use end_cursor explicitly to request another page.
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.per_page |
integer | Required | Maximum forms in one response. | minimum: 1; maximum: 1000 |
query.after |
string | Optional | Opaque end_cursor from the preceding page; omit on the first request. | maxLength: 1000; pattern: "^[A-Za-z0-9+/=_-]+$" |
Full JSON Schema
Example input
{
"query": {
"per_page": 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.