Composio

Manage Composio tools, connected accounts, MCP servers, triggers, and webhooks.

От сообществаРаботаетНужен API-ключГлобальныйБесплатноТолько чтение

Что умеет

Auth.Session.Info.List: Retrieves detailed information about the current authenticated user session, including project details, organization membership, and API key information if applicable. This end
Auth Configs.List: Retrieves all auth configs for your project. Auth configs define how users authenticate with external services (OAuth, API keys, etc.). Use filters to find configs for specific tool
Auth Configs.Create: Creates a new auth config for a toolkit, allowing you to use your own OAuth credentials or API keys instead of Composio-managed authentication. This is required when you want to u

Какие данные видит

Нужен ли аккаунт

Нужен API-ключ из настроек сервиса

Manage Composio tools, connected accounts, MCP servers, triggers, and webhooks. Requires an API key from the Composio dashboard.

Список инструментов сервера (60)

Технические названия из tools/list. Нужны только разработчикам.

auth.session.info.list	Retrieves detailed information about the current authenticated user session, including project details, organization membership, and API key information if applicable. This endpoint is useful for verifying authentication status and retrieving contextual information about the authenticated user and their access privileges.
auth_configs.list	Retrieves all auth configs for your project. Auth configs define how users authenticate with external services (OAuth, API keys, etc.). Use filters to find configs for specific toolkits or to distinguish between Composio-managed and custom configurations.
auth_configs.create	Creates a new auth config for a toolkit, allowing you to use your own OAuth credentials or API keys instead of Composio-managed authentication. This is required when you want to use custom OAuth apps (bring your own client ID/secret) or configure specific authentication parameters for a toolkit.
auth_configs.get	Retrieves detailed information about a specific authentication configuration using its unique identifier.
auth_configs.by_nanoid.update	Modifies an existing authentication configuration with new credentials or other settings. Only specified fields will be updated.
auth_configs.delete	Soft-deletes an authentication configuration by marking it as deleted in the database. This operation cannot be undone.
auth_configs.update	Updates the status of an authentication configuration to either enabled or disabled. Disabled configurations cannot be used for new connections.
connected_accounts.list	Retrieves all connected accounts for your project. Connected accounts represent authenticated user connections to external services (e.g., a user's Gmail account, Slack workspace). Filter by toolkit, status, user ID, or auth config to find specific connections.
connected_accounts.create	Initiates a new connection to an external service for a user. For OAuth-based toolkits, this returns a redirect URL to complete authentication. For API key-based toolkits, provide the credentials directly in the request body. Use the `user_id` field to associate the connection with a specific user in your system. Deprecated for Composio-managed OAuth: For Composio-managed auth configs on OAuth1, OAuth2, or DCR_OAUTH schemes, this endpoint is being retired and will start returning `400 BadRequest` on 2026-05-08 for new organizations and 2026-07-03 for all remaining organizations. Migrate those calls to `POST /api/v3/connected_accounts/link`. Custom auth configs and non-OAuth schemes (API key, bearer, basic) continue to be supported here. Responses on the retiring path carry a `Deprecation` header (RFC 9745) and a `Sunset` header (RFC 8594) for client-side detection.
connected_accounts.get	Retrieves comprehensive details of a connected account, including authentication configuration, connection status, and all parameters needed for API requests.
connected_accounts.update	Update a connected account. Supports updating the alias and/or credentials. Only specified fields will be updated. Set a credential field to null to remove it. Alias must be unique within the same project, entity, and toolkit scope.
connected_accounts.delete	Soft-deletes a connected account by marking it as deleted in the database. This prevents the account from being used for API calls but preserves the record for audit purposes.
connected_accounts.status.update	Updates the status of a connected account to either enabled (active) or disabled (inactive). Disabled accounts cannot be used for API calls but remain in the database.
connected_accounts.refresh	Initiates a new authentication flow for a connected account when credentials have expired or become invalid. This may generate a new authentication URL for OAuth flows or refresh tokens for other auth schemes.
connected_accounts.link.create	Creates a new authentication link session that users can use to connect their accounts
org.project.config.list	Retrieves the current project configuration including 2FA settings.
org.project.config.update	Updates the project configuration settings.
org.owner.project.new.create	Creates a new project within the authenticated user's organization using the specified name. Projects are isolated environments within your organization, each with their own API keys, webhook configurations, and resources. Use this endpoint to create additional projects for different environments (e.g., development, staging, production) or for separate applications.
org.owner.project.list.list	Retrieves all projects belonging to the authenticated organization. Projects are returned in descending order of creation date (newest first). This endpoint is useful for displaying project selection in dashboards or for integrations that need to list all available projects.
org.owner.project.get	Retrieves detailed information about a specific project using its unique identifier. This endpoint provides complete project configuration including webhook URLs, creation and update timestamps, and webhook secrets. Use this endpoint to inspect project settings or verify project configuration.
org.owner.project.delete	Soft-deletes a project within the organization by its unique identifier. When a project is deleted, it is marked as deleted but not immediately removed from the database. This operation affects all resources associated with the project including API keys, webhook configurations, and connected services. This action cannot be undone through the API.
org.owner.project.regenerate_api_key.create	Generates a new API key for the specified project, invalidating any existing API keys for that project. This operation creates a fresh API key with a new random name and key value. All existing API keys for this project will be marked as deleted.
webhook_subscriptions.list	Lists all webhook subscriptions for the authenticated project with pagination. Currently limited to one subscription per project.
webhook_subscriptions.create	Creates a webhook subscription for the authenticated project. Only one subscription is allowed per project. The signing secret is returned in subscription responses.
webhook_subscriptions.get	Retrieves a webhook subscription by ID.
webhook_subscriptions.update	Updates a webhook subscription. At least one field must be provided.
webhook_subscriptions.delete	Permanently deletes a webhook subscription. This action cannot be undone.
webhook_subscriptions.rotate_secret.create	Generates a new signing secret for the webhook subscription.
webhook_subscriptions.event_types.list	Returns all event types that can be subscribed to, along with their supported webhook versions.
webhook_endpoints.list	Lists webhook endpoints for the authenticated project, optionally filtered by toolkit.
webhook_endpoints.self.create	Creates a shared webhook endpoint for a toolkit + OAuth app + project. Returns the webhook URL that the customer registers in their app dashboard. Idempotent — returns existing endpoint if one already exists for this toolkit + client_id + project.
webhook_endpoints.get	Retrieves a single webhook endpoint. Secret values are redacted. Use GET /webhook_endpoints/schema to discover field definitions.
webhook_endpoints.create	Full replacement of webhook endpoint configuration. All required setup fields must be provided. Use PATCH to update individual fields.
webhook_endpoints.update	Updates app-specific secrets and credentials. Uses merge semantics — only included fields are updated; omitted fields are preserved. Can be called on active endpoints (e.g., to rotate a signing secret).
toolkits.list	Retrieves a comprehensive list of toolkits of their latest versions that are available to the authenticated project. Toolkits represent integration points with external services and applications, each containing a collection of tools and triggers. This endpoint supports filtering by category and management type, as well as different sorting options.
toolkits.categories.list	Retrieves a comprehensive list of all available toolkit categories from their latest versions. These categories can be used to filter toolkits by type or purpose when using the toolkit listing endpoint. Categories help organize toolkits into logical groups based on their functionality or industry focus.
toolkits.get	Retrieves comprehensive information about a specific toolkit using its unique slug identifier. This endpoint provides detailed metadata, authentication configuration options, and feature counts for the requested toolkit.
tools.list	Retrieve a paginated list of available tools with comprehensive filtering, sorting and search capabilities. Use query parameters to narrow down results by toolkit, tags, or search terms.
tools.enum.list	Retrieve a list of all available tool enumeration values (tool slugs) from latest version of each toolkit. This endpoint returns a comma-separated string of tool slugs that can be used in other API calls.
tools.get	Retrieve detailed information about a specific tool using its slug identifier. This endpoint returns full metadata about a tool including input/output parameters, versions, and toolkit information.
toolkits.multi.create	Retrieves a comprehensive list of toolkits of their latest versions that are available to the authenticated project. Toolkits represent integration points with external services and applications, each containing a collection of tools and triggers. This endpoint supports filtering by category and management type, as well as different sorting options. You can optionally specify a list of toolkit slugs to fetch specific toolkits.
tools.execute.create	Execute a specific tool operation with provided arguments and authentication. This is the primary endpoint for integrating with third-party services and executing tools. You can provide structured arguments or use natural language processing by providing a text description of what you want to accomplish.
tools.execute.input.create	Uses AI to translate a natural language description into structured arguments for a specific tool. This endpoint is useful when you want to let users describe what they want to do in plain language instead of providing structured parameters.
tools.execute.proxy.create	Proxy an HTTP request to a third-party API using connected account credentials. This endpoint allows making authenticated API calls to external services while abstracting away authentication details.
trigger_instances.upsert.create	Creates a new trigger instance or updates an existing one with the same configuration. Triggers listen for events from external services (webhooks or polling) and can invoke your workflows. If a matching trigger already exists and is disabled, it will be re-enabled. Requires a connected account ID to associate the trigger with a specific user connection.
trigger_instances.active.list	Retrieves all active trigger instances for your project. Triggers listen for events from connected accounts (e.g., new emails, Slack messages, GitHub commits) and can invoke webhooks or workflows. Use filters to find triggers for specific users, connected accounts, or trigger types.
trigger_instances.manage.update	Updates the status of a trigger instance to enable or disable it. Disabling a trigger pauses event listening without deleting the trigger configuration. Re-enabling restores the trigger to its active state. Use this for temporary maintenance or to control trigger execution.
trigger_instances.manage.delete	Permanently deletes a trigger instance. This stops the trigger from listening for events and removes it from your project. Use the PATCH endpoint with status "disable" if you want to temporarily pause a trigger instead.
triggers_types.list.enum.list	Retrieves a list of all available trigger type enum values that can be used across the API from latest versions of the toolkit only
triggers_types.get	Retrieve detailed information about a specific trigger type using its slug identifier
triggers_types.list	Retrieve a list of available trigger types with optional filtering by toolkit. Results are paginated and can be filtered by toolkit.
mcp.servers.list	Retrieves a paginated list of MCP servers associated with the authenticated project. Results can be filtered by name, toolkit, or authentication configuration ID. MCP servers are used to provide Model Control Protocol integration points for connecting AI assistants to your applications and services.
mcp.servers.create	Creates a new Model Control Protocol (MCP) server instance for the authenticated project. An MCP server provides a connection point for AI assistants to access your applications and services. The server is configured with specific authentication and tool permissions that determine what actions the connected assistants can perform.
mcp.servers.custom.create	Creates a new Model Control Protocol (MCP) server instance that can integrate with multiple applications or toolkits simultaneously. This endpoint allows you to create a server that can access tools from different applications, making it suitable for complex workflows that span multiple services.
mcp.servers.generate.create	Generates a Model Control Protocol (MCP) URL for an existing server with custom query parameters. The URL includes user-specific parameters and configuration flags that control the behavior of the MCP connection.
mcp.get	Retrieves detailed configuration information for a specific Model Control Protocol (MCP) server. The returned data includes connection details, associated applications, enabled tools, and authentication configuration.
mcp.update	Updates the configuration of an existing Model Control Protocol (MCP) server. You can modify the server name, associated applications, and enabled tools. Only the fields included in the request will be updated.
mcp.delete	Performs a soft delete on a Model Control Protocol (MCP) server, making it unavailable for future use. This operation is reversible in the database but cannot be undone through the API. Any applications or services connected to this server will lose access after deletion.
mcp.app.get	Retrieves a paginated list of Model Control Protocol (MCP) servers that are configured for a specific application or toolkit. This endpoint allows you to find all MCP server instances that have access to a particular application, such as GitHub, Slack, or Jira.
mcp.servers.instances.list	Retrieves a paginated list of user instances (user IDs) associated with a specific Model Control Protocol (MCP) server. This endpoint supports pagination to handle servers with many instances.