Routines in Claude Code can't use Claude.ai Connectors (e.g., Composio, Gmail, LinkedIn)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I configured the Composio connector in my Claude.ai account (Settings → Connectors), with LinkedIn enabled. It works perfectly in claude.ai chat — I can say "post this to LinkedIn via Composio" and it executes end-to-end.

However, when I try to do the same thing inside a Routine running in Claude Code on the web, Composio is not reachable:

• /mcp returns "isn't available in this environment"
• Adding a project-level .mcp.json pointing at https://connect.composio.dev/mcp has no effect in the web-hosted Claude Code runtime
• There appears to be no workspace/scope toggle in the Connectors UI to expose a connector to Claude Code

This means Routines can't automate any workflow that depends on my personal integrations — which is exactly the kind of automation Routines seem designed for. A Routine that drafts a LinkedIn post from current news, for example, has to stop at the draft; a human then has to copy/paste into claude.ai chat to actually publish.

Environment: Claude Code on the web, workspace: MySkillPersonal, model: Opus 4.7.

Proposed Solution

Please bridge Claude.ai Connectors into Claude Code's Routine runtime, or add a per-connector "enable for Claude Code workspaces" toggle. Either would unlock a large class of useful Routines that depend on personal integrations like Composio, Gmail, LinkedIn, etc.

Alternative Solutions

Currently there is no known workaround — the user must manually switch to claude.ai chat to execute any action that requires a Connector, defeating the purpose of Routines automation.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

A Routine set up to: (1) fetch today's top tech news, (2) draft a LinkedIn post summarizing it, (3) publish it via the Composio LinkedIn connector. Steps 1 and 2 work. Step 3 fails because the Composio connector configured in claude.ai Settings → Connectors is not accessible inside Claude Code's Routine runtime. The user must manually copy the draft into claude.ai chat and re-invoke Composio there.

Additional Context

_No response_