https://linen.dev logo
composio via mcp protocol doesnt need skill?
# 🖥│support-forum
w
Hi, I'm using Composio with multiple apps, including OpenClaw and OpenCode. The documentation states that installing Composio via the CLI automatically installs its skills. However, I set it up using the MCP method. Do I not need to install extra skills for Composio in this case? bc when I ask OpenCode to handle GitHub-related tasks, it sometimes forgot to use Composio to complete them.
b
Hi there, You've got it right. Over MCP you do not need to install any extra Composio skills for tool access. The MCP server exposes Composio's meta-tools (like
COMPOSIO_SEARCH_TOOLS
and
COMPOSIO_MULTI_EXECUTE_TOOL
), and the agent searches for and runs the right GitHub tool through those at runtime. The bundled skills ship specifically with the Claude Code plugin and are just guidance prompts, not a requirement for the tools to work. One of them,
prefer-composio
, is a routing prompt that nudges the agent to reach for Composio whenever you mention an external service. That is exactly your "OpenCode sometimes forgets" situation. Since OpenCode and OpenClaw don't get that plugin, the simplest fix is to add a short routing instruction yourself in the client's rules or system prompt (for example, OpenCode's
AGENTS.md
), telling the agent to use Composio for any external app task. Just reply here if anything's still off. 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.