One workspace, designed for the AI surfaces your team already uses.

FAOS, designed for the AI tools your team already uses.

Designed so your team can use FAOS agents and skills from the AI tools it already works in.

Where FAOS shows up

Tier 1 surfaces speak MCP natively — connect with one URL. Tier 2 surfaces use the FAOS protocol adapter. Tier 3 are on the roadmap.

Tier 1 — MCP-native

Connect with one URL
Tier 1 — MCP-native

Claude Desktop

Designed so one MCP URL brings your FAOS agents and skills into Claude Desktop.

Book a call about Claude Desktop
Tier 1 — MCP-native

Google Gemini

Designed so one MCP URL brings your FAOS agents and skills into Google Gemini.

Book a call about Google Gemini
Tier 1 — MCP-native

Cursor

Designed so one MCP URL brings your FAOS agents and skills into Cursor.

Book a call about Cursor
Tier 1 — MCP-native

Windsurf

Designed so one MCP URL brings your FAOS agents and skills into Windsurf.

Book a call about Windsurf
Tier 1 — MCP-native

Cline

Designed so one MCP URL brings your FAOS agents and skills into Cline.

Book a call about Cline
Tier 1 — MCP-native

Custom AI / SDK

Designed so one MCP URL brings your FAOS agents and skills into Custom AI / SDK.

Book a call about Custom AI / SDK

Tier 2 — protocol adapter

Bridged via FAOS adapter
Tier 2 — adapter

ChatGPT

Designed to bring your FAOS agents into ChatGPT through the FAOS protocol adapter.

Book a call about ChatGPT
Tier 2 — adapter

GitHub Copilot

Designed to bring your FAOS agents into GitHub Copilot through the FAOS protocol adapter.

Book a call about GitHub Copilot

Tier 3 — on the roadmap

On the FAOS roadmap
Roadmap

Microsoft 365 Copilot

On the FAOS roadmap

Newsletter signup
Roadmap

Perplexity Spaces

On the FAOS roadmap

Newsletter signup
Roadmap

Notion AI

On the FAOS roadmap

Newsletter signup

Stop switching tools. Bring FAOS to yours.

Bring the surface your team already uses. We will map one workflow onto it with you, agree what a useful result looks like, and show you where the agents run.