Triggers
Triggers overview
Add data-configured payment conditions to discovered MCP tools.
A trigger defines when a discovered tool requires payment. Until you configure and publish a trigger, the MCP server can remain in observe-only use.
Triggers can support patterns such as:
- Payment whenever a selected tool is called.
- An included usage allowance followed by payment.
- A condition based on supported tool input or usage state.
- A one-time or recurring payment offer.
The available fields depend on the current trigger editor and payment setup.
A clear trigger has three parts
- When: the tool and condition that cause the rule to match.
- Payment: the amount, currency, and payment type.
- Result: the message and access outcome users should understand.
Begin with Design a trigger, then validate both matching and non-matching cases before publication.
If you want help from your preferred AI assistant, follow Use your own AI to plan a trigger. Its public proposal format is a planning aid for human review, not an import or publishing API.