io.github.ComposioHQ/composio

Connect AI agents to 1000+ apps with managed authentication and tool-calling.

GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport:

0 tools

Grade F

Edit this pageView history

AI / ML Security

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-composiohq-composio": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-composiohq-composio)](https://mcppedia.org/s/io-github-composiohq-composio)

Read me

What io.github.ComposioHQ/composio does

This repository publishes Composio's MCP server to the official MCP Registry, which syndicates to the GitHub MCP Registry. Once listed, any MCP-compatible client — Claude, GitHub Copilot, Cursor, and others — can discover and install Composio in a click.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

12/100across 5 weighted dimensions

How we score →

0255075100

−88

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.ComposioHQ/composio safe to use?: io.github.ComposioHQ/composio has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.ComposioHQ/composio?: io.github.ComposioHQ/composio can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.ComposioHQ/composio?: io.github.ComposioHQ/composio is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in ai-ml / security

View all →

Memory MCP Server98

Persistent memory using a knowledge graph

87.9k 5

Sequential Thinking MCP Server95

Dynamic problem-solving through sequential thought chains

87.9k 1

Gpt Researcher95

An autonomous agent that conducts deep research on any data using any LLM providers

28.0k 5

Context Mode95

Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.

18.4k 6

MCP Security Weekly

Get CVE alerts and security updates for io.github.ComposioHQ/composio and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Composio — MCP Server

This repository publishes Composio's MCP server to the official MCP Registry, which syndicates to the GitHub MCP Registry. Once listed, any MCP-compatible client — Claude, GitHub Copilot, Cursor, and others — can discover and install Composio in a click.

Composio connects AI agents to 1000+ apps (Gmail, Slack, GitHub, Linear, and more) with managed authentication and tool-calling.

How publishing works

Publishing is automated with GitHub Actions. Creating a release (a v* tag) triggers .github/workflows/publish-mcp.yml, which:

Installs the mcp-publisher CLI

Authenticates to the registry with GitHub OIDC — no tokens or secrets

Runs mcp-publisher publish

Because the repository lives under the ComposioHQ org, OIDC proves ownership of the io.github.ComposioHQ namespace automatically.

# publish a new version git tag v1.0.4 git push origin v1.0.4

Verify the result:

File

Purpose

server.json

The registry listing (name, title, remote OAuth endpoint).

.github/workflows/publish-mcp.yml

Auto-publishes to the MCP Registry on release. GitHub OIDC, no secrets.

Frequently Asked Questions

Is io.github.ComposioHQ/composio safe to use?

io.github.ComposioHQ/composio has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.ComposioHQ/composio?

io.github.ComposioHQ/composio can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.ComposioHQ/composio?

io.github.ComposioHQ/composio is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Composio — MCP Server

Composio connects AI agents to 1000+ apps (Gmail, Slack, GitHub, Linear, and more) with managed authentication and tool-calling.

Using the Composio MCP server

Add the remote server to any MCP-compatible client:

https://connect.composio.dev/mcp

Zero config. Connecting opens an OAuth login (login.composio.dev) — no API keys or IDs to paste.
Remote + streamable HTTP. Nothing to install or run locally.

What gets published

server.json defines the listing:

{
  "name": "io.github.ComposioHQ/composio",
  "title": "Composio",
  "remotes": [
    { "type": "streamable-http", "url": "https://connect.composio.dev/mcp" }
  ]
}

How publishing works

Publishing is automated with GitHub Actions. Creating a release (a v* tag) triggers .github/workflows/publish-mcp.yml, which:

Installs the mcp-publisher CLI
Authenticates to the registry with GitHub OIDC — no tokens or secrets
Runs mcp-publisher publish

Because the repository lives under the ComposioHQ org, OIDC proves ownership of the io.github.ComposioHQ namespace automatically.

# publish a new version
git tag v1.0.4
git push origin v1.0.4

Verify the result:

➡️ https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.ComposioHQ/composio

Prior art

This follows the same path other vendors use to self-publish their official servers. For example, MongoDB publishes io.github.mongodb-js/mongodb-mcp-server via GitHub OIDC under its own org — no partnership required.

Repository layout

File	Purpose
`server.json`	The registry listing (name, title, remote OAuth endpoint).
`.github/workflows/publish-mcp.yml`	Auto-publishes to the MCP Registry on release. GitHub OIDC, no secrets.