Integrations and connectors
How agents reach your systems, how connectors authenticate, and what a deployment needs to reach.
- How do agents access our systems?Each agent runs in an isolated environment with only the tools its runbook allows; connectors use OAuth or a scoped service credential.
- Do agents hold credentials?No. Credentials are brokered to the connector at runtime and never written into the runbook or prompt.
- Which systems can Context connect to?A catalog of 180+ integrations across data, documents, communication, CRM, ITSM, finance, and identity, plus any remote MCP server you register.
- How does a connector authenticate?Through OAuth on a hosted consent page or an API key you enter there. Connections are per agent or per user, and tokens never enter the sandbox.
- Can we add our own MCP server or internal tool?Yes. An organization admin registers a remote MCP server as a connector, users authorize it with OAuth, and its tools are discovered live.
- Does Context work with Word, Excel, and PowerPoint files?Yes. .docx, .xlsx, and .pptx files are created and edited in a full browser editor inside the workspace and download as standard Office files.
- What outbound network access does a self-hosted deployment need?The model endpoints you allow, the connector service if connectors are on, and the release proxy for online installs. Sandbox egress is a posture you set.
Still need an answer?
Tell us what you were looking for and we reply within one business day.
Contact the team →Running a security review?
Documents, controls, and the request form live in the Trust Center.
Open the Trust Center →