MCP and API

Everything you can do in Falcon, an AI assistant or your own code can do too, within your access.

What you do in Falcon is also available over MCP, the protocol AI assistants use to call tools. Every build checks that the two match.

An assistant acts as the person who connected it. It can only do what that person may do, and risky changes wait for their approval.

The same operations are available as an HTTP API. The API reference lists every operation, grouped by area, and marks the few that assistants cannot call, such as sign-in steps that need a browser.

Connect an AI assistant

In pilot

Connect an AI assistant to Falcon over MCP and sign in as yourself.

What you can do

Connect an assistant with a browser sign-in
See connected assistants and disconnect any of them

In Falcon: MCP · Connected assistants · Connect an app

In the API: authorizeMcpClient, reviewMcpConsent, listMcpConnections, revokeMcpConnection

Approve what an assistant asks to do

In pilot

When an assistant asks to do something risky, such as publish or send, it waits until you approve it in Falcon.

What you can do

Review a pending request with its details
Approve or cancel it

In Falcon: Approvals · Review an app’s request

In the API: getMcpPendingOperation, confirmMcpPendingOperation, cancelMcpPendingOperation

Company MCP policy

In pilot

Administrators decide whether people may connect assistants, and what those assistants may do.

What you can do

Allow or stop assistant connections
Limit what connected assistants may do

In Falcon: MCP

In the API: getCompanyMcpPolicy, updateCompanyMcpPolicy

HTTP API

In pilot

The same operations as MCP, over HTTP, each described with when to use it and who may call it.

What you can do

Read the API reference
Call operations as a signed-in person

In the API: getMe, getCompany

Falcon inside your own product

Coming next

Show parts of Falcon inside your own app, so your users can shape their agents there.

What you can do

Embed an agent's settings in your app

Who can do what

Who may do each thing in this guide, and what an AI assistant connected as that person may do with it. Roles are set in Company settings › Roles.

What	Who may	An assistant
Authorize an MCP connection	The browser holding the required sign-in, setup, enrollment or consent challenge; callbacks also require their bound state.	Not offered to assistants
Review an MCP connection request	The browser holding the required sign-in, setup, enrollment or consent challenge; callbacks also require their bound state.	Not offered to assistants
List your MCP connections	Anyone who can see it	Reads · needs “look”
Disconnect an MCP client	People who can edit it	Cannot be undone · needs “change settings” · waits for your approval
Read an MCP request awaiting review	The browser holding the required sign-in, setup, enrollment or consent challenge; callbacks also require their bound state.	Not offered to assistants
Confirm an MCP request	The browser holding the required sign-in, setup, enrollment or consent challenge; callbacks also require their bound state.	Not offered to assistants
Cancel an MCP request	The browser holding the required sign-in, setup, enrollment or consent challenge; callbacks also require their bound state.	Not offered to assistants
Read MCP access policy	Company administrators	Reads · needs “look”
Change MCP access policy	Company administrators	Changes · needs “change settings” · waits for your approval
Get me	Anyone who can see it	Reads · needs “look”
Get company	Anyone who can see it	Reads · needs “look”

Next: every feature