Browse campaign summaries on your Mautic site with a dedicated API user.
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 campaign summaries — mautic.campaigns.list |
Read |
Get campaign summary — mautic.campaigns.get |
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 Mautic, then enter the issued values in the connection form below.
- Use your own publicly reachable root HTTPS Mautic installation. In Configuration > API Settings enable the API. Mautic recommends OAuth2; this initial connection uses its documented Basic API authentication, which an administrator must explicitly allow in the same settings. Create a dedicated Mautic user with a role limited to viewing the required campaigns; do not use an administrator password. In My tools > Mautic > Use my provider credentials, enter the root site URL, that username and password, select campaign reads and save. Credentials are encrypted in Tooluse.net and requests retain the existing public-DNS/TLS/timeout/byte-budget controls. Subdirectory installations and private-network sites are not supported here. List one page with start=0 and limit=20; explicitly increase start to continue, or get a known campaign ID. Only campaign summary metadata is returned, not events, contacts or content. This does not execute campaigns. Disconnect here and disable the dedicated user or rotate its password in Mautic when finished. No OAuth client registration or automatic renewal is claimed for this Basic connection.
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 |
|---|---|
| Mautic HTTPS site URL | Required |
| Dedicated Mautic API username | Required |
| Dedicated Mautic API password | 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": {
"start": 0,
"limit": 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 campaign summaries — mautic.campaigns.list
Read one explicit offset page of campaign IDs, names, publish flags and timestamps from your saved HTTPS site. Pass a new start value deliberately to continue. Excludes events, contacts and content; does not start or change campaigns.
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.start |
integer | Required | Zero-based offset for this explicit page. | minimum: 0; maximum: 9007199254740991 |
query.limit |
integer | Required | Campaigns requested on this page; choose 20. The response byte budget applies. | minimum: 1; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"query": {
"start": 0,
"limit": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get campaign summary — mautic.campaigns.get
Read an existing campaign’s summary without event definitions, contact details or campaign execution.
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 |
object | Required | additionalProperties: false |
|
path.campaign_id |
integer | Required | Existing campaign ID. | minimum: 1; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"path": {
"campaign_id": 3
}
}
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.