Integrations

Plug AGI intoyour stack.

Three patterns connect AGI to the tools you already use: MCP plugins for the agent, the native messaging bridge between Chrome and Desktop, and BYOK provider keys on Desktop and CLI. Every connection runs behind explicit, visible permissions.

Browse Apps & Connectors See Providers

The three patterns

How the pieces connect.

ToolsMCP pluginsMount Model Context Protocol servers and scope their access. stdio is the shipped transport; SSE and streamable HTTP are planned.

BridgeNative messaging bridgeThe Chrome side panel pairs with Desktop on localhost:8787. The browser captures intent. Desktop runs the model and the tool calls.

KeysProvider BYOKBring keys for Anthropic, OpenAI, Google, xAI, DeepSeek, Perplexity, Qwen, Moonshot, or Zhipu on Desktop and CLI. Or any OpenAI-compatible endpoint.

What's wired today

The honest inventory.

Providers	10+ providers across cloud APIs and local runtimes. BYOK on Desktop and CLI. Pay providers directly.
Local runtimes	Ollama and LM Studio. Free, offline-capable, no account required.
MCP transports	stdio shipped first. SSE and streamable HTTP are planned for the release path.
Native messaging	Chrome MV3 extension ↔ Desktop on localhost:8787. Extension availability tracks the Desktop release.
Editor	VS Code extension with the @agi chat participant. Developer preview. Not yet listed on the marketplace.

Public launch: July 12, 2026

Connect one tool, then the next.

Start with a provider key or a local runtime, add MCP plugins as the work demands, and keep every permission visible.

See Providers Read API Docs

AGI