claude-code - 💡(How to fix) Fix Routines in Claude Code can't use Claude.ai Connectors (e.g., Composio, Gmail, LinkedIn) [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52586Fetched 2026-04-24 06:03:11
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×2

Root Cause

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.

Fix Action

Fix / Workaround

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.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • 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

extent analysis

TL;DR

The Composio connector is not reachable within Claude Code's Routine runtime, preventing automation of workflows that depend on personal integrations.

Guidance

  • Verify that the Composio connector is properly configured in the Claude.ai account settings and that it works as expected in the claude.ai chat.
  • Check if there are any existing issues or feature requests related to MCP server integration in the Claude Code repository that may provide more insight or a potential workaround.
  • Consider reaching out to the Claude Code support team to inquire about potential plans to bridge Claude.ai Connectors into Claude Code's Routine runtime or add a per-connector toggle.
  • Explore alternative automation tools or services that can interact with Composio and LinkedIn APIs directly, potentially bypassing the need for integration within Claude Code.

Example

No code snippet is provided as the issue is related to configuration and integration rather than code.

Notes

The solution to this issue may require changes to the Claude Code platform or the Composio connector, which are outside the control of the user. The user may need to wait for an update or find alternative workarounds.

Recommendation

Apply workaround: While waiting for a potential update to Claude Code, explore alternative automation tools or services that can interact with Composio and LinkedIn APIs directly. This may provide a temporary solution to automate workflows that depend on personal integrations.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Routines in Claude Code can't use Claude.ai Connectors (e.g., Composio, Gmail, LinkedIn) [2 comments, 2 participants]