Connectors
Connectors are how skills get real tools: Slack search, Jira tickets, Google Drive files, your own internal API. This section explains what a connector is, where connectors come from, and how employees connect their own accounts.
What a connector is
A connector is an installed integration that exposes MCP tools to skills. The Connectors screen in the console describes itself the same way: "Installed integrations that expose tools to skills. Configure OAuth, server URLs, and tool permissions in Integration settings."
A skill on its own is instructions. Attach a connector and the skill gains tools it can actually call: search messages, create a task, read a document. One connector can serve several skills, and an admin decides which of its tools each audience may use.
How tools reach your people
The chain runs connector → tools → skills → devices:
- A connector points Harriet at an MCP server (a vendor's hosted server, a sandboxed package, or your own API).
- Harriet syncs the server's tools, and an admin enables the ones people need.
- A skill attaches the connector, so the AI knows when and how to use those tools.
- Assigning the skill through a profile puts it on every enrolled device on that team.
Tool calls do not go straight from the desktop to the vendor. Each enrolled device gets a per-person proxy endpoint, and Harriet's gateway forwards the call upstream with the right credentials. That is why every call shows up in the audit log: who called which tool, from which device, with which skill, and whether it worked.
Where connectors come from
There are two routes, and you can also ask your agent to set one up from the vendor's documentation:
- The catalog. Select Add connector on the Connectors screen to browse published templates (Slack, Atlassian, Asana, and more) and install one in a short wizard. See The connector catalog.
- Custom MCP. For servers not in the catalog, use Add MCP in the Connectors ⋮ menu to open the full setup flow in Integration settings, or Create custom MCP (npx / uvx) for sandboxed package servers. See Custom MCP servers.
Looking for step-by-step install instructions? Those live in the Admin section: Installing connectors and the per-app setup guides.
In this section
Browse published templates, pick an install mode, and create a starter skill in the same flow.
Bring your own: npx / uvx packages, remote HTTP servers, and OpenAPI-backed tools.
What each install mode means at runtime, and when each one fits.
Per-user OAuth: each employee authorizes with their own account and permissions.
Control which tools a connector exposes, and how approval prompts and auditing work.
Missing tools, OAuth loops, audit log rows, and other common questions.