Integrations·Tools & Utilities
Kit + OpenClaw
Give your autonomous agents a live connection to Kit: managed, secure, and ready in minutes.
Kit is a platform for creators and developers to automate tasks and publish apps on the Kit App Store. On Molted, your OpenClaw agents connect to Kit through the managed MCP integration layer, with no glue code, no servers to run, and no credentials baked into containers. The agent can automate tasks and connect this tool to the rest of your stack for Kit, autonomously and within the guardrails you set.
Available actions
29 ready-to-use Kit actions.
Your OpenClaw agents can call any of these Kit actions directly through Molted's managed MCP layer. No wrappers, no boilerplate.
KIT_ADD_SUBSCRIBER_TO_FORM
Add Subscriber to Form
Tool to add a subscriber to a specific form by id. use after confirming form and subscriber ids.
KIT_CREATE_CUSTOM_FIELD
Create Custom Field
Tool to create a new custom field for subscriber data. use when you need to store extra attributes for subscribers.
KIT_CREATE_TAG
Create Tag
Tool to create a new tag in the account. use when you need a custom label to segment subscribers. use after confirming tag uniqueness to avoid duplicates…
KIT_CREATE_WEBHOOK
Create Webhook
Tool to create a new webhook subscription. use when you need subscriber or purchase event notifications.
KIT_DELETE_BROADCAST
Delete Broadcast
Tool to delete a specific broadcast. use when you need to permanently remove a broadcast by id (after confirming the id). example prompt: "delete broadcast…
KIT_DELETE_CUSTOM_FIELD
Delete Custom Field
Tool to delete a specific custom field. use after confirming the custom field id is correct. deletes the field permanently.
KIT_DELETE_SUBSCRIBER
Delete Subscriber
Tool to delete (unsubscribe) a subscriber by id. use when you need to remove a subscriber from all sequences and forms after confirming the subscriber exists.
KIT_DELETE_TAG
Delete Tag
Tool to delete a tag by id. use when you need to remove obsolete or incorrect tags after confirming the tag exists.
KIT_DELETE_WEBHOOK
Delete Webhook
Tool to delete a webhook by id. use when you want to permanently remove a webhook after confirming its id.
KIT_GET_ACCOUNT
Get Account
Tool to retrieve current account information. use after validating api key to fetch account id, plan type, primary email, and timezone details.
+ 19 more Kit actions, all callable by your agents.
How the connection works
Connect once. The agent acts.
Connecting Kit is a one-click OAuth approval: no keys to copy, and access can be revoked at any time. Everything runs through Molted's managed MCP layer, so there is no integration code to write and nothing to keep running.
01
The agent requests access
Your OpenClaw agent asks for Kit when a task needs it.
02
You approve the connection
Authorize Kit once (OAuth 2.0). Credentials are encrypted at rest and scoped to what you allow.
03
The agent acts
It reads and writes to Kit autonomously, inside your guardrails, with full audit and revocable access.
FAQ
Kit on Molted, answered.
Q.01
Can OpenClaw agents use Kit on Molted?
Yes. Kit is one of 1,000+ apps available through Molted's managed MCP integration layer. Your agent requests access, you approve the connection, and it can act on Kit straight away, with no integration code to write or maintain.
Q.02
How do I connect Kit to my agent?
Connecting Kit is a one-click OAuth approval: no keys to copy, and access can be revoked at any time.
Q.03
What can an agent actually do with Kit?
Within the permissions you grant, an agent can automate tasks and connect this tool to the rest of your stack. Have your agent use Kit to trigger actions in response to events from your other tools.
Q.04
Is my Kit data and credentials secure?
Yes. Molted never bakes credentials into the agent's pod: every connection is brokered through the managed integration layer, secrets are encrypted at rest, and access stays scoped to what you approve. You can revoke Kit access at any time.
Q.05
Do I have to run any infrastructure to use Kit?
No. Molted is the managed operating environment for autonomous agents: compute, the MCP layer, browser automation and self-healing are all handled for you. Connecting Kit is a configuration step, not an engineering project.
Q.06
Can several agents share one Kit connection?
Each instance gets its own isolated, scoped Kit connection by default, so agents stay separated. You decide which agents may reach Kit and with which permissions.
More Tools & Utilities integrations
Browse all 1,000+ integrations →
Ship agents that use Kit, not infrastructure.
Get an agent-ready environment, the managed MCP layer with 1,000+ integrations, and direct access to our engineers. Onboarding within days.