IT

Plugs into everything your agency runs on

Slack, Stripe, Google, Zapier, and the rest of your stack — plus MCP and a REST API to connect tools like Notion, Calendly, and GoHighLevel.

Kyo’s MCP and API support

Built for how agencies work

Kyo is the future of agency integrations.

Competitor intelligence in Kyo AI Ark and Apollo enrichment in Kyo

More in IT

The details that round it out.

REST API

Read and write deals, people, companies, tasks, and more over HTTPS.

CLI

Your whole workspace from the terminal — scriptable, JSON-first.

Zapier & webhooks

Automations can trigger any Zap — 6,000+ apps — and forms flow in from Typeform, Tally, and Google Forms.

FAQs

Frequently asked questions about IT

Slack, Stripe, Google (Docs, Sheets, Calendar), Lemlist, Instantly, Granola, Miro, Typeform, Apollo, AI Ark, Claude, ChatGPT, X, Higgsfield, HeyGen, ElevenLabs, Zapier, and 10+ others. If a tool isn’t natively supported, the REST API or Zapier covers it.

Yes. Kyo ships an MCP server so AI agents like Claude and Cursor can read and write your workspace directly: creating tasks, updating CRM pipelines, pulling project context, and posting updates with real data. It’s not a read-only feed. Agents can take real action inside Kyo.

OAuth 2.0 with authorisation code and PKCE. There’s no API key or client secret to manage for public apps. AI tools, browser extensions, and custom integrations can authenticate securely without storing sensitive credentials on the client side.

Every workspace is isolated, and all data is transmitted over HTTPS. API tokens and integrations are scoped to your workspace and run through the same permission model as team members. An integration or AI agent can never access more data than the role it’s been assigned allows.

Yes. Kyo connects to Zapier, so any app Zapier supports (6,000+) can send data to or receive data from Kyo through webhooks. For more custom workflows, the REST API and CLI handle anything Zapier doesn’t cover.

Yes. Every integration and API token is scoped to a workspace, and AI agent access runs through the same per-feature permissions as people. An agent or integration can never see more data than the role it’s assigned. Same security model, same controls, whether it’s a person or a bot.

Explore the rest of Kyo

The next era of agency operations
runs on Kyo.