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:
/mcpreturns "isn't available in this environment"- Adding a project-level
.mcp.jsonpointing 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_
Showing cached comments. Read the full discussion on GitHub ↗
13 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This issue is related but not a duplicate of #51189, #44796, or #41044.
allowed_toolsUI/plumbing. Here, the problem is that Claude.ai Connectors (e.g. Composio/LinkedIn configured in claude.ai Settings → Connectors) are not exposed to the Claude Code Routine runtime at all, even though they work in claude.ai chat.The requested change here is a connector-level bridge or toggle ("enable for Claude Code workspaces/Routines") so account-level Connectors become usable inside web Routines, which none of the linked issues cover.
Confirming this still affects the
/scheduleskill as of 2026-04-27, and adding a more specific data point that may help narrow the root cause.Environment: Claude Code CLI (Mac), Max subscription, via the
/scheduleskill which fetches the connector list from the routines API.Observed behaviour:
claude.ai/customize/connectors: Amplitude and Sentrymcp__sentry__*tools are available and callable in the current session)/schedulefetches the connector list for routines, only Amplitude is returned — Sentry is absentWhy this is different from the original report:
The original report describes all connectors being unavailable in routines. Here, one connector (Amplitude) is correctly enumerated and can be attached to routines, while another (Sentry) is silently missing from the same API response. This suggests a selective enumeration bug rather than a blanket exclusion — something about how Sentry's connector registration differs from Amplitude's causes it to be dropped from the routines connector list.
Impact: Cannot attach the Sentry MCP connector to a daily routine that reviews and auto-fixes Sentry issues — even though the tools work fine in interactive sessions.
Having the same issue with the Sentry MCP
I think this is the same issue that I'm seeing with the Slack bot that makes
@claudeavailable to call in Slack channels.Starting a claude code sesion through
claude.ai/codedirectly defaults all my enabled MCP connectors to enabled, as I'd expect. Starting a sesion throughHey @claude, do a thingshows all the connectors as disabled, as pictured below.Claude Code web session started via
@claudein Slack<img width="367" height="162" alt="Image" src="https://github.com/user-attachments/assets/a694bd2a-9de8-402f-b4f4-7b82e34b6708" />
Claude Code web session started directly through the web UI
(ignore the extra MCP, I added that in between screenshots to see if updating the list changed anything)
<img width="551" height="228" alt="Image" src="https://github.com/user-attachments/assets/00b91e4f-36b6-4f80-bc59-3f645003ccc9" />
Seeing this morning in Routines:
<img width="424" height="207" alt="Image" src="https://github.com/user-attachments/assets/8f51dcb0-3bbb-4b6c-9029-25712e528308" />
and meanwhile in Settings:
<img width="1312" height="482" alt="Image" src="https://github.com/user-attachments/assets/922816f0-78a6-472f-9767-35c8d81ffe16" />
I'm having the same issue on my personal Max plan, even though it worked fine on my Team plan.
I'm seeing it on my teams account.
I'm seeing this on a teams account. The MCP configured on
claude.aiis refusing to fire up, be connected in my routine even though it literally is. Pretty simple stuff, myclaudelocally can use the connector just fine, but Routines is basically just "ignoring" the connectors and acting like they are not there.This really disrupts the usage of routines and appears to be a regression.
Routine screenshot:
<img width="853" height="300" alt="Image" src="https://github.com/user-attachments/assets/e4533d9d-4c0c-4da5-a327-82013aefee17" />
Routine setup showing the configured connector:
<img width="632" height="209" alt="Image" src="https://github.com/user-attachments/assets/44f847bc-b0b7-462d-b197-191cf2db1e5b" />
Also seeing this on an Enterprise Team account. Recurring maintenance on a Github Repo + Jira status update. Both Atlassian and Github connectors will work on one run, then ask me to re-authenticate the next.... I've already authenticated, shouldn't the connector get a new token via the OAuth handshake with a refresh token?
Update: This started working for me a few days after my original comment.
I'm currently experiencing this issue.
Goal: I want a Claude routine to auto-update my GitHub profile README as repos change across multiple orgs.
Context: I created a throwaway test to confirm the cloud sandbox can enumerate repos across all my orgs before designing the real routine.
Routine:
<img width="613" height="141" alt="Image" src="https://github.com/user-attachments/assets/65a1e9ea-6008-4603-b864-5cc7a8164a41" />
Connectors:
<img width="759" height="371" alt="Image" src="https://github.com/user-attachments/assets/0ae03e35-bf3a-46be-b150-8089374c38d0" />
Additionally: I can connect repos to the routine but this won't account for new repos being created as well (without testing) I assume there will be a limit to how many repos I can attach.
<img width="619" height="67" alt="Image" src="https://github.com/user-attachments/assets/8c8ba255-37b5-4b7d-b215-3aa950ead4d8" />
The exact same thing is happening for us, sometimes Connectors show up, most of the time they don't.