---
title: What agents connect to by default
description: A logged-in venom connects every Venom product's MCP server (Notes, Tasks, People, Funnel and the rest) with deferred tools; how to narrow or turn them off, and the credential sessions Venom Cloud starts get.
section: cloud
order: 247
audience: [user, operator, agent]
sources: [packages/harness/src/compat/venom-products.ts, packages/harness/src/compat/mcp.ts, packages/harness/src/harness.ts, cli/src/library-command.ts, packages/harness-server/src/session.ts, packages/harness-server/openapi.yaml, services/nodejs-cloud/lib/computers/run-mcp.ts, services/nodejs-cloud/lib/computers/agent-runs.ts, services/nodejs-cloud/lib/mcp/products.ts]
features: []
---

Once you're signed in with `venom cloud login`, every venom session (the terminal, `venom serve`, `venom acp`) is
connected to every Venom product's MCP server, so an agent can look things up in your workspace while it works: a note
in Notes, an issue in Tasks, a person in People, a deal in Funnel, a support conversation, a flag, an incident.

## What gets connected

One server per product, at `/workspace/mcp/<product>` on your Venom Cloud, with your login's key as the bearer token.
The table in [Workspace MCP](/docs/cloud/workspace-mcp) lists the products and their tools.

| Server name | Product |
|---|---|
| `globe` | Notes |
| `tasks` | Issues, projects, cycles |
| `calendar` | Your calendar and booking pages |
| `venom-flags` | Feature flags |
| `venom-forms` | Forms and responses |
| `venom-incidents` | Errors, incidents, on-call |
| `venom-experiments` | Experiments |
| `venom-people` | People and relationships |
| `venom-funnel` | Deals and pipelines |
| `venom-support` | The support inbox |
| `venom-chat` | Team chat |
| `venom-status` | The status page |
| `venom-comms` | Messages and calls |
| `venom-admin` | Console admin |
| `venom-org` | Teams and members |
| `venom-computers` | Agents' computers |

`globe`, `tasks` and `calendar` keep the names they had when they were the only three, so permission rules you wrote
for them (`mcp__globe__*`) still match. The others use the same `venom-<product>` names as the cloud's own connect
commands, so they don't collide with a server of yours called `chat` or `status`.

**Your prompt doesn't grow by a product's worth of tools.** Every one of these servers is deferred: its tools are not
declared to the model. The agent finds them with `tool_search` when it needs one, and the system prompt only names
them, in one section capped at 3,000 characters.

**What an agent can do is what you can do.** The key is yours, so each product checks your role, exactly as it does for
any MCP client. An MCP tool still asks before it runs, in every permission mode but yolo.

## Turning them off

| Setting | Effect |
|---|---|
| `VENOM_CLOUD_MCP=off` | No Venom product servers at all. |
| `VENOM_CLOUD_MCP=tasks,globe,people` | Only these (product names or server names). |
| `VENOM_MCP_<PRODUCT>=off` | Leaves one out, for example `VENOM_MCP_ADMIN=off`, `VENOM_MCP_PEOPLE=off` or `VENOM_MCP_EXPERIMENTS=off` (`VENOM_MCP_EXP` works too). |
| `VENOM_GLOBE_MCP=off`, `VENOM_TASKS_MCP=off`, `VENOM_CALENDAR_MCP=off` | The older switches for those three; they still work. |

Two more things can leave a product out:

- An MCP server of your own with the same name takes its place.
- If your organisation's policy has an MCP allowlist (`mcp.allow`), only the names it lists are connected. Add
  `venom-people` to it to let sessions use People, for example.

Without a login nothing is connected, and nothing is sent anywhere.

## Sessions Venom Cloud starts

When Venom Cloud starts a session itself, the session gets the same product servers, but not with the key of whoever is
logged in on the daemon. The cloud mints a key for it. It does this for:

- an agent's run on its computer (from a Chat mention, a delegated issue or a routine);
- a chat in [Venom Agents](/docs/agents.md), a code chat or a computer chat.

The key:

- is a personal key of the person who asked (for a chat, the member whose chat it is), so the agent can only read and
  change what that person can.
- For a computer run, expires within a day and is revoked when the run ends. For a chat, expires within 30 days (chats
  stay open for weeks and a running session can't swap its key) and is revoked when the chat is archived, its session
  ends, or its session fails to start.
- is revoked when its member leaves the organisation.
- Both show in the audit log (`key.create` and `key.revoke`, actor `system:computers` for runs, `system:agents` for
  chats).
- goes to the daemon in the create-session body (`venomMcp`, below) and from there only into the servers'
  `Authorization` header. It is never stored on the run or the chat, never in the session's state or events, and
  never in the model's context.

A run nobody asked for (a Tasks delegation with no person behind it, a routine whose owner left) gets no key and no
product servers.

A daemon running a venom from before this change refuses the field; the cloud then starts the session without it, as
it did before.

### `venomMcp` on POST /v1/sessions

Any client of `venom serve` can do the same. `venomMcp` in the create body replaces the host's own login for that
session:

```json
{
  "cwd": "/work/repo",
  "venomMcp": { "url": "https://cloud.usevenom.dev", "key": "vck_…", "products": ["tasks", "people"] }
}
```

`url` is https (http only to loopback) with no credentials in it, `key` is the bearer token, and `products` is optional
(all by default). `"venomMcp": false` connects none, even on a logged-in host.
