How it worksConnections and operations
Connections and operations
A connection links Mindset to one outside system and holds its credential. Operations are the single reads and writes agents make through it.
Skills for your coding agent
See it running: Trip planner
A connection links Mindset to one outside system and holds its address and credential. Mindset adds the credential to each call, so it never reaches the agent or the model. It can be an HTTP API, an MCP server, an AI model, a Postgres database, a Google Sheet or a knowledge base. What each asks for is on Connection types.
An operation is a single action on a connection, with fixed parameters, marked read or write. Operations are an agent's only way into a system, so a connection's operations are the complete list of what agents can do there.
Why it matters#
You don't write credential handling, and no prompt can get an agent to reveal a credential it never sees. You can read a connection's operations, and approve its writes, before anything runs.
The invoice exceptions agent uses the finance system (an HTTP API) and the supplier contracts knowledge base. On the finance system:
| Operation | Kind | Available to | Assigned |
|---|---|---|---|
get_invoice | Read | Agents and functions | The agent |
get_purchase_order_for_invoice | Read | Agents and functions | The agent and the comparison function |
get_supplier | Read | Functions | Nobody yet |
register_supplier_query | Write | Agents | The agent |
Read or write#
A read needs no consent. A write needs consent once per operation, which your org gives automatically by default. See Security and approval.
An HTTP API operation is a read when its method is GET and a write otherwise, unless its access was stated when it was registered. An MCP tool's access is resolved in this order:
- An admin's choice is final. Later discoveries never change it.
- The server's own hints.
destructiveHint: truemakes it a write. OtherwisereadOnlyHint: truemakes it a read, andreadOnlyHint: falsemakes it a write. - A model's reading of the tool's name and description, kept only when confident.
- Anything still unanswered is treated as a write.
Your coding agent can correct any marking. When in doubt, mark it a write.
Shared or individual#
A connection that signs in to an account is either Shared or Individual, chosen when it's set up.
- Shared: an admin signs in once, and every agent, run and user acts as that one account. The invoice exceptions agent's finance system is Shared, because everyone reads the same invoices.
- Individual: each person connects their own account, and the agent acts as whoever is asking. Two users ask the same agent "What's on my calendar tomorrow?" and each gets their own Google Calendar, never the other's.
The first time an agent needs someone's account, they get a Connect button in the conversation. After they connect, the call runs as them. They can see and disconnect their accounts under Account settings → My connections.
From registered to callable#
An agent can call an operation only when every check passes:
| Check | Passes when |
|---|---|
| Connection | It passed its connection test and is enabled |
| Lifecycle | The operation is enabled |
| Consent | Not required, or granted. A pending write is refused, not queued |
| Exposure | The operation is available to agents, which needs a description on the operation and every parameter |
| Assignment | The operation is on the agent's Resources tab, in its active version |
The first three are checked on every call, so switching one off stops the operation at once. Assignment changes with the next agent version. Separately, an Untested operation can stop a script or function going live. See Versions, testing and going live.
Limits#
- Only remote MCP servers can be connected. A local (stdio) MCP server can't.
- An HTTP API that needs an OAuth sign-in can't be connected yet, except Google Calendar, Drive and Gmail. MCP servers with OAuth sign-in work.
- A connection keeps no history. A change applies straight away, and to undo it you change it back.
To connect one, see Connect a system, or Post to Slack or send email.