Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Composio (BYOK) icon

Composio (BYOK)

Read the Composio toolkit and tool catalog and your own connected accounts, auth configs and triggers with your own project API key

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderComposiounofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which toolkits does Composio offer for project management?
Tools called
list_toolkits
Tell me about the Composio github toolkit
Tools called
get_toolkit
Which toolkit categories does Composio have?
Tools called
list_toolkit_categories
Which Composio tools exist for creating GitHub issues?
Tools called
list_tools
What inputs does the Composio tool GITHUB_CREATE_AN_ISSUE take?
Tools called
get_tool
Which Composio connected accounts are active?
Tools called
list_connected_accounts

About

Composio (BYOK) lets an AI assistant read your own Composio data through the Composio API with a key you supply (Composio project API key). Read-only: 9 tools (list_toolkits, get_toolkit, list_toolkit_categories, list_tools, get_tool, list_connected_accounts, list_auth_configs, list_trigger_types, list_active_triggers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to backend.composio.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Composio. Composio and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Composio API (backend.composio.dev) with a BYOK key; documentation: https://docs.composio.dev/reference. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List toolkitsList the toolkits (apps and services Composio integrates with) with name, description, auth methods and tool and trigger counts.
  • Get toolkitGet one toolkit: description, auth methods, categories, versions and counts of tools and triggers.
  • List toolkit categoriesList the toolkit categories with display name and id, which can be used to filter list_toolkits.
  • List toolsList tools (single actions of a toolkit) with name, description, toolkit, tags and whether authentication is needed.
  • Get toolGet one tool: description, input and output parameter schemas, required scopes, tags and available versions.
  • List connected accountsList the connected accounts (end-user links to apps) of the project with toolkit, status, alias and times.
  • List auth configsList the auth configs (how users sign in to each toolkit) with toolkit, scheme, status and number of connections.
  • List trigger typesList trigger types (events a connected app can send) with name, description, webhook or poll type and toolkit.
  • List active triggersList the trigger instances active in the project with trigger name, connected account, update time and disabled time.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-composio.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-composio.connectorbay.com/mcp
RESTPOST https://byok-composio.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-composio.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Composio project API key in the X-Upstream-Key header (get one at docs.composio.dev).
  • Ask a question; the agent picks the right tool and answers from the live data.

Composio connector: questions and answers

What is the Composio connector?

Composio (BYOK) lets an AI assistant read your own Composio data through the Composio API with a key you supply (Composio project API key). It is a hosted MCP server with 9 tools such as List toolkits, Get toolkit, List toolkit categories, List tools, Get tool, List connected accounts, published by Unify Dynamics LLC. It is independent and not affiliated with Composio.

How do I connect Composio to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-composio.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-composio.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-composio.json.

Do I need a Composio account or API key?

Yes: this is a bring-your-own-key connector. Create a Composio project API key at https://docs.composio.dev/reference/authenticating-to-composio and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Composio read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Composio connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Cloudflare Workers AI (BYOK)

Browse the Cloudflare Workers AI model catalog, tasks, authors, fine-tunes and model input schemas with your own Cloudflare API token

Live · MCP + REST7 tools

Cloudflare Workers Platform (BYOK)

Read your Cloudflare Workers platform resources: KV namespaces, D1 databases, Queues, Hyperdrive configs, Vectorize indexes, Workflows, custom domains and cron triggers with your own API token

Live · MCP + REST11 tools

Cloudflare Workers Storage (BYOK)

Read your Cloudflare Workers KV namespaces and keys and Durable Object namespaces (names and metadata, not stored values) with your own API token

Live · MCP + REST6 tools

Cloudflare Workflows (BYOK)

Read your Cloudflare Workflows, their instances, versions and concurrency settings with your own API token (instance step outputs and payloads are left out)

Live · MCP + REST9 tools

Cloudflare Zero Trust (BYOK)

Read your Cloudflare Zero Trust Access applications, policies, groups, identity providers, service tokens, Gateway rules and tunnels with your own API token

Live · MCP + REST9 tools

Cloudflare Zone Settings (BYOK)

Read a Cloudflare zone's settings such as SSL mode, minimum TLS, security level and caching options, plus tiered caching, Argo and cache reserve switches, with your own API token

Live · MCP + REST9 tools

Documentation

Back to top

Composio (BYOK) — connector documentation

  • MCP endpoint: https://byok-composio.connectorbay.com/mcp
  • REST API: POST https://byok-composio.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-composio.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Composio Composio project API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-composio.connectorbay.com/health · Tool schemas: https://byok-composio.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-composio · agent@connectorbay.com

What Composio (BYOK) is for

Composio (BYOK) lets an AI assistant read your own Composio data through the Composio API with a key you supply (Composio project API key). Read-only: 9 tools (list_toolkits, get_toolkit, list_toolkit_categories, list_tools, get_tool, list_connected_accounts, list_auth_configs, list_trigger_types, list_active_triggers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to backend.composio.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Composio. Composio and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which toolkits does Composio offer for project management?"
  • "Tell me about the Composio github toolkit"
  • "Which toolkit categories does Composio have?"
  • "Which Composio tools exist for creating GitHub issues?"
  • "What inputs does the Composio tool GITHUB_CREATE_AN_ISSUE take?"
  • "Which Composio connected accounts are active?"

What it does

  • list_toolkits: List the toolkits (apps and services Composio integrates with) with name, description, auth methods and tool and trigger counts.
  • get_toolkit: Get one toolkit: description, auth methods, categories, versions and counts of tools and triggers.
  • list_toolkit_categories: List the toolkit categories with display name and id, which can be used to filter list_toolkits.
  • list_tools: List tools (single actions of a toolkit) with name, description, toolkit, tags and whether authentication is needed. Schemas are not requested.
  • get_tool: Get one tool: description, input and output parameter schemas, required scopes, tags and available versions.
  • list_connected_accounts: List the connected accounts (end-user links to apps) of the project with toolkit, status, alias and times. Credentials are not requested.
  • list_auth_configs: List the auth configs (how users sign in to each toolkit) with toolkit, scheme, status and number of connections. Credentials are not requested.
  • list_trigger_types: List trigger types (events a connected app can send) with name, description, webhook or poll type and toolkit.
  • list_active_triggers: List the trigger instances active in the project with trigger name, connected account, update time and disabled time.

BYOK key

You bring your own Composio Composio project API key (https://docs.composio.dev/reference/authenticating-to-composio). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to backend.composio.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Composio API (backend.composio.dev) with a BYOK key; documentation: https://docs.composio.dev/reference. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Composio. Composio and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Composio account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Composio (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Composio (BYOK) is. Composio (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Composio data: Read the Composio toolkit and tool catalog and your own connected accounts, auth configs and triggers with your own project API key. You bring your own Composio Composio project API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Composio call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to backend.composio.dev, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Composio rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Composio receives. The request we make on your behalf, including the key and the arguments, under Composio's own terms and privacy policy. Composio acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Composio gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Composio data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Composio (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Composio at any time to end all access.

Children. Composio (BYOK) is a general-audience service operated by the adult using the assistant, under Composio's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Composio (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Composio (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Composio (BYOK) provides: Read the Composio toolkit and tool catalog and your own connected accounts, auth configs and triggers with your own project API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Composio credentials and only access data you are allowed to access. Composio's terms apply to your use of Composio; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Composio. Composio and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Composio returns, lightly trimmed; it may be incomplete, delayed or changed by Composio. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Composio account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Composio's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Composio may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Composio key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Composio takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-composio

Composio (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Composio (BYOK) never asks for them.

Get Composio (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Composio Composio project API key. Create one at https://docs.composio.dev/reference/authenticating-to-composio, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Composio. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Composio.