Skip to main content

Integrations Overview

Anyy integrations connect the resident assistant to model providers, external tools, browser automation, media services, and messaging surfaces. Keep the mental model simple: Anyy owns the session, memory, policies, tools, and runtime; integrations supply transport or capability.

This section lists implemented integration entry points. Feature pages explain what the assistant can do; integration pages explain how to wire the external system safely.

Provider Integrations​

Provider integrations configure the model backends Anyy can call. A provider entry defines API mode, base URL, auth, catalog behavior, and default model ids.

Use Provider Integrations for provider configuration. Use Configuring Models for main model, auxiliary model, and fallback routing.

MCP Integrations​

MCP integrations let Anyy consume tools from external MCP servers. Each MCP server is configured, filtered, and exposed through a mcp-<server> toolset.

Use MCP Integration for the full configuration model and Use MCP Servers for a hands-on setup path.

Messaging Integrations​

Messaging integrations are the resident gateway channels: Telegram, Discord, Slack, WhatsApp, Email, SMS, DingTalk, Feishu, Weixin, QQ Bot, LINE, IRC, and Facebook Messenger.

Start from Messaging Gateway, then use the platform page for exact credentials and access policy.

Browser Integration​

Browser integration configures the managed browser MCP server and exposes Anyy-managed browser tools through browser.

Use Browser Integration for setup and doctor checks.

Media Integrations​

Media integrations cover implemented media services:

  • image generation through the media_generation toolset
  • text to speech through the tts toolset
  • audio transcription for inbound audio and voice attachments

Use Media Integrations for wiring and the feature pages for the runtime behavior of each capability.

Safety Pattern​

Use the smallest useful integration surface:

  1. Configure one provider, channel, or MCP server.
  2. Run the relevant doctor/status command.
  3. Add allowlists or tool include lists before broad exposure.
  4. Reload or restart the resident gateway after config changes.
  5. Check logs and status before adding the next integration.