Integrations

Plug AGI into your 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, CLI, and VS Code. 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, SSE, and streamable HTTP transports are all supported.

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, CLI, and VS Code. Or any OpenAI-compatible endpoint.

What's wired today

The honest inventory.

Providers	10+ providers across cloud APIs and local runtimes. BYOK on Desktop, CLI, and VS Code. Pay providers directly.
Local runtimes	Ollama, LM Studio, llama.cpp, and vLLM on Desktop. Free, offline-capable after setup, no account required. CLI runtime support is documented separately.
MCP transports	stdio, SSE, and streamable HTTP are all supported.
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: date to be announced

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