Sym
Sym is Insym's company hub: one secure connection that lets the AI assistants Insym works with (Claude, ChatGPT, Gemini, Codex) and Insym's own software act in the services the business runs on. Ask in plain words, from any of them, and Sym carries it out with the right access.
What it connects
Insym's work Google account. Drive, Gmail, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts and Apps Script: find, read, write, share, send.
Insym's servers and apps. What is running, health, logs, deployments; deploy, roll back and change, after a person says yes.
Insym's own tools, such as wilo, joining the same connection, each with its own access rules.
How it works
- Bundles. Each project or person gets a bundle: the set of tools it may use, at its own address
(
/b/<bundle>/mcp). - Keys. Each consumer has its own key that opens only its bundles. Chat apps sign in once on Sym's key page; command-line tools send the key in a header.
- Guides on demand. Sym tells an assistant what is there, and hands it the guide for a service with
the
sym-guidetool only when a task needs it. - Every call is logged (time, caller, tool, result; never contents) and rate-limited. Writes that reach outside, like deploys, mail or sharing, are confirmed with the person first.
Connect
claude mcp add --transport http sym \
https://sym.insym.io/b/<bundle>/mcp \
--header 'Authorization: Bearer ${SYM_KEY}'[mcp_servers.sym]
url = "https://sym.insym.io/b/<bundle>/mcp"
bearer_token_env_var = "SYM_KEY"Add a custom connector (Gemini: Developer Mode) with the
address https://sym.insym.io/b/<bundle>/mcp, choose OAuth, and paste your key on Sym's page once.
Access is for Insym staff and Insym software only; there is no public sign-up. Questions: contact@insym.io.
Policies
How Google user data is accessed, used, stored and deleted: the privacy policy. Rules of use: the terms of service. Service status: /health.