https://linen.dev logo
Windows Codex CLI - Unable to Use Composio with OA...
# 🖥│support-forum
w
On Windows, trying to use Codex CLI... I have a Composio MCP Server, but no tools are being exposed. What is going on?
Copy code
• Composio MCP is configured and appears authenticated:

  composio  https://connect.composio.dev/mcp  enabled  OAuth

  codex mcp get composio also shows:

  enabled: true
  transport: streamable_http
  url: https://connect.composio.dev/mcp

  I did not see Composio-specific tools exposed in this session’s current tool list via tool_search; only other MCP/app
  tools surfaced. So: server/auth look good, but Composio tool exposure is not currently visible from the tools
  available to me in this chat.
b
Hi there, Good news, this is actually expected rather than a fault. The
https://connect.composio.dev/mcp
server is Composio's Tool Router, and it doesn't list each app's tools (like
GMAIL_SEND_EMAIL
) directly in the tool list. Instead it exposes a small set of meta-tools prefixed
COMPOSIO_
, such as: •
COMPOSIO_SEARCH_TOOLS
(find the right tool for a task) •
COMPOSIO_EXECUTE_TOOL
/
COMPOSIO_MULTI_EXECUTE_TOOL
(run it) •
COMPOSIO_MANAGE_CONNECTIONS
(connect/check accounts) The agent calls those to discover and run the actual app tool on demand, so you won't see individual app tools sitting in the list. Two things to check: • Look for the
COMPOSIO_
prefixed tools in your current tool list. If they're there, you're set, just prompt for a task (e.g. "send an email via Gmail") and the agent will search and execute. • If you don't see even the
COMPOSIO_
tools, that's a different issue, so reply here with your full tool-list output and we'll dig in. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.