Compared with 0.24.0: `MCP`, `MCPAuthOptionsSchema`, `MCPToolkitConfigSchema`, `MCPToolkitConfigsArraySchema`, `ComposioProvider.wrapMcpServerResponse`, and 595 more.
@composio/core 0.24.0 → 0.27.0: deprecates 600 API(s): from its source to your code
MCP: MCP (Model Control Protocol) class Handles MCP server operations. When `config.experimental.mcp` is enabled, this class augments the features of `composio.mcp`. Use a session's MCP endpoint instead: `composio.create(userId, { mcp: true })` returns a session that exposes `session.mcp.url` / `session.mcp.headers`. MCP is now opt-in per session; the standalone `composio.mcp` server-management API is kept only for backwards compatibility. Prefer the session MCP endpoint; do not generate new code against `composio.mcp`. See https://docs.composio.dev/docs/sessions-via-mcp
ComposioProvider.wrapMcpServerResponse: : Will be removed in a future version, once the `experimental.mcp` flag is stabilized. Use `wrapMcpServers` instead. Optional method to transform MCP URL response into provider-specific format. Providers can override this method to define custom transformation logic for MCP server responses.
ToolRouterSession.workbench: Resolved sandbox config for the session. Use `session.sandbox` instead. `workbench` is a backwards-compatible alias and will be removed in a future release.
WebhookConnectedAccountAuthConfigSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
WebhookConnectedAccountAuthConfigSchema.augment: Use `.extend` instead
WebhookConnectedAccountAuthConfig.auth_scheme: - use state.authScheme instead
WebhookConnectionStateSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
WebhookConnectionStateSchema.augment: Use `.extend` instead
SingleConnectedAccountDetailedResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
SingleConnectedAccountDetailedResponseSchema.augment: Use `.extend` instead
SingleConnectedAccountDetailedResponse.params: - use state instead
SingleConnectedAccountDetailedResponse.user_id: - user ID of the connection owner
SingleConnectedAccountDetailedResponse.data: - use state instead
WebhookConnectionMetadataSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
WebhookConnectionMetadataSchema.augment: Use `.extend` instead
ConnectionExpiredEventSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ConnectionExpiredEventSchema.augment: Use `.extend` instead
ErrorHandleOptions.exitProcess: Use ComposioError.handleAndThrow() instead. This option will be removed in a future version.
ErrorHandleOptions.exitCode: This option is no longer used.
AuthConfigCreationToolAccessConfigSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthConfigCreationToolAccessConfigSchema.augment: Use `.extend` instead
AuthConfigListParamsSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthConfigListParamsSchema.augment: Use `.extend` instead
AuthConfigListResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthConfigListResponseSchema.augment: Use `.extend` instead
AuthConfigRetrieveResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthConfigRetrieveResponseSchema.augment: Use `.extend` instead
AuthConfigToolAccessConfigSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthConfigToolAccessConfigSchema.augment: Use `.extend` instead
AuthCustomConfigUpdateParamsSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthCustomConfigUpdateParamsSchema.augment: Use `.extend` instead
AuthDefaultConfigUpdateParamsSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
AuthDefaultConfigUpdateParamsSchema.augment: Use `.extend` instead
BaseAgenticProvider.wrapMcpServerResponse: : Will be removed in a future version, once the `experimental.mcp` flag is stabilized. Use `wrapMcpServers` instead. Optional method to transform MCP URL response into provider-specific format. Providers can override this method to define custom transformation logic for MCP server responses.
BaseNonAgenticProvider.wrapMcpServerResponse: : Will be removed in a future version, once the `experimental.mcp` flag is stabilized. Use `wrapMcpServers` instead. Optional method to transform MCP URL response into provider-specific format. Providers can override this method to define custom transformation logic for MCP server responses.
Composio.mcp: Model Context Protocol server management. Use a session's MCP endpoint instead: `composio.create(userId, { mcp: true })` returns a session that exposes `session.mcp.url` / `session.mcp.headers`. MCP is now opt-in per session; this standalone server-management API is kept only for backwards compatibility. Prefer the session MCP endpoint; do not generate new code against `composio.mcp`. See https://docs.composio.dev/docs/sessions-via-mcp
Composio.toolRouter: Legacy alias for `composio.sessions`. Use `composio.sessions` instead — `toolRouter` was renamed to `sessions` and is kept only for backwards compatibility. Prefer `composio.sessions`; do not generate new code against `composio.toolRouter`.
Composio.createSession: Creates a new instance of the Composio SDK with custom request options while preserving the existing configuration. This method is particularly useful when you need to: - Add custom headers for specific requests - Track request contexts with unique identifiers - Override default request behavior for a subset of operations The new instance inherits all configuration from the parent instance (apiKey, baseURL, provider, etc.) but allows you to specify custom request options that will be used for all API calls made through this session. Will be removed in a future version of the SDK. Instead, cons
ComposioCustomCreateResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ComposioCustomCreateResponseSchema.augment: Use `.extend` instead
ComposioGenerateURLParamsSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ComposioGenerateURLParamsSchema.augment: Use `.extend` instead
ComposioGenerateURLResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ComposioGenerateURLResponseSchema.augment: Use `.extend` instead
ComposioMcpDeleteResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ComposioMcpDeleteResponseSchema.augment: Use `.extend` instead
ComposioMcpListResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ComposioMcpListResponseSchema.augment: Use `.extend` instead
ComposioMcpRetrieveResponseSchema.nonstrict: In most cases, this is no longer needed - unknown properties are now silently stripped. If you want to pass through unknown properties, use `.passthrough()` instead.
ComposioMcpRetrieveResponseSchema.augment: Use `.extend` instead
registry.npmjs.orgquote checked
Nemotron fixes