Anything becomes an endpoint
Publish a workflow, an agent, a connector action or an action on your data as a REST endpoint, with its own path, method and parameters.
APIs & MCP
Publish what you build as APIs and MCP servers.
Everything you build on RocketKind can be called from outside it: by your own apps over REST, or by AI assistants over MCP, with the same keys, limits and audit.
# one toolkit = one MCP server
claude mcp add \
--transport http \
--header "Authorization: Bearer <access key>" \
support-tools \
https://<host>/v1/mcp/support-tools
# each workflow becomes a tool; its inputs
# come from the workflow itselfTools: lookup_order · issue_refund · escalate_ticket
APIs
Versioned REST APIs, without writing a service.
Versioned like software
Work on a draft, publish a version and set it live. Callers keep working while you change the next one.
Your choice of sign-in
API keys, basic auth, personal access keys or JWTs from your own identity provider.
Limits on every key
Rate limits, quotas, concurrency caps, timeouts, request validation, IP allowlists, allowed origins and model budgets.
MCP
Tools for every assistant your team uses.
Your own MCP servers
Group workflows, agents and actions into a toolkit, and each toolkit is an MCP server any assistant can connect to.
Schemas you never write
Each tool’s inputs come from what it calls, so they stay right when the workflow behind it changes.
Drive the platform from your editor
Connect Claude Code, Cursor, Codex, GitHub Copilot or Antigravity to RocketKind and build workflows and agents from there, with one plugin they all install.
- Claude Code
- Cursor
- Codex
- GitHub Copilot
- Antigravity
Forms anyone can open
Publish a form as a public page or embed it in your own site, limited to the origins you list.