silico·docsOpen Silico →

Connect your tools

Connectors let Silico's agent use your other apps — GitHub, Gmail, Slack, Stripe, Notion, and thousands more — to actually do things: read your data, draft messages, create records, look things up. They're built on MCP (the open Model Context Protocol), so anything that speaks MCP can plug in.

Opening Connectors

Click the Plug icon in the left sidebar — labeled Connected servers — to open the Connectors panel. There's a Setup guide link inside for step-by-step help at the moment you need it.

Connecting a tool

Open the panel and either pick from the catalog or add your own server.

From the catalog (one click)

The catalog has ready-made presets for popular tools, including:

GitHub · Gmail · Google Workspace · Notion · Linear · Slack · Stripe · HubSpot · PostHog · Airtable · Zapier · Google Ads · Meta Ads · Postgres

Click a card and Silico pre-fills everything it can — the connection URL, how it authenticates, and a link to that service's setup page. You just supply your credential.

Three ways to authenticate

Depending on the tool, you'll connect one of these ways:

  1. No credential — some servers just need a URL.
  2. API key — paste a key from the service. It's sent once over a secure connection, encrypted at rest, and never shown back to you.
  3. Authorize (OAuth) — click Connect and you're sent to the provider's own consent screen, then back to Silico.

Reaching thousands of apps with Zapier: connect the Zapier card once and the agent can reach the many apps Zapier supports without you setting each one up individually.

Adding a custom server

Power users can paste any MCP server URL into Add a server. Connections must be secure (https://); local and insecure URLs are rejected.

Confirming it worked

Right after connecting, you'll see "Connected — N tools discovered." That tool count is your proof the agent can now use the service. Each connected tool gets a row with a live status dot (connected / unreachable / pending).

Staying in control

Every connector has per-tool safety settings, both on by default:

  • Auto-approve reads — harmless lookups (reading a file, listing issues) run automatically.
  • Confirm writes — anything that changes something (send an email, issue a refund, post a message, delete a record) pauses for your approval first.

You can also Enable/Disable a connector (disabling keeps your credentials), Reconnect if it goes unreachable, or Delete it (which wipes its stored credentials). If a trusted connector's writes don't need review, turn off Confirm writes for it.

Good to know

  • Credentials are encrypted at rest and never displayed back after you enter them.
  • You bring your own keys — for OAuth apps, you supply your own client credentials; Silico never asks for another service's secrets it shouldn't have.
  • Reads vs. writes is the core safety line — reads flow, writes ask. That default keeps a connected agent from doing anything irreversible without you.