Corey Corey
Hire Corey
How it works Use cases Guides Build log What Corey builds Docs Hire Corey

Custom integrations

Corey can connect to additional tools and services through MCP (Model Context Protocol), so it can do the work that is specific to your business. If a tool speaks MCP, Corey can use it - which means the set of things Corey can do grows with what you connect.

Corey is not limited to a fixed list. Everything it does runs through MCP (Model Context Protocol), the open standard for connecting tools to an AI agent. Because Corey speaks MCP, you can connect additional tools and services and Corey can use them like any other - which is how it adapts to the way your business actually runs.

How connecting works

If a tool offers an MCP server, you can connect it to Corey. Once connected, Corey can use it inside a job just like its built-in tools - reading, preparing and acting within the same approval rules.

This is the same mechanism behind every category on this page: file, web, communication, finance and calendar tools are all reached over MCP. Custom integrations simply extend that to the tools specific to you.

The same rules apply

A connected tool does not get a free pass. The approval model covers everything:

  • read-only steps run freely
  • anything that writes, sends, spends or is irreversible waits for your approval

So however you extend Corey, you keep the same control. What changes is the range of work Corey can do; what stays is your sign-off on anything that matters.

Why this matters

Most businesses run on a particular mix of tools. Custom integrations mean Corey can meet you there rather than asking you to change how you work. The more you connect, the more of your actual workflow Corey can take on - and because it is all MCP, adding a tool does not change the way you work with Corey or the guardrails you have set.

See how Corey works for the bigger picture, and best practices for setting guardrails on connected tools.

Related

Corey tools overview Scheduling and calendar tools How Corey works

Questions, answered

MCP (Model Context Protocol) is the open standard Corey uses to talk to tools. If a tool or service offers an MCP server, Corey can use it - which is what lets the set of things Corey can do grow with what you connect, rather than being fixed.
Any tool or service that speaks MCP. That is how Corey adapts to the way your business actually runs - the work it can do is shaped by the tools you bring, not limited to a built-in list.
Yes. The approval model applies to every tool, connected or built-in. Read-only steps run freely; anything that writes, sends, spends or is irreversible waits for your approval, no matter which tool performs it.