# Claude connectors

Source: https://routineos.org/learn/claude-connectors

> Claude connectors give routines access to mail, calendars, docs and more. How they work in cloud runs, which can write, and how RoutineOS gates every write.

Learn

# Claude connectors, and what a routine can do with them.

A Claude connector is a link from your Claude account to another service, such as mail, a calendar or a docs tool. In a scheduled task it is how a run reads from and writes to that service without holding a password. This guide says how that works, which connectors can write, and how RoutineOS puts an approval in front of every write.

[Get started](https://routineos.org/#start)[Add the docs connector](#custom)

docs-statedconnectors and MCP

What a connector is

## What are Claude connectors?

A connector is an integration on a person's claude.ai account, built on the Model Context Protocol (MCP). An MCP server is any service that speaks MCP, and a connector is one way of adding one.

You sign in to the service once on claude.ai. After that, no key reaches the run, your repository or the Desk. Connector traffic also goes through Anthropic's servers, not the run's own network, so the run's network allowlist does not block it.

Anthropic keeps a directory of connectors, and you can add a custom one. A custom remote connector must be reachable from the public internet. See Anthropic's [help article on connectors](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities) and the [connectors directory](https://claude.com/connectors). We do not quote a count, because it changes.

Docs-stated. Source: [Connectors and MCP](https://docs.routineos.org/infrastructure/connectors-and-mcp) in the RoutineOS docs, and Anthropic's [scheduled tasks documentation](https://code.claude.com/docs/en/web-scheduled-tasks), read on 2026-10-30.

In a scheduled task

## Every connector is included by default, and can write

When you create a scheduled task, all of your currently connected connectors are included by default. Anthropic's docs say Claude can use an included connector during a run, including writes. Remove any the task does not need.

What a connector does appears as you. A Slack message or a calendar change goes out from your linked account, not from a bot.

Servers added on your own machine with `claude mcp add` live on your machine, not your account, so a cloud task cannot see them. Add the server as a connector, or, for a task with one repository, declare it in a committed `.mcp.json`.

**Heads up**Leaving every connector on is the common mistake. A routine that only needs to read mail should not also be able to post to Slack.

Writes

## How RoutineOS gates every connector write

RoutineOS treats every write connector as a send. Each connector a routine uses is declared with a direction, read or write. Lint refuses a write connector that has no gate. The permission screen lists each connector and you approve the list before anything is created.

A gate holds any send, post or delete until a named person approves. The prompt also forbids sends that are not on the approved list. That is a prompt rule, not a runtime guarantee, because one pilot saw a run use a send tool the approved list did not include. Read more on [approvals](https://routineos.org/concepts/approvals).

| Connector | What we saw | How we know |
|---|---|---|
| Email gate transport | Approval requests over email worked end to end in a pilot. | pilot-verified |
| Slack send | Needed the Slack connector's tool policy set to "Ask for approval" on claude.ai before a send tool appeared in the run. | pilot-verified |
| Gmail send approval | Anthropic's help article says send actions need approval by default. A pilot send from an unattended run went through with no policy change. The two do not obviously agree, so test it in your own account. | docs-stated and pilot-verified |

Approve-then-send on the Desk has not been piloted end to end. Email and Slack as transports have.

Custom connector

## Add a Claude custom connector: the RoutineOS docs server

The RoutineOS docs and template catalog are a read-only MCP server. No account and no sign in. It is a handy worked example of adding a custom connector.

1. **Open Customize, then Connectors**On Claude on the web or Claude Desktop, choose **+ Add**, then **Add custom connector**.
2. **Name it and paste the address**Name it `RoutineOS` and paste `https://docs.routineos.org/api/mcp`.
3. **Choose No sign in, then Add**Turn it on in a chat from **+ > Connectors**.
4. **Ask it something**For example, "search the RoutineOS docs for gates".

Free plans allow one custom connector. On Team and Enterprise an owner adds it under Organization settings, Connectors (RoutineOS README). In Claude Code, installing the plugin connects it for you, or run the line below.

`claude mcp add --transport http routineos https://docs.routineos.org/api/mcp`

Add `--scope project` to commit it to the repo's `.mcp.json`, so cloud scheduled routines on that repo get it too.

By template

## Connectors each RoutineOS template uses

Taken from the catalog. Read means it only looks. Write means it can send or publish, so it sits behind a gate. Built-in means web search or fetch, with nothing to connect.

| Template | Needs | Optional |
|---|---|---|
| [Jobs watch](https://routineos.org/templates/jobs-watch) piloted | Web search, Web fetch (built in) | Mail (write) |
| [Watch](https://routineos.org/templates/watch) piloted | Web fetch (built in) | None |
| [Inbox triage](https://routineos.org/templates/inbox-triage) | Mail (read) | Mail for approvals, Mail (send), both write |
| [Meeting brief](https://routineos.org/templates/meeting-brief) | Calendar (read), Web search, Web fetch | None |
| [Invoice exceptions](https://routineos.org/templates/invoice-exceptions) | Invoice mailbox or folder (read) | None |
| [Candidate shortlist](https://routineos.org/templates/candidate-shortlist) | Applicant tracking system (read, via MCP) | None |
| [Content calendar](https://routineos.org/templates/content-calendar) | Web search, Web fetch | Mail for approvals, Publishing platform (via MCP), both write |
| Engineering digest | Code host (read) | None |
| Support gap digest | Help desk (read, via MCP), Web fetch | None |
| Weekly marketing report | Analytics and ad platforms (read, via MCP) | Web fetch |

Only Jobs watch and Watch are piloted. The other templates have passed validation, not a real run. See all on [templates](https://routineos.org/templates).

## Put a gate in front of every write

Install the plugin in Claude Code and start from a template. Free (MIT). Needs a paid Claude plan.

[Get started](https://routineos.org/#start)[Read about the docs MCP](https://docs.routineos.org/mcp)