SemAgentHow-to
Connectors & MCP
The agent's power comes from the systems it connects to. This guide covers making a connection, choosing scopes and the security model.
📚
Go deeper: Agent Connectors (the full catalog, field by field) · Social media connectors · Agent Vault · Adding tools with MCP.
Google (Gmail · Calendar · Drive)
- Settings → Connectors → Google → connect via OAuth; approve only the scopes you need.
- For enterprise accounts, a service-account JSON is also supported (the test button verifies it).
- After connecting, agent tools switch on automatically:
gmail_read/search/send,calendar_*,drive_read/upload.
Databases
Enter Postgres / MySQL / MSSQL connection details; the agent runs queries with db_query.
🔐
We recommend creating a read-only user and connecting that; targets are also subject to an allow-list.
MCP: your own systems
- Settings → MCP → add your server URL.
- Tools are auto-discovered and listed; each hooks into the policy engine (approval thresholds + allow-lists apply as usual).
- If there's no ready MCP server for your internal API, writing a thin MCP layer wrapping your API is usually a one-day job.
🛡️
Security: all credentials are stored in an encrypted vault (Fernet), never sent to the LLM, and masked in logs. You can delete vault secrets from the panel at any time.
Quick troubleshooting
- Connection test fails: verify scopes and (for service-account) the JSON; check the access IP on the DB side.
- Tool returns empty: the agent doesn't invent a reason — read the diagnostic note (e.g. provider limit, empty result).
Was this page helpful? Send feedback