535
],
536
"toolCount": 893,
537
"triggerCount": 20,
538
- "version": "20260721_00",
538
+ "version": "20260728_00",
539
"tools": [
540
{
541
"slug": "GITHUB_ABORT_REPOSITORY_MIGRATION",
5519
"composioManagedAuthSchemes": [
5520
"OAUTH2"
5521
],
5522
- "toolCount": 48,
5522
+ "toolCount": 56,
5523
"triggerCount": 8,
5524
- "version": "20260721_00",
5524
+ "version": "20260730_00",
5525
"tools": [
5526
{
5527
"slug": "NOTION_ADD_MULTIPLE_PAGE_CONTENT",
5593
"name": "Create Notion page",
5594
"description": "Creates a new page in a Notion workspace under a specified parent page or database. Supports creating pages with markdown content using the native markdown parameter, or as an empty page that can be populated later. PREREQUISITES: - Parent page/database must exist and be accessible in your Notion workspace - Use search_pages or list_databases first to obtain valid parent IDs LIMITATIONS: - Cannot create root-level pages (must have a parent) - May encounter conflicts if creating pages too quickly - Title-based parent search is less reliable than using UUIDs - The markdown parameter is mutually exclusive with children/content parameters"
5595
},
5596
+ {
5597
+ "slug": "NOTION_CREATE_VIEW",
5598
+ "name": "Create Notion view",
5599
+ "description": "Create a Notion view."
5600
+ },
5601
+ {
5602
+ "slug": "NOTION_CREATE_VIEW_QUERY",
5603
+ "name": "Create Notion view query",
5604
+ "description": "Create a Notion view query and return the first page of page references."
5605
+ },
5606
{
5607
"slug": "NOTION_DELETE_BLOCK",
5608
"name": "Delete a block",
5609
"description": "Archives a Notion block, page, or database using its ID, which sets its 'archived' property to true (like moving to \"Trash\" in the UI) and allows it to be restored later. Note: This operation will fail if the block has an archived parent or ancestor in the hierarchy. You must unarchive the ancestor before archiving/deleting its descendants. IMPORTANT LIMITATION: Workspace-level pages (top-level pages that are direct children of the workspace, not contained within other pages or databases) cannot be archived via the Notion API. This is a documented Notion API restriction. Only pages that are children of other pages or databases can be deleted through this action."
5610
},
5611
+ {
5612
+ "slug": "NOTION_DELETE_VIEW",
5613
+ "name": "Delete Notion view",
5614
+ "description": "Delete a Notion view."
5615
+ },
5616
+ {
5617
+ "slug": "NOTION_DELETE_VIEW_QUERY",
5618
+ "name": "Delete Notion view query",
5619
+ "description": "Delete a cached Notion view query."
5620
+ },
5621
{
5622
"slug": "NOTION_DUPLICATE_PAGE",
5623
"name": "Duplicate page",
5678
"name": "Get page property",
5679
"description": "Call this to get a specific property from a Notion page when you have a valid `page_id` and `property_id`; handles pagination for properties returning multiple items."
5680
},
5681
+ {
5682
+ "slug": "NOTION_GET_VIEW_QUERY_RESULTS",
5683
+ "name": "Get Notion view query results",
5684
+ "description": "Get a page of results from a cached Notion view query."
5685
+ },
5686
{
5687
"slug": "NOTION_INSERT_ROW_DATABASE",
5688
"name": "Insert row database",
5708
"name": "List users",
5709
"description": "Retrieves a paginated list of users (excluding guests) from the Notion workspace; the number of users returned per page may be less than the requested `page_size`."
5710
},
5711
+ {
5712
+ "slug": "NOTION_LIST_VIEWS",
5713
+ "name": "List Notion views",
5714
+ "description": "List Notion views for a database or data source."
5715
+ },
5716
{
5717
"slug": "NOTION_MOVE_PAGE",
5718
"name": "Move Page",
5721
{
5722
"slug": "NOTION_QUERY_DATABASE",
5723
"name": "Query database",
5694
- "description": "Queries a Notion database to retrieve pages (rows). In Notion, databases are collections where each row is a page and columns are properties. Returns paginated results with metadata. Important requirements: - The database must be shared with your integration - Property names in sorts must match existing database properties exactly (case-sensitive) - For timestamp sorting, use 'created_time' or 'last_edited_time' (case-insensitive) - The start_cursor must be a valid UUID from a previous response's next_cursor field - Database IDs must be valid 32-character UUIDs (with or without hyphens) Use this action to: - Retrieve all or filtered database entries - Sort results by database properties or page timestamps - Paginate through large result sets - Get database content for processing or display"
5724
+ "description": "Queries a Notion database to retrieve pages (rows). In Notion, databases are collections where each row is a page and columns are properties. Returns paginated results with metadata. Important requirements: - The database must be shared with your integration - Property names in sorts must match existing database properties exactly (case-sensitive) - For timestamp sorting, use 'created_time' or 'last_edited_time' (case-insensitive) - The start_cursor must be the opaque value from a previous response's next_cursor field - Database IDs must be valid 32-character UUIDs (with or without hyphens) Use this action to: - Retrieve all or filtered database entries - Sort results by database properties or page timestamps - Paginate through large result sets - Get database content for processing or display"
5725
},
5726
{
5727
"slug": "NOTION_QUERY_DATABASE_WITH_FILTER",
5758
"name": "Retrieve page",
5759
"description": "Retrieve a Notion page's properties/metadata (not block content) by page_id. Use when you have a page URL/ID and need to access its properties; for page content use block-children tools."
5760
},
5761
+ {
5762
+ "slug": "NOTION_RETRIEVE_VIEW",
5763
+ "name": "Retrieve Notion view",
5764
+ "description": "Retrieve a Notion view and its configuration."
5765
+ },
5766
{
5767
"slug": "NOTION_SEARCH_NOTION_PAGE",
5768
"name": "Search Notion pages and databases",
5793
"name": "Update database schema",
5794
"description": "Updates an existing Notion database's schema including title, description, and/or properties (columns). IMPORTANT NOTES: - At least one update (title, description, or properties) must be provided - The database must be shared with your integration - Property names are case-sensitive and must match exactly - When changing a property to 'relation' type, you MUST provide the database_id of the target database - Removing properties will permanently delete that column and its data - Use NOTION_FETCH_DATA first to get the exact property names and database structure Common errors: - 'database_id' missing: Ensure you're passing the database_id parameter (not page_id) - 'data_source_id' undefined: When changing to relation type, database_id is required in PropertySchemaUpdate - Property name mismatch: Names must match exactly including case and special characters"
5795
},
5796
+ {
5797
+ "slug": "NOTION_UPDATE_VIEW",
5798
+ "name": "Update Notion view",
5799
+ "description": "Update a Notion view."
5800
+ },
5801
{
5802
"slug": "NOTION_UPSERT_ROW_DATABASE",
5803
"name": "Upsert database rows",
15415
],
15416
"toolCount": 574,
15417
"triggerCount": 6,
15378
- "version": "20260721_00",
15418
+ "version": "20260729_00",
15419
"tools": [
15420
{
15421
"slug": "CANVAS_ABORT_QUIZ_REPORT_GENERATION",
26235
"OAUTH2",
26236
"S2S_OAUTH2"
26237
],
26238
+ "composioManagedAuthSchemes": [
26239
+ "OAUTH2"
26240
+ ],
26241
"toolCount": 407,
26242
"triggerCount": 0,
26243
"version": "20260721_00",
28812
],
28813
"toolCount": 83,
28814
"triggerCount": 9,
28772
- "version": "20260724_00",
28815
+ "version": "20260728_00",
28816
"tools": [
28817
{
28818
"slug": "ONE_DRIVE_ADD_WORKBOOK_WORKSHEET",
29041
},
29042
{
29043
"slug": "ONE_DRIVE_LIST_ALL_DRIVE_ITEMS",
29001
- "name": "List All Drive Items Recursively",
29002
- "description": "Recursively lists all files and folders in a OneDrive drive by traversing the entire folder hierarchy. Starts at the drive root and explores every subfolder to return a complete flattened list of all items. Use this action when you need a comprehensive inventory of all drive contents, want to search across all folders, or need to analyze the complete drive structure. For large drives with thousands of items, this operation may take significant time as it must traverse every folder."
29044
+ "name": "List All Drive Items",
29045
+ "description": "Lists a complete OneDrive or SharePoint drive safely, one Microsoft Graph delta page per invocation. Start without `page_token`, then pass each `next_page_token` back until `sync_complete` is true. The terminal `delta_token` can be saved and passed back later to fetch changes since the completed snapshot. Delta enumeration is stable under concurrent writes and avoids the request burst caused by recursively fetching every folder in one execution."
29046
},
29047
{
29048
"slug": "ONE_DRIVE_LIST_BUNDLES",
32056
],
32057
"toolCount": 223,
32058
"triggerCount": 7,
32016
- "version": "20260721_00",
32059
+ "version": "20260728_00",
32060
"tools": [
32061
{
32062
"slug": "SALESFORCE_ACCOUNT_CREATION_WITH_CONTENT_TYPE_OPTION",
60353
],
60354
"toolCount": 452,
60355
"triggerCount": 2,
60313
- "version": "20260721_00",
60356
+ "version": "20260728_00",
60357
"tools": [
60358
{
60359
"slug": "ZENDESK_APPLY_ZENDESK_MACRO",
62918
"OAUTH2",
62919
"API_KEY"
62920
],
62878
- "toolCount": 52,
62921
+ "toolCount": 53,
62922
"triggerCount": 0,
62880
- "version": "20260721_00",
62923
+ "version": "20260731_00",
62924
"tools": [
62925
{
62926
"slug": "METAADS_CREATE_AD",
63027
"name": "List Business Ad Accounts",
63028
"description": "Tool to retrieve all ad accounts owned by a specific Business Manager. Use when you need to get ad account information for a business including account IDs, names, and status."
63029
},
63030
+ {
63031
+ "slug": "METAADS_LIST_BUSINESSES",
63032
+ "name": "List Businesses",
63033
+ "description": "Tool to discover every Business Manager the authenticated Meta principal can access, via `GET /me/businesses`. Use this first when you do not know a `business_id`: it works for both user and system-user tokens and returns the businesses you have a role in, so you can then reach Business-Manager-owned ad accounts (which do NOT appear in `/me/adaccounts`) through the owned/client ad-account tools. Requires the `business_management` permission on the connected token."
63034
+ },
63035
{
63036
"slug": "METAADS_LIST_BUSINESS_INVOICES",
63037
"name": "List Business Invoices",
63228
"type": "string",
63229
"description": "Scopes to request from the user, comma separated",
63230
"required": false,
63183
- "default": "ads_read,ads_management"
63231
+ "default": "ads_read,ads_management,business_management"
63232
}
63233
]
63234
},
68093
],
68094
"toolCount": 171,
68095
"triggerCount": 0,
68048
- "version": "20260721_00",
68096
+ "version": "20260730_00",
68097
"tools": [
68098
{
68099
"slug": "SERVICENOW_ATTACH_FILE_TO_RECORD",
69302
],
69303
"toolCount": 368,
69304
"triggerCount": 0,
69257
- "version": "20260721_00",
69305
+ "version": "20260730_00",
69306
"tools": [
69307
{
69308
"slug": "PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGER",
69357
{
69358
"slug": "PAGERDUTY_CREATE_AND_MANAGE_CUSTOM_INCIDENT_FIELDS",
69359
"name": "Create and manage custom incident fields",
69312
- "description": "Creates a new custom field for incidents in PagerDuty. This endpoint allows you to define additional data points to be associated with incidents, enhancing incident management and reporting capabilities. Custom fields can be used to store various types of information such as environment, severity, or any other relevant metadata. The field can be configured with different data types and value constraints, allowing for flexible and structured data capture. Use this endpoint when you need to extend the incident data model with organization-specific information. Note that once created, certain properties of a custom field cannot be changed, so careful planning of field structure is important."
69360
+ "description": "Creates a new custom field for incidents in PagerDuty. This endpoint allows you to define additional data points to be associated with incidents, enhancing incident management and reporting capabilities. Custom fields can be used to store various types of information such as environment, severity, or any other relevant metadata. The field can be configured with different data types and value constraints, allowing for flexible and structured data capture. Use this endpoint when you need to extend the incident data model with organization-specific information. Note that once created, certain properties of a custom field cannot be changed, so careful planning of field structure is important. DEPRECATED: PagerDuty has deprecated this Base Incident Type endpoint. Use `create_a_custom_field_for_an_incident_type` for new integrations."
69361
},
69362
{
69363
"slug": "PAGERDUTY_CREATE_AN_INCIDENT_TYPE",
69367
{
69368
"slug": "PAGERDUTY_CREATE_A_RULESET",
69369
"name": "Create a ruleset",
69322
- "description": "Creates a new Ruleset in PagerDuty for managing incident routing and notification rules. This endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. It's particularly useful when setting up or modifying your incident management workflow. The created Ruleset can be global, affecting all incoming incidents, or assigned to a specific team for more targeted incident routing. Note that while you can create the Ruleset structure with this call, the actual rules within the Ruleset must be added separately using other API endpoints."
69370
+ "description": "Creates a new Ruleset in PagerDuty for managing incident routing and notification rules. This endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. It's particularly useful when setting up or modifying your incident management workflow. The created Ruleset can be global, affecting all incoming incidents, or assigned to a specific team for more targeted incident routing. Note that while you can create the Ruleset structure with this call, the actual rules within the Ruleset must be added separately using other API endpoints. DEPRECATED: Rulesets/Event Rules are EOL; creates are rejected. Use Event Orchestrations."
69371
},
69372
{
69373
"slug": "PAGERDUTY_CREATE_A_TRIGGER",
69397
{
69398
"slug": "PAGERDUTY_CREATE_EVENT_RULE_IN_RULESET",
69399
"name": "Create event rule in ruleset",
69352
- "description": "Creates a new Event Rule within a specified Ruleset in PagerDuty's incident management system. This endpoint allows you to define complex conditions for event matching and specify actions to be taken when an event meets those conditions. Use this to automate incident response, customize alert routing, and fine-tune event processing based on specific criteria. The created rule becomes part of the Ruleset's evaluation sequence, affecting how incoming events are processed and managed. **DEPRECATION WARNING**: Rulesets and Event Rules reached end-of-life on January 31, 2025. While the API still supports accessing and modifying existing rulesets/rules, creating new rulesets is disabled. PagerDuty strongly recommends migrating to Event Orchestration for improved UI, advanced conditions, rule nesting, and better API/Terraform support. This action only works with pre-existing rulesets created before the EOL date."
69400
+ "description": "Creates a new Event Rule within a specified Ruleset in PagerDuty's incident management system. This endpoint allows you to define complex conditions for event matching and specify actions to be taken when an event meets those conditions. Use this to automate incident response, customize alert routing, and fine-tune event processing based on specific criteria. The created rule becomes part of the Ruleset's evaluation sequence, affecting how incoming events are processed and managed. **DEPRECATION WARNING**: Rulesets and Event Rules reached end-of-life on January 31, 2025. While the API still supports accessing and modifying existing rulesets/rules, creating new rulesets is disabled. PagerDuty strongly recommends migrating to Event Orchestration for improved UI, advanced conditions, rule nesting, and better API/Terraform support. This action only works with pre-existing rulesets created before the EOL date. DEPRECATED: Rulesets/Event Rules are EOL; creates are rejected. Use Event Orchestrations."
69401
},
69402
{
69403
"slug": "PAGERDUTY_CREATE_EXTENSION_OBJECT",
69482
{
69483
"slug": "PAGERDUTY_CREATE_RESPONSE_PLAY_FOR_INCIDENTS",
69484
"name": "Create response play for incidents",
69437
- "description": "Creates a new Response Play in PagerDuty, which is a predefined set of actions to be executed in response to an incident. This endpoint allows you to configure automated responses, including adding subscribers, assigning responders, setting up conference details, and defining how the Response Play can be triggered. Use this when you want to standardize and automate your incident management process, ensuring consistent and efficient responses to different types of incidents. The Response Play can be set to run automatically for specific services or be manually triggered by team members or responders, depending on the configuration. This tool is particularly useful for creating templated responses for common incident types or for implementing best practices across your organization's incident management workflow."
69485
+ "description": "Creates a new Response Play in PagerDuty, which is a predefined set of actions to be executed in response to an incident. This endpoint allows you to configure automated responses, including adding subscribers, assigning responders, setting up conference details, and defining how the Response Play can be triggered. Use this when you want to standardize and automate your incident management process, ensuring consistent and efficient responses to different types of incidents. The Response Play can be set to run automatically for specific services or be manually triggered by team members or responders, depending on the configuration. This tool is particularly useful for creating templated responses for common incident types or for implementing best practices across your organization's incident management workflow. DEPRECATED: Response Plays are EOL. On accounts with Incident Workflows enabled this always fails; use the Incident Workflows actions instead."
69486
},
69487
{
69488
"slug": "PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION",
69492
{
69493
"slug": "PAGERDUTY_CREATE_SERVICE_EVENT_RULE",
69494
"name": "Create service event rule",
69447
- "description": "Creates a new event rule for a specific service in PagerDuty. This endpoint allows you to define complex conditions and actions for handling incoming events, enabling automated incident management and alert routing. Use this when you need to set up custom logic for processing events, such as setting priorities, annotating incidents, or suppressing alerts based on specific criteria. The rule's position in the evaluation order can be specified, and various time-based conditions can be applied to control when the rule is active. This endpoint is crucial for fine-tuning your incident response workflow and reducing alert noise."
69495
+ "description": "Creates a new event rule for a specific service in PagerDuty. This endpoint allows you to define complex conditions and actions for handling incoming events, enabling automated incident management and alert routing. Use this when you need to set up custom logic for processing events, such as setting priorities, annotating incidents, or suppressing alerts based on specific criteria. The rule's position in the evaluation order can be specified, and various time-based conditions can be applied to control when the rule is active. This endpoint is crucial for fine-tuning your incident response workflow and reducing alert noise. DEPRECATED: Rulesets/Event Rules are EOL; creates are rejected. Use Event Orchestrations."
69496
},
69497
{
69498
"slug": "PAGERDUTY_CREATE_STATUS_PAGE_SUBSCRIPTION",
69657
{
69658
"slug": "PAGERDUTY_DELETE_RESPONSE_PLAY",
69659
"name": "Delete response play",
69612
- "description": "Deletes a specific Response Play from the PagerDuty system. This endpoint should be used when you need to remove an outdated or unnecessary Response Play from your incident management workflow. It permanently eliminates the predefined sequence of actions associated with the specified Response Play ID. Use this endpoint with caution, as the deletion is irreversible and may impact automated incident response processes. This operation is particularly useful for maintaining an up-to-date and efficient set of response strategies in your PagerDuty account. **IMPORTANT**: Response Plays are deprecated in favor of Incident Workflows. If your PagerDuty account has Incident Workflows enabled, this endpoint will return a 301 status code with the message \"Incident Workflows are enabled on this account.\" In such cases, you should use the Incident Workflows API instead."
69660
+ "description": "Deletes a specific Response Play from the PagerDuty system. This endpoint should be used when you need to remove an outdated or unnecessary Response Play from your incident management workflow. It permanently eliminates the predefined sequence of actions associated with the specified Response Play ID. Use this endpoint with caution, as the deletion is irreversible and may impact automated incident response processes. This operation is particularly useful for maintaining an up-to-date and efficient set of response strategies in your PagerDuty account. **IMPORTANT**: Response Plays are deprecated in favor of Incident Workflows. If your PagerDuty account has Incident Workflows enabled, this endpoint will return a 301 status code with the message \"Incident Workflows are enabled on this account.\" In such cases, you should use the Incident Workflows API instead. DEPRECATED: Response Plays are EOL. On accounts with Incident Workflows enabled this always fails; use the Incident Workflows actions instead."
69661
},
69662
{
69663
"slug": "PAGERDUTY_DELETE_RULE_FROM_RULESET_BY_ID",
69667
{
69668
"slug": "PAGERDUTY_DELETE_RULESET_BY_ID",
69669
"name": "Delete ruleset by id",
69622
- "description": "Deletes a specific ruleset from the PagerDuty system based on the provided ID. This endpoint should be used when you need to remove an existing ruleset, which may be necessary during incident management reconfiguration or when cleaning up obsolete rulesets. The deletion is permanent and cannot be undone, so use this endpoint with caution. It's important to note that deleting a ruleset will affect the incident routing and escalation policies associated with it, potentially impacting your organization's incident response workflow."
69670
+ "description": "Deletes a specific ruleset from the PagerDuty system based on the provided ID. This endpoint should be used when you need to remove an existing ruleset, which may be necessary during incident management reconfiguration or when cleaning up obsolete rulesets. The deletion is permanent and cannot be undone, so use this endpoint with caution. It's important to note that deleting a ruleset will affect the incident routing and escalation policies associated with it, potentially impacting your organization's incident response workflow. PagerDuty no longer permits creating Rulesets/Event Rules, but this endpoint remains available for deleting an existing Ruleset. PagerDuty recommends migrating existing Rulesets to Event Orchestration."
69671
},
69672
{
69673
"slug": "PAGERDUTY_DELETE_RUNNER_TEAM_ASSOCIATION",
69692
{
69693
"slug": "PAGERDUTY_DELETE_SERVICE_RULE_BY_ID",
69694
"name": "Delete service rule by id",
69647
- "description": "Deletes a specific rule from a PagerDuty service. This endpoint is used to permanently remove a rule that defines conditions for incident creation or automation within a particular service. It should be used when you need to eliminate an outdated, incorrect, or no longer needed rule from your service configuration. The operation cannot be undone, so use it with caution. This endpoint does not return the deleted rule's details; it only confirms the successful deletion."
69695
+ "description": "Deletes a specific rule from a PagerDuty service. This endpoint is used to permanently remove a rule that defines conditions for incident creation or automation within a particular service. It should be used when you need to eliminate an outdated, incorrect, or no longer needed rule from your service configuration. The operation cannot be undone, so use it with caution. This endpoint does not return the deleted rule's details; it only confirms the successful deletion. PagerDuty no longer permits creating Rulesets/Event Rules, but this endpoint remains available for deleting an existing Service Event Rule. PagerDuty recommends migrating existing Event Rules to Event Orchestration."
69696
},
69697
{
69698
"slug": "PAGERDUTY_DELETE_STATUS_PAGE_POSTMORTEM",
69797
{
69798
"slug": "PAGERDUTY_EXECUTE_RESPONSE_PLAY_BY_ID",
69799
"name": "Execute response play by id",
69752
- "description": "Executes a predefined Response Play for a specific incident in PagerDuty. This endpoint allows you to trigger a sequence of automated actions designed to manage and respond to the given incident. It's useful for standardizing and streamlining your incident response process, ensuring consistent handling of similar incidents. The endpoint requires you to specify the incident for which the Response Play should be run, using the incident's unique identifier. Note that the Response Play itself is identified by the ID in the URL path, not in the request body."
69800
+ "description": "Executes a predefined Response Play for a specific incident in PagerDuty. This endpoint allows you to trigger a sequence of automated actions designed to manage and respond to the given incident. It's useful for standardizing and streamlining your incident response process, ensuring consistent handling of similar incidents. The endpoint requires you to specify the incident for which the Response Play should be run, using the incident's unique identifier. Note that the Response Play itself is identified by the ID in the URL path, not in the request body. DEPRECATED: Response Plays are EOL. On accounts with Incident Workflows enabled this always fails; use the Incident Workflows actions instead."
69801
},
69802
{
69803
"slug": "PAGERDUTY_FETCH_CACHE_VARIABLE_FOR_EVENT_ORCHESTRATION",
69892
{
69893
"slug": "PAGERDUTY_GET_AGGREGATED_PD_ADVANCE_USAGE_DATA",
69894
"name": "Get aggregated pd advance usage data",
69847
- "description": "Provides aggregated metrics for the usage of PD Advance. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.read`"
69895
+ "description": "Provides aggregated metrics for the usage of PD Advance. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`"
69896
},
69897
{
69898
"slug": "PAGERDUTY_GET_ALERT_GROUPING_SETTINGS",
70072
{
70073
"slug": "PAGERDUTY_GET_OAUTH_DELEGATIONS_REVOCATION_REQUESTS_STATUS",
70074
"name": "Get oauth delegations revocation requests status",
70027
- "description": "**DEPRECATED**: This endpoint is deprecated. The DELETE /oauth_delegations endpoint is now synchronous and completes immediately, eliminating the need to check revocation request status separately. Get the status of all OAuth delegations revocation requests for this account, specifically how many requests are still pending processing. OAuth delegations represent instances of app authorization (e.g., mobile app, Slack, Microsoft Teams) to access a PagerDuty account. This endpoint was previously used when deletion was asynchronous. **Access Requirements:** - Limited to account owners and admins only - Scoped OAuth requires: `oauth_delegations.read` **Note**: Since the DELETE operation is now synchronous, you should use the PAGERDUTY_DELETE_ALL_OAUTH_DELEGATIONS action directly, which returns the result immediately without needing to poll for status."
70075
+ "description": "**DEPRECATED**: This endpoint is deprecated. The DELETE /oauth_delegations endpoint is now synchronous and completes immediately, eliminating the need to check revocation request status separately. Get the status of all OAuth delegations revocation requests for this account, specifically how many requests are still pending processing. OAuth delegations represent instances of app authorization (e.g., mobile app, Slack, Microsoft Teams) to access a PagerDuty account. This endpoint was previously used when deletion was asynchronous. **Access Requirements:** - Limited to account owners and admins only - Scoped OAuth requires: `oauth_delegations.read` **Note**: Since the DELETE operation is now synchronous, you should use the PAGERDUTY_DELETE_ALL_OAUTH_DELEGATIONS action directly, which returns the result immediately without needing to poll for status. DEPRECATED: returns 404. Use PAGERDUTY_DELETE_ALL_OAUTH_DELEGATIONS, which returns the result directly."
70076
},
70077
{
70078
"slug": "PAGERDUTY_GET_PAUSED_INCIDENT_ALERTS",
70087
{
70088
"slug": "PAGERDUTY_GET_RESPONSE_PLAYS",
70089
"name": "Get response plays",
70042
- "description": "**DEPRECATED**: This endpoint was deprecated and removed in June 2024. Response Plays have been replaced by Incident Workflows, which provide more robust and powerful automation capabilities. Accounts have been migrated to use Incident Workflows instead. If you need similar functionality, please use the Incident Workflows API endpoints: - List Incident Workflows: GET /incident_workflows - Get Incident Workflow: GET /incident_workflows/{id} Original functionality: This endpoint retrieved a list of response plays configured in the PagerDuty account. Response plays were predefined sets of actions that could be automatically executed when an incident occurred, helping to streamline and standardize incident response processes."
70090
+ "description": "**DEPRECATED**: This endpoint was deprecated and removed in June 2024. Response Plays have been replaced by Incident Workflows, which provide more robust and powerful automation capabilities. Accounts have been migrated to use Incident Workflows instead. If you need similar functionality, please use the Incident Workflows API endpoints: - List Incident Workflows: GET /incident_workflows - Get Incident Workflow: GET /incident_workflows/{id} Original functionality: This endpoint retrieved a list of response plays configured in the PagerDuty account. Response plays were predefined sets of actions that could be automatically executed when an incident occurred, helping to streamline and standardize incident response processes. DEPRECATED: Response Plays are EOL. On accounts with Incident Workflows enabled this always fails; use the Incident Workflows actions instead."
70091
},
70092
{
70093
"slug": "PAGERDUTY_GET_RULE_FROM_RULESET_BY_ID",
70632
{
70633
"slug": "PAGERDUTY_RETRIEVE_RESPONSE_PLAY_BY_ID",
70634
"name": "Retrieve response play by id",
70587
- "description": "**DEPRECATED**: This endpoint has been deprecated and removed. Response Plays have been replaced by Incident Workflows. When calling this endpoint, the API returns HTTP 301 (Moved Permanently) with the error message: \"Incident Workflows are enabled on this account.\" **Migration Path**: Use Incident Workflows API instead: - List Incident Workflows: GET /incident_workflows - Get Incident Workflow: GET /incident_workflows/{id} **Original Functionality**: This endpoint previously retrieved detailed information about a specific response play in the PagerDuty incident management system, including configuration and actions for automating incident response processes."
70635
+ "description": "**DEPRECATED**: This endpoint has been deprecated and removed. Response Plays have been replaced by Incident Workflows. When calling this endpoint, the API returns HTTP 301 (Moved Permanently) with the error message: \"Incident Workflows are enabled on this account.\" **Migration Path**: Use Incident Workflows API instead: - List Incident Workflows: GET /incident_workflows - Get Incident Workflow: GET /incident_workflows/{id} **Original Functionality**: This endpoint previously retrieved detailed information about a specific response play in the PagerDuty incident management system, including configuration and actions for automating incident response processes. DEPRECATED: Response Plays are EOL. On accounts with Incident Workflows enabled this always fails; use the Incident Workflows actions instead."
70636
},
70637
{
70638
"slug": "PAGERDUTY_RETRIEVE_RULE_BY_SERVICE_ID",
70982
{
70983
"slug": "PAGERDUTY_UPDATE_EVENT_RULE_BY_ID",
70984
"name": "Update event rule by id",
70937
- "description": "This endpoint allows you to update an existing Event Rule within a specified Ruleset in PagerDuty. Event Rules define conditions for matching events and actions to take when those conditions are met. You can modify various aspects of the rule, including its active status, matching conditions, time frames, variables, position in the ruleset, and associated actions. This endpoint is particularly useful for fine-tuning your incident management workflow, adjusting how events are processed, and controlling alert behavior. It's important to note that changes made through this endpoint will immediately affect how incoming events are handled, so careful consideration should be given to the potential impact on your alerting system."
70985
+ "description": "This endpoint allows you to update an existing Event Rule within a specified Ruleset in PagerDuty. Event Rules define conditions for matching events and actions to take when those conditions are met. You can modify various aspects of the rule, including its active status, matching conditions, time frames, variables, position in the ruleset, and associated actions. This endpoint is particularly useful for fine-tuning your incident management workflow, adjusting how events are processed, and controlling alert behavior. It's important to note that changes made through this endpoint will immediately affect how incoming events are handled, so careful consideration should be given to the potential impact on your alerting system. PagerDuty no longer permits creating Rulesets/Event Rules, but this endpoint remains available for modifying an existing Ruleset Event Rule. PagerDuty recommends migrating existing Event Rules to Event Orchestration."
70986
},
70987
{
70988
"slug": "PAGERDUTY_UPDATE_EVENT_RULE_FOR_SERVICE",
70989
"name": "Update event rule for service",
70942
- "description": "This endpoint allows you to update an existing Event Rule for a specific service in PagerDuty. Event Rules are used to define how incoming events should be processed, including conditions for matching events and actions to take when a match occurs. You can modify various aspects of the rule, such as its conditions, time-based restrictions, variables for extraction, and actions to perform on matching events. This endpoint is particularly useful for fine-tuning event management processes, adjusting rule priorities, or temporarily disabling rules without removing them entirely. It provides granular control over event handling, allowing for sophisticated automation and incident management workflows."
70990
+ "description": "This endpoint allows you to update an existing Event Rule for a specific service in PagerDuty. Event Rules are used to define how incoming events should be processed, including conditions for matching events and actions to take when a match occurs. You can modify various aspects of the rule, such as its conditions, time-based restrictions, variables for extraction, and actions to perform on matching events. This endpoint is particularly useful for fine-tuning event management processes, adjusting rule priorities, or temporarily disabling rules without removing them entirely. It provides granular control over event handling, allowing for sophisticated automation and incident management workflows. PagerDuty no longer permits creating Rulesets/Event Rules, but this endpoint remains available for modifying an existing Service Event Rule. PagerDuty recommends migrating existing Event Rules to Event Orchestration."
70991
},
70992
{
70993
"slug": "PAGERDUTY_UPDATE_EXTENSION_BY_ID",
71057
{
71058
"slug": "PAGERDUTY_UPDATE_RESPONSE_PLAY_BY_ID",
71059
"name": "Update response play by id",
71012
- "description": "Updates an existing Response Play in PagerDuty's incident management system. This endpoint allows you to modify various aspects of a Response Play, including its name, description, associated team, subscribers, responders, runnability, and conference details. Use this when you need to alter the behavior or configuration of an existing Response Play to better suit your incident response processes. The update is performed by specifying the Response Play's unique identifier and providing the updated information in the request body. This endpoint is particularly useful for refining your incident management automation based on evolving team structures, communication preferences, or response strategies."
71060
+ "description": "Updates an existing Response Play in PagerDuty's incident management system. This endpoint allows you to modify various aspects of a Response Play, including its name, description, associated team, subscribers, responders, runnability, and conference details. Use this when you need to alter the behavior or configuration of an existing Response Play to better suit your incident response processes. The update is performed by specifying the Response Play's unique identifier and providing the updated information in the request body. This endpoint is particularly useful for refining your incident management automation based on evolving team structures, communication preferences, or response strategies. DEPRECATED: Response Plays are EOL. On accounts with Incident Workflows enabled this always fails; use the Incident Workflows actions instead."
71061
},
71062
{
71063
"slug": "PAGERDUTY_UPDATE_RULESET_BY_ID",
71064
"name": "Update ruleset by id",
71017
- "description": "Updates an existing ruleset in the PagerDuty incident management system. This endpoint allows you to modify the name of a ruleset or change its team association. It's used when you need to adjust the configuration of a specific ruleset, such as renaming it for better clarity or reassigning it to a different team. The endpoint requires the ruleset's unique ID and accepts updates to the name and team fields. It's important to note that other fields like routing keys, creation details, and update history are read-only and cannot be modified through this call. This endpoint is particularly useful for maintaining and organizing rulesets as your incident management needs evolve."
71065
+ "description": "Updates an existing ruleset in the PagerDuty incident management system. This endpoint allows you to modify the name of a ruleset or change its team association. It's used when you need to adjust the configuration of a specific ruleset, such as renaming it for better clarity or reassigning it to a different team. The endpoint requires the ruleset's unique ID and accepts updates to the name and team fields. It's important to note that other fields like routing keys, creation details, and update history are read-only and cannot be modified through this call. This endpoint is particularly useful for maintaining and organizing rulesets as your incident management needs evolve. PagerDuty no longer permits creating Rulesets/Event Rules, but this endpoint remains available for modifying an existing Ruleset. PagerDuty recommends migrating existing Rulesets to Event Orchestration."
71066
},
71067
{
71068
"slug": "PAGERDUTY_UPDATE_SCHEDULE_BY_ID",
71069
"name": "Update schedule by id",
71022
- "description": "The UpdateSchedule endpoint modifies an existing on-call schedule in PagerDuty. It updates the schedule's name, time zone, description, and layers. Each layer defines a rotation pattern for on-call duties. Use this to adjust rotations, add/remove users, change time zones, or modify restrictions. Note: This replaces the entire schedule configuration, so include all desired layers and settings, even if only changing part of the schedule."
71070
+ "description": "The UpdateSchedule endpoint modifies an existing on-call schedule in PagerDuty. It updates the schedule's name, time zone, description, and layers. Each layer defines a rotation pattern for on-call duties. Use this to adjust rotations, add/remove users, change time zones, or modify restrictions. The API requires `type` and `time_zone` in the schedule object. Schedule layers are optional. When supplied, each layer must include its start, users, virtual rotation start, and rotation turn length."
71071
},
71072
{
71073
"slug": "PAGERDUTY_UPDATE_SERVICE_BY_ID",
71097
{
71098
"slug": "PAGERDUTY_UPDATE_STATUS_PAGE_POST_POSTMORTEM",
71099
"name": "Update status page post postmortem",
71052
- "description": "Updates an existing postmortem for a specific status page post in PagerDuty. This endpoint allows you to modify the postmortem message and notification settings for an incident's detailed analysis. The postmortem provides insights about the incident's root causes, impact, and lessons learned. Use this when you need to revise or enhance an existing postmortem after it has been created. The postmortem message supports Rich-Text formatting (max 10,000 characters) and you can control whether subscribers receive notifications about the update. Note: This endpoint updates an existing postmortem - use POST to create a new one."
71100
+ "description": "Legacy duplicate of `create_or_update_status_page_postmortem`. Both actions use the same PUT endpoint, which creates or replaces a postmortem for a Status Page Post. Use `create_or_update_status_page_postmortem` instead."
71101
},
71102
{
71103
"slug": "PAGERDUTY_UPDATE_STATUS_PAGE_POST_RESOURCE",
73739
"description": "A feature management platform that helps teams build better software faster using feature flags.",
73740
"category": "developer tools",
73741
"authSchemes": [
73694
- "API_KEY"
73742
+ "API_KEY",
73743
+ "OAUTH2"
73744
],
73745
"toolCount": 248,
73746
"triggerCount": 0,
73698
- "version": "20260615_00",
73747
+ "version": "20260729_00",
73748
"tools": [
73749
{
73750
"slug": "LAUNCH_DARKLY_ADD_MEMBER_TO_TEAMS",
74989
],
74990
"triggers": [],
74991
"authConfigDetails": [
74992
+ {
74993
+ "mode": "OAUTH2",
74994
+ "name": "launchdarkly_oauth",
74995
+ "fields": {
74996
+ "auth_config_creation": {
74997
+ "required": [
74998
+ {
74999
+ "name": "client_id",
75000
+ "displayName": "Client id",
75001
+ "type": "string",
75002
+ "description": "Client id of the app",
75003
+ "required": true,
75004
+ "default": null
75005
+ },
75006
+ {
75007
+ "name": "client_secret",
75008
+ "displayName": "Client secret",
75009
+ "type": "string",
75010
+ "description": "Client secret of the app",
75011
+ "required": true,
75012
+ "default": null
75013
+ }
75014
+ ],
75015
+ "optional": [
75016
+ {
75017
+ "name": "oauth_redirect_uri",
75018
+ "displayName": "Redirect URI",
75019
+ "type": "string",
75020
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
75021
+ "required": false,
75022
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
75023
+ },
75024
+ {
75025
+ "name": "scopes",
75026
+ "displayName": "Scopes",
75027
+ "type": "string",
75028
+ "description": "Scopes to request from the user, comma separated",
75029
+ "required": false,
75030
+ "default": "reader,writer,observability,offline_access"
75031
+ }
75032
+ ]
75033
+ },
75034
+ "connected_account_initiation": {
75035
+ "required": [],
75036
+ "optional": []
75037
+ }
75038
+ }
75039
+ },
75040
{
75041
"mode": "API_KEY",
75042
"name": "launchdarkly_api_key",
75548
],
75549
"toolCount": 124,
75550
"triggerCount": 0,
75454
- "version": "20260721_00",
75551
+ "version": "20260731_00",
75552
"tools": [
75553
{
75554
"slug": "CONTENTFUL_ACTIVATE_CONTENT_TYPE",
77898
],
77899
"toolCount": 22,
77900
"triggerCount": 0,
77804
- "version": "20260721_00",
77901
+ "version": "20260729_00",
77902
"tools": [
77903
{
77904
"slug": "SURVEY_MONKEY_CREATE_BULK_CONTACTS",
90860
],
90861
"toolCount": 84,
90862
"triggerCount": 1,
90766
- "version": "20260721_00",
90863
+ "version": "20260731_00",
90864
"tools": [
90865
{
90866
"slug": "TODOIST_ADD_WORKSPACE",
100178
],
100179
"toolCount": 9,
100180
"triggerCount": 0,
100084
- "version": "20260721_00",
100181
+ "version": "20260731_00",
100182
"tools": [
100183
{
100184
"slug": "BITWARDEN_DELETE_GROUP",
105560
],
105561
"toolCount": 84,
105562
"triggerCount": 0,
105466
- "version": "20260721_00",
105563
+ "version": "20260729_00",
105564
"tools": [
105565
{
105566
"slug": "BREX_ADD_WEBHOOK_GROUP_MEMBERS",
110867
"category": "server monitoring",
110868
"authSchemes": [
110869
"OAUTH2",
110773
- "API_KEY"
110870
+ "API_KEY",
110871
+ "BEARER_TOKEN"
110872
],
110873
"toolCount": 65,
110874
"triggerCount": 0,
110777
- "version": "20260721_00",
110875
+ "version": "20260731_00",
110876
"tools": [
110877
{
110878
"slug": "DATADOG_AGGREGATE_LOGS",
111259
}
111260
}
111261
},
111262
+ {
111263
+ "mode": "BEARER_TOKEN",
111264
+ "name": "datadog_pat",
111265
+ "fields": {
111266
+ "auth_config_creation": {
111267
+ "required": [],
111268
+ "optional": []
111269
+ },
111270
+ "connected_account_initiation": {
111271
+ "required": [
111272
+ {
111273
+ "name": "token",
111274
+ "displayName": "Bearer Token",
111275
+ "type": "string",
111276
+ "description": "Token for bearer authentication",
111277
+ "required": true,
111278
+ "default": null
111279
+ },
111280
+ {
111281
+ "name": "region",
111282
+ "displayName": "Datadog Site",
111283
+ "type": "string",
111284
+ "description": "Your Datadog site, shown in your browser address bar: app.datadoghq.com → us1, us5.datadoghq.com → us5, app.datadoghq.eu → eu. Most accounts can keep the default us1.",
111285
+ "required": true,
111286
+ "default": "us1"
111287
+ },
111288
+ {
111289
+ "name": "bearer_token",
111290
+ "displayName": "Personal Access Token",
111291
+ "type": "string",
111292
+ "description": "Your Datadog Personal Access Token. PATs authenticate API calls with a single short-lived, scoped credential and do not require a Datadog API key.",
111293
+ "required": true,
111294
+ "default": null
111295
+ }
111296
+ ],
111297
+ "optional": []
111298
+ }
111299
+ }
111300
+ },
111301
{
111302
"mode": "API_KEY",
111303
"name": "datadog_api_key",
114977
}
114978
]
114979
},
114980
+ {
114981
+ "slug": "aiwyn_tax_mcp",
114982
+ "name": "Aiwyn Tax MCP",
114983
+ "logo": "https://logos.composio.dev/api/aiwyn_tax_mcp",
114984
+ "description": "Aiwyn Tax (formerly Column Tax) estimates federal and state taxes with Aiwyn's tax engine.",
114985
+ "category": "taxes",
114986
+ "authSchemes": [
114987
+ "NO_AUTH"
114988
+ ],
114989
+ "toolCount": 10,
114990
+ "triggerCount": 0,
114991
+ "version": "20260730_01",
114992
+ "tools": [
114993
+ {
114994
+ "slug": "AIWYN_TAX_MCP_CALCULATE_TAX",
114995
+ "name": "Calculate tax",
114996
+ "description": "Calculate a tax return for a given jurisdiction. The 'input' argument must conform to the JSON schema returned by the tax_namespace_schema tool. Returns computed tax return document on success, or validation errors if the input is invalid. If some inputs trigger a PARTIAL DISQUALIFICATION, the document is still returned for the supported fields; review the disqualification details and estimate the impact of the unsupported fields on the taxpayer's tax owed or refund due. Use the check_tax tool first to validate the input before calculating the tax return with this tool.IMPORTANT RULES: (1) All field values must be wrapped as {\"value\": <val>} — never pass bare values. (2) Currency amounts are whole-dollar integers (e.g. $19,312.42 = 19312). (3) Every item in an array namespace (NamespaceList) must have a \"uuid\" field with a valid UUIDv4 string. UUIDv4 format: xxxxxxxx-xxxx-4xxx-[89ab]xxx-xxxxxxxxxxxx — the 3rd group MUST start with '4' (version) and the 4th group MUST start with '8', '9', 'a', or 'b' (variant). NEVER construct UUIDs manually (e.g. 'B1111111-1111-1111-1111-111111111111' is invalid). Use a UUID generator; example valid value: 'a3b4c5d6-e7f8-4a9b-8c0d-1e2f3a4b5c6d'. (4) Nested arrays (e.g. w2_state_local_tax_grp inside a w2) also require a UUIDv4 on each item. (5) Use \"who_applies_to\" to cross-reference entries: {\"value\": \"taxpayer\"} for singletons, {\"value\": \"<namespace>#<uuid>\"} for array items (e.g. \"dependent_detail#<uuid>\"). Other named reference fields (e.g. \"person\" in qualifying_person_grp, \"student\" in student_educational_instn_grp) use the same \"<namespace>#<uuid>\" format. (6) For state returns with Extended Links (state namespace extending a federal NamespaceList), each extended link item must use a UUIDv5 generated from the source item's UUID (as the namespace) and the extended namespace name (as the name). Matching is UUID-based, not positional. The number of expected instances depends on the source formula — it is NOT always a 1:1 match with the federal list (e.g. CA Form 3853 ca_household_grp expects taxpayer + spouse + all dependents). Incorrect or random UUIDs cause SILENT DATA LOSS — the server drops unrecognized UUIDs and replaces them with empty instances. Use the generate_uuid_v5 tool with the source item's UUID as the source_uuid and the extended namespace name (e.g. \"ca_provider\", \"ca_irsw2_g\") as the namespace input.Example: generate_uuid_v5(source_uuid: w2_uuid, namespace: \"ca_irsw2_g\") for a CA W-2 extension.(7) return_header is top-level, NOT nested inside return_data. Use tax_simple_return first to see the full input structure and examples. When returning the tax calculation inform the user that I'm just a tax estimator, you should consult with a tax professional."
114997
+ },
114998
+ {
114999
+ "slug": "AIWYN_TAX_MCP_CHECK_TAX",
115000
+ "name": "Check tax",
115001
+ "description": "Check inputs to calculate a tax return for a given jurisdiction. The 'input' argument must conform to the JSON schema returned by the tax_namespace_schema tool. Returns 'Success' on success, or validation errors if the input is invalid. If some inputs trigger a PARTIAL DISQUALIFICATION, the check still succeeds but includes disqualification details — proceed to calculate_tax to get the document and estimate the impact. Use this tool to validate inputs before calculating the tax return."
115002
+ },
115003
+ {
115004
+ "slug": "AIWYN_TAX_MCP_GENERATE_TAX_PDF_TOOL",
115005
+ "name": "Generate tax pdf tool",
115006
+ "description": "Start async PDF generation for a tax return. The 'input' argument must conform to the JSON schema returned by the tax_namespace_schema tool. Returns a job ID to poll with get_tax_pdf.Use the check_tax tool first to validate the input before generating the tax PDF with this tool.The input follows the same rules as calculate_tax: all values wrapped as {\"value\": <val>}, array items require UUIDv4 fields (extended link items use UUIDv5), references use who_applies_to, and return_header is top-level (not inside return_data). Use tax_simple_return to see the full input structure."
115007
+ },
115008
+ {
115009
+ "slug": "AIWYN_TAX_MCP_GENERATE_UUID_V5",
115010
+ "name": "Generate uuid v5",
115011
+ "description": "Generate a UUID v5 based on a source uuid and namespace."
115012
+ },
115013
+ {
115014
+ "slug": "AIWYN_TAX_MCP_GET_TAX_PDF_TOOL",
115015
+ "name": "Get tax pdf tool",
115016
+ "description": "Check status of a PDF generation job. Returns the status and a download URL when completed, only use this tool after generating the tax PDF with the generate_tax_pdf tool and it successfully returns a job ID. When returning the url of the PDF inform the user that I'm just a tax estimator, you should consult with a tax professional."
115017
+ },
115018
+ {
115019
+ "slug": "AIWYN_TAX_MCP_TAX_JURISDICTIONS",
115020
+ "name": "Tax jurisdictions",
115021
+ "description": "List all supported tax jurisdictions for a given tax year."
115022
+ },
115023
+ {
115024
+ "slug": "AIWYN_TAX_MCP_TAX_NAMESPACES",
115025
+ "name": "Tax namespaces",
115026
+ "description": "List all available input namespaces for a given jurisdiction. Use the returned names with the tax_namespace_schema tool to get the schema for a specific namespace. Requires a jurisdiction (e.g. \"us\" for federal, \"ca\" for California). Use the tax_jurisdictions tool first to discover available jurisdictions. NAMESPACE NAMING CONVENTIONS: Federal namespaces: irs1040, irs1040_schedule1, irs8962, w2, dependent_detail, etc. State namespaces: always prefixed with the state abbreviation (ca_form540, ny_it201, az_form140). NAMESPACE TYPES: Some namespaces are singletons (object), others are NamespaceLists (array) that can hold multiple items — e.g. w2 (multiple W-2s), dependent_detail (multiple dependents), irs1040_schedulec (multiple businesses). NamespaceList items require UUIDv4 fields. State NamespaceLists may act as Extended Links that extend a federal NamespaceList (e.g. ca_provider extends care_provider_grp). Extended link items must use UUIDv5 (deterministic, derived from source item UUID as namespace + extended namespace name as name). Matching is UUID-based, not positional. Wrong UUIDs cause silent data loss.Use the generate_uuid_v5 tool with the source item's UUID as the source_uuid and the extended namespace name (e.g. \"ca_provider\", \"ca_irsw2_g\") as the namespace input.Example: generate_uuid_v5(source_uuid: w2_uuid, namespace: \"ca_irsw2_g\") for a CA W-2 extension."
115027
+ },
115028
+ {
115029
+ "slug": "AIWYN_TAX_MCP_TAX_NAMESPACE_SCHEMA",
115030
+ "name": "Tax namespace schema",
115031
+ "description": "Get the TCB input schema for a single namespace (e.g. \"irs1040\", \"irs1040_schedulec\", \"ca_form540\"). Returns the properties and types for that namespace. HOW TO READ THE SCHEMA: (1) Each field references a type like tcb_string_null, tcb_integer_null, or tcb_boolean_null. All values must be wrapped as {\"value\": <val>}. (2) If the namespace title ends in '_list' (e.g. 'w2_list', 'dependent_detail_list'), it is a NamespaceList — an array of objects. Each array item MUST include a \"uuid\" field (non-null UUIDv4 string). (3) Reference fields link entries to other namespaces e.g. \"person\" in qualifying_person_grp, \"student\" in student_educational_instn_grp. All use the same format: {\"value\": \"<namespace>#<uuid>\"} (e.g. \"dependent_detail#<uuid>\"). (4) Nested arrays within a namespace (e.g. w2_state_local_tax_grp inside w2) also require uuid on each nested item. (5) Pattern-validated strings (e.g. SSNs, ZIPs, dates) have regex constraints in the schema $defs. SSNs/EINs: 9-digit string (no dashes). ZIPs: 5 or 9 digits. Dates: YYYY-MM-DD."
115032
+ },
115033
+ {
115034
+ "slug": "AIWYN_TAX_MCP_TAX_SIMPLE_RETURN",
115035
+ "name": "Tax simple return",
115036
+ "description": "Call this FIRST when beginning any tax return. Returns the curated namespace list, top-level structure guide, example input, and step-by-step filing workflow. By default returns a simple scenario (single or MFJ filer, W-2 income only, standard deduction, no dependents). Pass scenario=\"with_dependents\" for returns that include dependents, child care (Form 2441), and education credits (Form 8863). Optionally pass a state jurisdiction (e.g. \"ca\") to also include state-level namespaces — if you don't know which state applies, ask the user before calling."
115037
+ },
115038
+ {
115039
+ "slug": "AIWYN_TAX_MCP_TAX_YEARS",
115040
+ "name": "Tax years",
115041
+ "description": "List all supported tax years."
115042
+ }
115043
+ ],
115044
+ "triggers": [],
115045
+ "authConfigDetails": [
115046
+ {
115047
+ "mode": "NO_AUTH",
115048
+ "name": "AIWYN_TAX_MCP_NO_AUTH",
115049
+ "fields": {
115050
+ "auth_config_creation": {
115051
+ "required": [],
115052
+ "optional": []
115053
+ },
115054
+ "connected_account_initiation": {
115055
+ "required": [],
115056
+ "optional": []
115057
+ }
115058
+ }
115059
+ }
115060
+ ]
115061
+ },
115062
{
115063
"slug": "algodocs",
115064
"name": "Algodocs",
115906
}
115907
]
115908
},
115909
+ {
115910
+ "slug": "alltrails_mcp",
115911
+ "name": "AllTrails MCP",
115912
+ "logo": "https://logos.composio.dev/api/alltrails_mcp",
115913
+ "description": "Find hiking, biking, and running trails with reviews, photos, and route details from AllTrails.",
115914
+ "category": "fitness",
115915
+ "authSchemes": [
115916
+ "NO_AUTH"
115917
+ ],
115918
+ "toolCount": 5,
115919
+ "triggerCount": 0,
115920
+ "version": "20260730_01",
115921
+ "tools": [
115922
+ {
115923
+ "slug": "ALLTRAILS_MCP_FIND_TRAILS_NEAR_LOCATION",
115924
+ "name": "Find trails near location",
115925
+ "description": "Find hiking, running, biking, backpacking or other trails for outdoor activities near a set of coordinates within an optional specified maximum radius (meters).\n\nUse this tool when the user:\n* Requests trails near a specific point of interest or landmark.\n* Requests trails near a named location within a specified radius or accessible within a specified time constraint.\n* Provides specific latitude and longitude coordinates.\n\nFor most named places, use the \"search within bounding box\" tool if possible. Use this tool as a fallback when the bounding box of the named place is unknown.\n\nUsers can specify filters related to appropriate activities, attractions, suitability, and more. Numeric range filters related to distance, elevation, and length are also available. These filter values MUST be specified in meters.\n\nIn the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.\n"
115926
+ },
115927
+ {
115928
+ "slug": "ALLTRAILS_MCP_FIND_TRAILS_WITHIN_BOUNDS",
115929
+ "name": "Find trails within bounds",
115930
+ "description": "Find hiking, running, biking, backpacking or other trails for outdoor activities within a specified bounding box defined by southwest and northeast coordinates.\n\nUse this tool when the user:\n* Requests trails within specific geographic boundaries or coordinates.\n* Requests trails near a named geographic or political place, such as a continent, country, state, province, region, city, town, or neighborhood and you know the bounding box for that place.\n* Requests trails within a national, state or local park or other protected area and you know the bounding box for that park.\n\nIf the bounding box for the named place is not known, use the \"find trails near a location\" tool instead to find trails around a center point.\n\nUsers can specify filters related to appropriate activities, attractions, suitability, and more. Numeric range filters related to distance, elevation, and length are also available. These filter values MUST be specified in meters.\n\nIn the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.\n"
115931
+ },
115932
+ {
115933
+ "slug": "ALLTRAILS_MCP_GET_TRAIL_DETAILS",
115934
+ "name": "Get trail details",
115935
+ "description": "Find detailed information about a trail from AllTrails.\n\nGet descriptive overviews and specific accessibility information. Includes structured data about suitable activities, and feature highlights along the trail.\n\nGet stats about the trail geography and length, and stats about associated user-generated content.\n\nIn the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.\n\nRecent reviews are summarized in the `review_summary` field. If the user wants information that might be found in specific reviews, direct the user to the AllTrails web URL for the trail.\n"
115936
+ },
115937
+ {
115938
+ "slug": "ALLTRAILS_MCP_GET_TRAIL_WEATHER_OVERVIEW",
115939
+ "name": "Get trail weather overview",
115940
+ "description": "Get 7-day forecast for a trail at its trailhead, including high/low temperatures.\n\nFor more detailed weather information, including current conditions, sunrise/sunset times, and weather alerts, direct the user to the AllTrails web URL for the trail (available in the `get_trail_details` tool response).\n"
115941
+ },
115942
+ {
115943
+ "slug": "ALLTRAILS_MCP_SEARCH_TRAILS_BY_NAME",
115944
+ "name": "Search trails by name",
115945
+ "description": "Search for hiking, running, biking, backpacking or other trails by full or partial name match.\n\nUse this tool when the user:\n* Requests a specific trail by name (e.g., \"Avalanche Lake Trail\", \"Half Dome\")\n* Searches for trails with specific keywords in the name\n\nThe search can biased towards results near the provided coordinates if they are provided explicitly or available from the request metadata.\n\nIf there is a clear match to the user's query, the model should automatically make a subsequent call to the `get_trail_details` tool to present the user with complete details for the matching trail.\n\nIn the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.\n"
115946
+ }
115947
+ ],
115948
+ "triggers": [],
115949
+ "authConfigDetails": [
115950
+ {
115951
+ "mode": "NO_AUTH",
115952
+ "name": "ALLTRAILS_MCP_NO_AUTH",
115953
+ "fields": {
115954
+ "auth_config_creation": {
115955
+ "required": [],
115956
+ "optional": []
115957
+ },
115958
+ "connected_account_initiation": {
115959
+ "required": [],
115960
+ "optional": []
115961
+ }
115962
+ }
115963
+ }
115964
+ ]
115965
+ },
115966
{
115967
"slug": "alpaca",
115968
"name": "Alpaca",
121275
}
121276
]
121277
},
121278
+ {
121279
+ "slug": "aws_marketplace_mcp",
121280
+ "name": "AWS Marketplace MCP",
121281
+ "logo": "https://logos.composio.dev/api/aws_marketplace_mcp",
121282
+ "description": "Discover, evaluate, and procure cloud solutions across AWS Marketplace's 30K+ software, data, and service listings.",
121283
+ "category": "commerce",
121284
+ "authSchemes": [
121285
+ "NO_AUTH"
121286
+ ],
121287
+ "toolCount": 6,
121288
+ "triggerCount": 0,
121289
+ "version": "20260730_01",
121290
+ "tools": [
121291
+ {
121292
+ "slug": "AWS_MARKETPLACE_MCP_GET_AWS_MARKETPLACE_RELATED_SOLUTIONS",
121293
+ "name": "Get aws marketplace related solutions",
121294
+ "description": "Direct AWS Marketplace Catalog API call. Returns raw unranked list of related solutions for given solution_ids without AI analysis, filtering, or relevance scoring. Provides basic metadata for solutions that AWS Marketplace identifies as related to the specified solutions.\n\n**Input Parameters:**\n\n- **solution_ids** (required): Array of solution IDs (max 10) to find related solutions for. IDs start with `prodview-`, not `prod-`\n\n**Returns:** `{ results: [...] }` - Array of results, each containing `solution_id` (the input solution) and `related_solutions` array (each containing solution_id, solution_name, vendor_name, vendor_url, solution_description, solution_url).\n\n**Example:**\n```json\n{\n \"solution_ids\": [\"prodview-abc123\", \"prodview-xyz789\"]\n}\n```\n\n**Use this tool ONLY when:**\n\n- You have solution_ids and need raw related solutions list\n- Building programmatic integrations requiring unprocessed related solutions data\n- User explicitly requests raw related solutions API response\n- Need direct access to AWS Marketplace's related solutions without AI filtering\n\n**DO NOT use this tool for:**\n\n- Finding alternative solutions → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n- User asking \"what are alternatives to [solution]?\" → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n- Recommendations or comparisons → Use `get_aws_marketplace_report_guidelines` to get workflow instructions first\n- Requirements-based alternative discovery → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n\n**Note:** This is a stateless tool that does not require a conversation or request_id. Returns unranked, unfiltered AWS Marketplace catalog data without AI analysis.\n\n**⚠️ CRITICAL:** For any recommendation, comparison, or evaluation, first call `get_aws_marketplace_report_guidelines` to get the step-by-step guide and output format.\n\n**CRITICAL: When displaying URLs from this response (solution_url, vendor_url), always render the COMPLETE URL including ALL query parameters such as `ref_`. Do not truncate or simplify these URLs. These parameters are required for attribution tracking.**"
121295
+ },
121296
+ {
121297
+ "slug": "AWS_MARKETPLACE_MCP_GET_AWS_MARKETPLACE_REPORT_GUIDELINES",
121298
+ "name": "Get aws marketplace report guidelines",
121299
+ "description": "**⚠️ CALL THIS TOOL FIRST for any recommendation, comparison, or evaluation workflow.** Returns combined workflow instructions and output format template.\n\n**Input Parameters:**\n\n- **workflow_type** (required): The type of report to create. One of:\n - `\"recommendations\"` - Discover and rank AWS Marketplace solutions based on user requirements. Returns ranked product recommendations with relevance scores.\n - `\"comparison\"` - Create side-by-side comparisons of multiple AWS Marketplace solutions. Returns structured comparison tables with consistent dimensions.\n - `\"evaluation\"` - Generate a comprehensive evaluation report for a single AWS Marketplace solution. Returns professional-grade evaluation documents.\n\n**Returns:** Response object with:\n- `workflow_type` - The requested workflow type\n- `guidelines` - Combined workflow instructions and output format specification. Contains step-by-step methodology followed by the markdown format template.\n\n**Example:**\n```json\n{\n \"workflow_type\": \"recommendations\"\n}\n```\n\n**Important:** Call this tool first for any recommendations, comparison, or evaluation workflow. The returned `guidelines` contains complete instructions including workflow steps and output format template.\n\n**When to use each workflow:**\n\n1. **recommendations** - Solution discovery queries:\n - \"find monitoring tools for Kubernetes\"\n - \"I need a CI/CD solution\"\n - \"help me find NoSQL database solutions\"\n - \"SOC2-compliant security scanning under $5k/month\"\n\n2. **comparison** - Side-by-side analysis:\n - \"compare Datadog vs New Relic\"\n - \"differences between MongoDB Atlas and Amazon DocumentDB\"\n - \"Splunk vs Elastic for log management\"\n\n3. **evaluation** - Deep-dive on single product:\n - \"build evaluation report for Terraform Cloud\"\n - \"create a proposal for Datadog\"\n - \"should we choose Snowflake? Full analysis\"\n - \"justify purchasing New Relic to my CTO\"\n\n**📋 User Feedback (REQUIRED):** After completing any workflow, ask the user if the report was helpful and submit their feedback using `submit_aws_marketplace_feedback`:\n- Positive: User found response helpful (thumbs up)\n- Negative: Ask which categories apply (irrelevant, incomplete, inaccurate, other) and optionally collect detailed feedback text"
121300
+ },
121301
+ {
121302
+ "slug": "AWS_MARKETPLACE_MCP_GET_AWS_MARKETPLACE_SOLUTION",
121303
+ "name": "Get aws marketplace solution",
121304
+ "description": "Direct AWS Marketplace Catalog API call. Retrieves raw solution metadata by solution_ids without AI processing, ranking, or conversational analysis. Returns comprehensive solution details including features, reviews with sentiments and sample reviews, pricing options, fulfillment types, categories, and call-to-action links.\n\n**Input Parameters:**\n\n- **solution_ids** (required): Array of solution IDs (max 10). IDs start with `prodview-`, not `prod-`\n\n**Returns:** `{ solutions: [...] }` - Array of solution details\n\nEach solution includes: `solution_id`, `solution_name`, `solution_description`, `solution_url`, `vendor_name`, `vendor_url`, `highlights` array, `reviews_summary` with count/rating, `review_sentiments` array by category (functionality, ease_of_use, customer_service, cost_effectiveness) with scores and sample_reviews, optional `free_trial_available`, `pricing_options` array with name/description, optional `fulfillment_options_types` (e.g., SaaS, Container), optional `categories` (e.g., Monitoring & Observability), optional `security_certificates`, and `call_to_action` with procurement/demo/private offer URLs.\n\n**Example:**\n```json\n{\n \"solution_ids\": [\"prodview-abc123\", \"prodview-xyz789\"]\n}\n```\n\n**Use this tool ONLY when:**\n\n- You have exact solution_ids and need raw catalog data\n- Building programmatic integrations requiring unprocessed solution information\n- User explicitly requests raw API response for specific solutions\n- Need direct access to solution metadata without conversational context\n\n**DO NOT use this tool for:**\n\n- Solution discovery or search queries → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n- User asking \"tell me about [solution]\" → Use `get_aws_marketplace_report_guidelines` with `evaluation` workflow\n- Comparative analysis → Use `get_aws_marketplace_report_guidelines` with `comparison` workflow\n- Recommendations or evaluations → Use `get_aws_marketplace_report_guidelines` to get workflow instructions first\n\n**Note:** This is a stateless tool that does not require a conversation or request_id.\n\n**⚠️ CRITICAL:** For any recommendation, comparison, or evaluation, first call `get_aws_marketplace_report_guidelines` to get the step-by-step guide and output format.\n\n**CRITICAL: When displaying URLs from this response (solution_url, vendor_url, procurement_url, request_for_demo_url, etc.), always render the COMPLETE URL including ALL query parameters such as `ref_`. Do not truncate or simplify these URLs. These parameters are required for attribution tracking.**"
121305
+ },
121306
+ {
121307
+ "slug": "AWS_MARKETPLACE_MCP_RESEARCH_AWS_MARKETPLACE_SOLUTION",
121308
+ "name": "Research aws marketplace solution",
121309
+ "description": "Deep web research tool for AWS Marketplace solutions. Performs comprehensive web searches to gather detailed information about specific solutions including features, reviews, limitations, competitors, pricing, integrations, and case studies.\n\n**Input Parameters:**\n\n- **solution_ids** (required): Array of solution IDs (max 5) to research. IDs start with `prodview-`, not `prod-`\n- **sections** (optional): Array of specific sections to research. Default: all sections.\n\n**Section Reference:**\n| Section | Returns |\n|---------|---------|\n| features | Official documentation, capabilities, specifications |\n| reviews | G2, Gartner, TrustRadius customer feedback |\n| limitations | Known issues, drawbacks, criticisms |\n| competitors | Competitive positioning, alternatives |\n| pricing | Cost information, pricing models, tiers |\n| integrations | AWS ecosystem, APIs, third-party tools |\n| case_studies | Customer success stories, testimonials, ROI |\n\n**Returns:** `{ results: [...] }` - Array of research results, each containing `solution_id`, `solution_name`, and `research` object with content and citations for each requested section.\n\n**Examples:**\n\n*Comparison workflow (features + integrations only - reviews already available from get_aws_marketplace_solution catalog data):*\n```json\n{\n \"solution_ids\": [\"prodview-abc123\", \"prodview-xyz789\"],\n \"sections\": [\"features\", \"integrations\"]\n}\n```\n\n*Evaluation workflow (comprehensive research for proposal documents):*\n```json\n{\n \"solution_ids\": [\"prodview-abc123\"],\n \"sections\": [\"features\", \"reviews\", \"limitations\", \"case_studies\"]\n}\n```\n\n*General research:*\n```json\n{\n \"solution_ids\": [\"prodview-abc123\"],\n \"sections\": [\"features\", \"reviews\", \"pricing\", \"integrations\"]\n}\n```\n\n**Use this tool when:**\n\n- You need detailed research beyond basic catalog metadata\n- User asks for in-depth analysis of specific solutions\n- Gathering third-party reviews and testimonials\n- Researching competitor comparisons or alternatives\n- Understanding pricing models and cost structures\n\n**Note:** This tool performs web searches and may take longer than catalog API calls. Results include citations linking to source materials.\n\n**⚠️ CRITICAL:** For any recommendation, comparison, or evaluation, first call `get_aws_marketplace_report_guidelines` to get the step-by-step guide and output format."
121310
+ },
121311
+ {
121312
+ "slug": "AWS_MARKETPLACE_MCP_SEARCH_AWS_MARKETPLACE_SOLUTIONS",
121313
+ "name": "Search aws marketplace solutions",
121314
+ "description": "Direct AWS Marketplace Catalog API search. Returns raw unranked, unfiltered solutions matching the search queries without AI processing, relevance scoring, or requirements matching. Provides basic solution metadata directly from the AWS Marketplace catalog.\n\n**Input Parameters:**\n\n- **queries** (required): Array of search queries (max 10)\n- **max_results** (optional): Maximum number of solutions to return per query\n- **cursor** (optional): Pagination cursor (only works for single query, ignored for batch)\n\n**Returns:** `{ results: [...], next_cursor: ... }` - Array of search results with optional pagination cursor\n\nEach result includes: solution_id, solution_name, vendor_name, vendor_url, solution_description, solution_url.\n\n**Example:**\n```json\n{\n \"queries\": [\"Drata compliance\", \"Vanta compliance\"],\n \"max_results\": 5\n}\n```\n\n**Use this tool ONLY when:**\n\n- Building programmatic integrations requiring raw search API access\n- Need unprocessed search results for custom processing\n- User explicitly requests raw AWS Marketplace search API response\n- Direct access to catalog search without AI analysis is required\n\n**DO NOT use this tool for:**\n\n- Solution discovery queries → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n- User asking \"find [solution type]\" → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n- Requirements-based search → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n- Recommendations or comparisons → Use `get_aws_marketplace_report_guidelines` to get workflow instructions first\n- Any conversational queries about finding solutions → Use `get_aws_marketplace_report_guidelines` with `recommendations` workflow\n\n**Pagination:** If `next_cursor` is returned (only for single-query requests), call this tool again with the same query and the `cursor` value to retrieve additional solutions. When `next_cursor` is `null`, all matching solutions have been retrieved.\n\n**Note:** This is a stateless tool that does not require a conversation or request_id. Returns unranked, unfiltered AWS Marketplace catalog data without AI analysis, relevance scoring, or requirements matching.\n\n**⚠️ CRITICAL:** For any recommendation, comparison, or evaluation, first call `get_aws_marketplace_report_guidelines` to get the step-by-step guide and output format.\n\n**CRITICAL: When displaying URLs from this response (solution_url, vendor_url), always render the COMPLETE URL including ALL query parameters such as `ref_`. Do not truncate or simplify these URLs. These parameters are required for attribution tracking.**"
121315
+ },
121316
+ {
121317
+ "slug": "AWS_MARKETPLACE_MCP_SUBMIT_AWS_MARKETPLACE_FEEDBACK",
121318
+ "name": "Submit aws marketplace feedback",
121319
+ "description": "Submit user feedback about AWS Marketplace responses.\n\n**IMPORTANT: After completing any AWS Marketplace workflow, you MUST ask the user if they found the report helpful and submit their feedback using this tool.**\n\n**Input Parameters:**\n\n- **sentiment** (required): User sentiment\n - `\"positive\"` - Response was helpful (thumbs up)\n - `\"negative\"` - Response was not helpful (thumbs down)\n\n- **categories** (optional, for negative feedback): Array of feedback categories\n - `\"irrelevant\"` - Didn't address the question\n - `\"incomplete\"` - Missing important information\n - `\"inaccurate\"` - Contained errors\n - `\"other\"` - Other issues\n\n- **feedback_text** (optional): Free-form feedback (max 1000 characters)\n\n**Returns:** `{ success: boolean, message: string }`\n\n**Examples:**\n\nPositive feedback:\n```json\n{ \"sentiment\": \"positive\", \"feedback_text\": \"Great recommendations!\" }\n```\n\nNegative feedback with categories:\n```json\n{\n \"sentiment\": \"negative\",\n \"categories\": [\"incomplete\", \"other\"],\n \"feedback_text\": \"Missing pricing details\"\n}\n```\n\n**Feedback collection flow:**\n1. Complete the user's request (recommendation, comparison, evaluation)\n2. Ask: \"Was this response helpful? (thumbs up/thumbs down)\"\n3. If negative, ask which categories apply\n4. Optionally collect additional text feedback\n5. Submit using this tool"
121320
+ }
121321
+ ],
121322
+ "triggers": [],
121323
+ "authConfigDetails": [
121324
+ {
121325
+ "mode": "NO_AUTH",
121326
+ "name": "AWS_MARKETPLACE_MCP_NO_AUTH",
121327
+ "fields": {
121328
+ "auth_config_creation": {
121329
+ "required": [],
121330
+ "optional": []
121331
+ },
121332
+ "connected_account_initiation": {
121333
+ "required": [],
121334
+ "optional": []
121335
+ }
121336
+ }
121337
+ }
121338
+ ]
121339
+ },
121340
{
121341
"slug": "ayrshare",
121342
"name": "Ayrshare",
139265
}
139266
]
139267
},
139268
+ {
139269
+ "slug": "clarity_ai_mcp",
139270
+ "name": "Clarity AI MCP",
139271
+ "logo": "https://logos.composio.dev/api/clarity_ai_mcp",
139272
+ "description": "Simulate SFDR 2.0 fund classifications from name, ISIN, or CUSIP using Clarity AI's disclosure data and modeling.",
139273
+ "category": "analytics",
139274
+ "authSchemes": [
139275
+ "NO_AUTH"
139276
+ ],
139277
+ "toolCount": 6,
139278
+ "triggerCount": 0,
139279
+ "version": "20260730_01",
139280
+ "tools": [
139281
+ {
139282
+ "slug": "CLARITY_AI_MCP_INTERPRET_SFDR20_RESULT",
139283
+ "name": "Interpret sfdr20 result",
139284
+ "description": "Normalize raw SFDR20 flags into category-level assessment evidence."
139285
+ },
139286
+ {
139287
+ "slug": "CLARITY_AI_MCP_SEARCH_SECURITIES",
139288
+ "name": "Search securities",
139289
+ "description": "Search securities by keyword, ISIN, or CUSIP through the upstream Clarity SFDR demo API."
139290
+ },
139291
+ {
139292
+ "slug": "CLARITY_AI_MCP_SFDR20_ASSESS_FUND_NAME",
139293
+ "name": "Sfdr20 assess fund name",
139294
+ "description": "Preferred for fund names, partial names, and natural-language requests. Resolve a fund from free-text (for example S&P 500 or Nordea 1 Global Climate and Environment), then run the SFDR20 check and return an interpreted assessment. Example: use this for 'Show the SFDR 2.0 category assessment evidence for Nordea 1 Global Climate and Environment Fund'."
139295
+ },
139296
+ {
139297
+ "slug": "CLARITY_AI_MCP_SFDR20_CHECK",
139298
+ "name": "Sfdr20 check",
139299
+ "description": "Deprecated alias for sfdr20_check_by_isin. Keep for backward compatibility only. Do not use for fund names or natural-language requests."
139300
+ },
139301
+ {
139302
+ "slug": "CLARITY_AI_MCP_SFDR20_CHECK_BY_ISIN",
139303
+ "name": "Sfdr20 check by isin",
139304
+ "description": "Use only when the user already provided an explicit ISIN. Do not use for fund names, partial names, or natural-language fund requests; use sfdr20_assess_fund_name instead."
139305
+ },
139306
+ {
139307
+ "slug": "CLARITY_AI_MCP_SFDR20_CHECK_BY_QUERY",
139308
+ "name": "Sfdr20 check by query",
139309
+ "description": "Deprecated alias for sfdr20_assess_fund_name. Keep for backward compatibility only. Prefer sfdr20_assess_fund_name for fund names and natural-language requests."
139310
+ }
139311
+ ],
139312
+ "triggers": [],
139313
+ "authConfigDetails": [
139314
+ {
139315
+ "mode": "NO_AUTH",
139316
+ "name": "CLARITY_AI_MCP_NO_AUTH",
139317
+ "fields": {
139318
+ "auth_config_creation": {
139319
+ "required": [],
139320
+ "optional": []
139321
+ },
139322
+ "connected_account_initiation": {
139323
+ "required": [],
139324
+ "optional": []
139325
+ }
139326
+ }
139327
+ }
139328
+ ]
139329
+ },
139330
{
139331
"slug": "classmarker",
139332
"name": "Classmarker",
147078
],
147079
"toolCount": 384,
147080
"triggerCount": 0,
146681
- "version": "20260721_00",
147081
+ "version": "20260729_00",
147082
"tools": [
147083
{
147084
"slug": "COUPA_ABANDON_AN_INVOICE",
152377
],
152378
"toolCount": 427,
152379
"triggerCount": 0,
151980
- "version": "20260721_00",
152380
+ "version": "20260729_00",
152381
"tools": [
152382
{
152383
"slug": "DATABRICKS_ADD_MEMBER_TO_SECURITY_GROUP",
158462
}
158463
]
158464
},
158465
+ {
158466
+ "slug": "dice_mcp",
158467
+ "name": "Dice MCP",
158468
+ "logo": "https://logos.composio.dev/api/dice_mcp",
158469
+ "description": "Search Dice's tech-job database with conversational filters for role, company, location, and employment type.",
158470
+ "category": "hr talent & recruitment",
158471
+ "authSchemes": [
158472
+ "NO_AUTH"
158473
+ ],
158474
+ "toolCount": 2,
158475
+ "triggerCount": 0,
158476
+ "version": "20260730_01",
158477
+ "tools": [
158478
+ {
158479
+ "slug": "DICE_MCP_GET_CANDIDATE",
158480
+ "name": "Get candidate",
158481
+ "description": "Retrieve a Dice candidate's profile by candidate ID. Returns career info, skills, ideal job preferences, company preferences, and education.\n\nUse this tool when you already have a candidateId and need that candidate's profile details.\nDO NOT use for: searching/discovering candidates by keyword (use a candidate search tool instead), or for job listings.\n\nArgs:\n candidate_id: The unique identifier of the candidate to retrieve (required)\n\nReturns:\n CandidateResult: Contains:\n - data: CandidateData with candidateId, profileTitle, careerInfo (years of experience,\n work authorization, employment history, resume), skills, idealJob, companyPreference,\n and education\n\nRaises:\n Exception: If API call fails, the candidate is not found, or input validation errors occur\n"
158482
+ },
158483
+ {
158484
+ "slug": "DICE_MCP_SEARCH_JOBS",
158485
+ "name": "Search jobs",
158486
+ "description": "Search for job listings by keyword, location, and filters. Returns job details, company info, and application links.\n\nUse this tool when users want to find jobs, search employment opportunities, or explore job openings.\nDO NOT use for: applying to jobs, submitting applications, or making employment decisions.\n\nLLM USAGE INSTRUCTIONS:\n- ALWAYS provide the keyword parameter (required)\n- When presenting results to users, include BOTH the job details URL (detailsPageUrl)\n AND the company page URL (companyPageUrl) for each job\n- Use location to find geographically relevant positions\n- Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work)\n- Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days)\n- Default jobs_per_page is reasonable, increase for comprehensive searches\n\nIMPORTANT - AI DISCLOSURE REQUIREMENT:\nWhen presenting job search results to users, you MUST include an appropriate disclosure\nthat these results were retrieved using AI assistance. Example disclosure language:\n\"These job listings were found using AI-powered search. Please review all job details\ncarefully and verify information directly with employers before applying.\"\n\nThis tool provides job listing data only. Final employment decisions should always\ninvolve human judgment and direct review of complete job postings.\n\nArgs:\n keyword: The job keyword or title to search for (required)\n location: Geographic location for the job search (city, state, country)\n radius: Search radius from the specified location (minimum 1.0)\n radius_unit: Unit for search radius. Options: 'mi', 'km', 'miles', 'kilometers'\n jobs_per_page: Number of jobs to return per page (1-100, default handled by API)\n page_number: Page number for pagination (1-based, default is 1)\n posted_date: Filter by posting date. Options: 'ONE' (1 day), 'THREE' (3 days), 'SEVEN' (7 days)\n workplace_types: Workplace arrangements. Options: 'Remote', 'On-Site', 'Hybrid'\n employment_types: Employment types. Options: 'FULLTIME', 'CONTRACTS', 'PARTTIME', 'THIRD_PARTY'\n employer_types: Employer types. Options: 'Direct Hire', 'Recruiter', 'Other'\n willing_to_sponsor: Filter for employers willing to sponsor work authorization (boolean)\n easy_apply: Filter for jobs with easy application process (boolean)\n fields: Specific fields to include in response (optional, returns all fields by default)\n\nReturns:\n JobSearchResult: Contains:\n - data: List of JobDisplayFields with job details including:\n * detailsPageUrl: Direct link to full job posting\n * companyPageUrl: Link to company profile page\n * title, summary, salary, location, employmentType, etc.\n - meta: Search metadata with pagination info and facet results\n - _links: Pagination navigation links\n\nRaises:\n Exception: If API call fails or input validation errors occur\n"
158487
+ }
158488
+ ],
158489
+ "triggers": [],
158490
+ "authConfigDetails": [
158491
+ {
158492
+ "mode": "NO_AUTH",
158493
+ "name": "DICE_MCP_NO_AUTH",
158494
+ "fields": {
158495
+ "auth_config_creation": {
158496
+ "required": [],
158497
+ "optional": []
158498
+ },
158499
+ "connected_account_initiation": {
158500
+ "required": [],
158501
+ "optional": []
158502
+ }
158503
+ }
158504
+ }
158505
+ ]
158506
+ },
158507
{
158508
"slug": "dictionary_api",
158509
"name": "Dictionary Api",
169237
}
169238
]
169239
},
169240
+ {
169241
+ "slug": "excalidraw_mcp",
169242
+ "name": "Excalidraw MCP",
169243
+ "logo": "https://logos.composio.dev/api/excalidraw_mcp",
169244
+ "description": "Create hand-drawn style diagrams in Excalidraw with viewport camera control and fullscreen editing.",
169245
+ "category": "images & design",
169246
+ "authSchemes": [
169247
+ "NO_AUTH"
169248
+ ],
169249
+ "toolCount": 5,
169250
+ "triggerCount": 0,
169251
+ "version": "20260730_01",
169252
+ "tools": [
169253
+ {
169254
+ "slug": "EXCALIDRAW_MCP_CREATE_VIEW",
169255
+ "name": "Create view",
169256
+ "description": "Renders a hand-drawn diagram using Excalidraw elements.\nElements stream in one by one with draw-on animations.\nCall read_me first to learn the element format."
169257
+ },
169258
+ {
169259
+ "slug": "EXCALIDRAW_MCP_EXPORT_TO_EXCALIDRAW",
169260
+ "name": "Export to excalidraw",
169261
+ "description": "Upload diagram to excalidraw.com and return shareable URL."
169262
+ },
169263
+ {
169264
+ "slug": "EXCALIDRAW_MCP_READ_CHECKPOINT",
169265
+ "name": "Read checkpoint",
169266
+ "description": "Read checkpoint state for restore."
169267
+ },
169268
+ {
169269
+ "slug": "EXCALIDRAW_MCP_READ_ME",
169270
+ "name": "Read me",
169271
+ "description": "Returns the Excalidraw element format reference with color palettes, examples, and tips. Call this BEFORE using create_view for the first time."
169272
+ },
169273
+ {
169274
+ "slug": "EXCALIDRAW_MCP_SAVE_CHECKPOINT",
169275
+ "name": "Save checkpoint",
169276
+ "description": "Update checkpoint with user-edited state."
169277
+ }
169278
+ ],
169279
+ "triggers": [],
169280
+ "authConfigDetails": [
169281
+ {
169282
+ "mode": "NO_AUTH",
169283
+ "name": "EXCALIDRAW_MCP_NO_AUTH",
169284
+ "fields": {
169285
+ "auth_config_creation": {
169286
+ "required": [],
169287
+ "optional": []
169288
+ },
169289
+ "connected_account_initiation": {
169290
+ "required": [],
169291
+ "optional": []
169292
+ }
169293
+ }
169294
+ }
169295
+ ]
169296
+ },
169297
{
169298
"slug": "excel",
169299
"name": "Excel",
175539
],
175540
"toolCount": 76,
175541
"triggerCount": 0,
175043
- "version": "20260721_00",
175542
+ "version": "20260731_00",
175543
"tools": [
175544
{
175545
"slug": "FREEAGENT_CASHFLOW_SUMMARY_FOR_A_GIVEN_DATE_RANGE",
176584
],
176585
"toolCount": 8,
176586
"triggerCount": 0,
176088
- "version": "20260724_00",
176587
+ "version": "20260728_00",
176588
"tools": [
176589
{
176590
"slug": "GEMINI_COUNT_TOKENS",
178845
],
178846
"toolCount": 116,
178847
"triggerCount": 0,
178349
- "version": "20260721_00",
178848
+ "version": "20260729_00",
178849
"tools": [
178850
{
178851
"slug": "GITLAB_ADD_SPENT_TIME",
180928
}
180929
]
180930
},
180931
+ {
180932
+ "slug": "godaddy_mcp",
180933
+ "name": "GoDaddy MCP",
180934
+ "logo": "https://logos.composio.dev/api/godaddy_mcp",
180935
+ "description": "Search available domains and get AI-powered suggestions based on keywords or business ideas.",
180936
+ "category": "website & app building",
180937
+ "authSchemes": [
180938
+ "NO_AUTH"
180939
+ ],
180940
+ "toolCount": 2,
180941
+ "triggerCount": 0,
180942
+ "version": "20260730_01",
180943
+ "tools": [
180944
+ {
180945
+ "slug": "GODADDY_MCP_DOMAINS_CHECK_AVAILABILITY",
180946
+ "name": "Domains check availability",
180947
+ "description": "Check if domain names are available for registration. Works with single domains or lists of multiple domains. Returns formatted results with availability status and registration options ready for display. IMPORTANT: Always display the registration links from the response to the user - each domain has a direct GoDaddy registration URL that must be shown."
180948
+ },
180949
+ {
180950
+ "slug": "GODADDY_MCP_DOMAINS_SUGGEST",
180951
+ "name": "Domains suggest",
180952
+ "description": "Generate domain name suggestions based on keywords, seed domains, or business descriptions. Returns an interactive widget with clickable domain links for clients that support HTML rendering (browsers, web-based AI assistants), with automatic fallback to formatted text for other clients. IMPORTANT: Always display the registration links from the response to the user - each domain has a direct GoDaddy registration URL that must be shown."
180953
+ }
180954
+ ],
180955
+ "triggers": [],
180956
+ "authConfigDetails": [
180957
+ {
180958
+ "mode": "NO_AUTH",
180959
+ "name": "GODADDY_MCP_NO_AUTH",
180960
+ "fields": {
180961
+ "auth_config_creation": {
180962
+ "required": [],
180963
+ "optional": []
180964
+ },
180965
+ "connected_account_initiation": {
180966
+ "required": [],
180967
+ "optional": []
180968
+ }
180969
+ }
180970
+ }
180971
+ ]
180972
+ },
180973
{
180974
"slug": "godial",
180975
"name": "Godial",
183688
],
183689
"toolCount": 4,
183690
"triggerCount": 0,
183150
- "version": "20260206_00",
183691
+ "version": "20260731_02",
183692
"tools": [
183693
{
183694
"slug": "GRANOLA_MCP_GET_MEETINGS",
183762
}
183763
]
183764
},
183765
+ {
183766
+ "slug": "granted_mcp",
183767
+ "name": "Granted MCP",
183768
+ "logo": "https://logos.composio.dev/api/granted_mcp",
183769
+ "description": "Discover grant opportunities across funders, with eligibility and deadline details.",
183770
+ "category": "fundraising",
183771
+ "authSchemes": [
183772
+ "NO_AUTH"
183773
+ ],
183774
+ "toolCount": 5,
183775
+ "triggerCount": 0,
183776
+ "version": "20260730_01",
183777
+ "tools": [
183778
+ {
183779
+ "slug": "GRANTED_MCP_GET_FUNDER",
183780
+ "name": "Get funder",
183781
+ "description": "Get a full foundation profile including mission, 5-year financials, recent grants awarded, key officers, and application info. Accepts a foundation slug (from search_funders results) or EIN (e.g. '13-1684331')."
183782
+ },
183783
+ {
183784
+ "slug": "GRANTED_MCP_GET_GRANT",
183785
+ "name": "Get grant",
183786
+ "description": "Get full details for a specific grant by its slug. Returns eligibility criteria, application link, deadline, amount, funder info, and tags. Use search_grants first to find valid slugs."
183787
+ },
183788
+ {
183789
+ "slug": "GRANTED_MCP_GET_PAST_WINNERS",
183790
+ "name": "Get past winners",
183791
+ "description": "Competitive intelligence: see who has won a specific federal grant program. Shows top recipients grouped by organization with award counts, total funding, and year-over-year trends. Filter by CFDA number, agency, program name, or state. Supports agency abbreviations: NIH, NSF, EPA, DOE, DOD, USDA, NASA, SBA, etc."
183792
+ },
183793
+ {
183794
+ "slug": "GRANTED_MCP_SEARCH_FUNDERS",
183795
+ "name": "Search funders",
183796
+ "description": "Search 133,000+ US foundations by name, state, NTEE code, asset range, and annual income range. Returns key metrics: name, state, total assets, annual income (from IRS 990), NTEE category, and mission. Use get_funder with the returned slug for full profiles including actual giving history."
183797
+ },
183798
+ {
183799
+ "slug": "GRANTED_MCP_SEARCH_GRANTS",
183800
+ "name": "Search grants",
183801
+ "description": "Search 140,000+ grant opportunities by keyword, state, source type, funder, and more. Uses semantic search (embeddings + full-text + scoring) combined with live AI-powered web discovery for comprehensive results. Returns active grants ranked by relevance with fit scores, deadlines, amounts, and application links. Use this as the starting point to find relevant grants."
183802
+ }
183803
+ ],
183804
+ "triggers": [],
183805
+ "authConfigDetails": [
183806
+ {
183807
+ "mode": "NO_AUTH",
183808
+ "name": "GRANTED_MCP_NO_AUTH",
183809
+ "fields": {
183810
+ "auth_config_creation": {
183811
+ "required": [],
183812
+ "optional": []
183813
+ },
183814
+ "connected_account_initiation": {
183815
+ "required": [],
183816
+ "optional": []
183817
+ }
183818
+ }
183819
+ }
183820
+ ]
183821
+ },
183822
{
183823
"slug": "graphhopper",
183824
"name": "Graphhopper",
185895
],
185896
"toolCount": 192,
185897
"triggerCount": 0,
185300
- "version": "20260721_00",
185898
+ "version": "20260729_00",
185899
"tools": [
185900
{
185901
"slug": "GUSTO_ADD_EMPLOYEES_TO_HOLIDAY_PAY_POLICY",
192756
],
192757
"toolCount": 135,
192758
"triggerCount": 0,
192161
- "version": "20260721_00",
192759
+ "version": "20260729_00",
192760
"tools": [
192761
{
192762
"slug": "HUGGING_FACE_CHANGE_DISCUSSIONS_STATUS",
196327
],
196328
"toolCount": 36,
196329
"triggerCount": 0,
195732
- "version": "20260721_00",
196330
+ "version": "20260730_00",
196331
"tools": [
196332
{
196333
"slug": "INSTAGRAM_CREATE_CAROUSEL_CONTAINER",
196352
{
196353
"slug": "INSTAGRAM_DELETE_MESSENGER_PROFILE",
196354
"name": "Delete Messenger Profile",
195757
- "description": "Tool to delete messenger profile settings for an Instagram account. Use when you need to remove ice breakers, persistent menu, greeting messages, or other messaging configuration from the messenger profile."
196355
+ "description": "Delete ice breakers or a persistent menu from an Instagram messenger profile."
196356
},
196357
{
196358
"slug": "INSTAGRAM_GET_CONVERSATION",
196406
},
196407
{
196408
"slug": "INSTAGRAM_GET_IG_USER_TAGS",
195811
- "name": "Get IG User Tags",
195812
- "description": "Get Instagram media where the user has been tagged by other users. Use when you need to retrieve all media in which an Instagram Business or Creator account has been tagged, including tags in captions, comments, or on the media itself."
196409
+ "name": "Get IG User Tags (Deprecated)",
196410
+ "description": "Deprecated because the Instagram API with Instagram Login does not support tagging. Use a Facebook Login-based Instagram integration for tagged media."
196411
},
196412
{
196413
"slug": "INSTAGRAM_GET_MESSENGER_PROFILE",
196437
{
196438
"slug": "INSTAGRAM_GET_USER_INFO",
196439
"name": "Get User Info",
195842
- "description": "Get Instagram Business Account info including profile details and statistics. IMPORTANT: Only works for Business/Creator accounts you manage through Facebook Business Manager. Cannot query arbitrary public Instagram accounts. Use \"me\" to query your own authenticated account. NOTE: followers_count and follows_count are ONLY available when querying your own profile with ig_user_id=\"me\" - these fields return null for specific user IDs due to Instagram Graph API limitations."
196440
+ "description": "Get Instagram Business Account info including profile details and statistics. Use \"me\" to query your own authenticated account, or provide the numeric Business Account ID of an account you manage. NOTE: followers_count and follows_count are returned for your own profile (ig_user_id=\"me\"). For other accounts, follower/follow counts are surfaced through the business_discovery edge rather than this direct-node action, so they may be null here."
196441
},
196442
{
196443
"slug": "INSTAGRAM_GET_USER_INSIGHTS",
196482
{
196483
"slug": "INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH",
196484
"name": "Publish IG User Media",
195887
- "description": "Tool to publish a media container to an Instagram Business account. This action automatically waits for the container to finish processing before publishing. Rate limited to 25 API-published posts per 24-hour moving window. The publishing process: 1. First, create a media container using INSTAGRAM_CREATE_MEDIA_CONTAINER 2. Call this action with the creation_id - it will automatically poll for FINISHED status 3. Once ready, the media is published and the published media ID is returned For videos/reels, processing may take 30-120 seconds. Images are typically instant."
196485
+ "description": "Tool to publish a media container to an Instagram Business account. This action automatically waits for the container to finish processing before publishing. Instagram enforces an account-specific content-publishing rate limit over a 24-hour moving window; the exact cap varies by account and should be read live via INSTAGRAM_GET_IG_USER_CONTENT_PUBLISHING_LIMIT before bulk publishing. The publishing process: 1. First, create a media container using INSTAGRAM_CREATE_MEDIA_CONTAINER 2. Call this action with the creation_id - it will automatically poll for FINISHED status 3. Once ready, the media is published and the published media ID is returned For videos/reels, processing may take 30-120 seconds. Images are typically instant."
196486
},
196487
{
196488
"slug": "INSTAGRAM_POST_IG_USER_MENTIONS",
206581
}
206582
]
206583
},
206584
+ {
206585
+ "slug": "malwarebytes_mcp",
206586
+ "name": "Malwarebytes MCP",
206587
+ "logo": "https://logos.composio.dev/api/malwarebytes_mcp",
206588
+ "description": "Verify links, emails, phone numbers, and domains against Malwarebytes threat intelligence.",
206589
+ "category": "security & identity tools",
206590
+ "authSchemes": [
206591
+ "NO_AUTH"
206592
+ ],
206593
+ "toolCount": 6,
206594
+ "triggerCount": 0,
206595
+ "version": "20260730_01",
206596
+ "tools": [
206597
+ {
206598
+ "slug": "MALWAREBYTES_MCP_REPUTATION_CHECK_EMAIL",
206599
+ "name": "Reputation-check email",
206600
+ "description": "Use this when you need to check if an email address is associated with phishing, scams, or malicious activity.\n\nChecks the email domain against threat intelligence database. Returns one of:\n- malicious: Confirmed phishing or malicious email domain\n- suspicious: Potentially dangerous email domain\n- safe: Verified legitimate email domain\n- unknown: No threat intelligence available\n\nCross-tool workflow:\n- If the email contains URLs, consider scanning them with reputation-check_link.\n- If the email contains phone numbers, consider scanning them with reputation-check_phone.\n- For unknown or suspicious verdicts, consider using reputation-whois to check domain\n registration details (age, registrar, abuse contact).\n\nDo not use this for email validation, mailbox verification, or general email lookup services."
206601
+ },
206602
+ {
206603
+ "slug": "MALWAREBYTES_MCP_REPUTATION_CHECK_LINK",
206604
+ "name": "Reputation-check link",
206605
+ "description": "Use this when you need to check if a link or URL is safe, suspicious, or malicious.\n\nProvides reputation verdict based on threat intelligence database. Returns one of:\n- malicious: Confirmed harmful link\n- suspicious: Potentially dangerous link\n- safe: Verified safe link\n- unknown: No threat intelligence available\n\nCross-tool workflow:\n- For unknown or suspicious verdicts, consider using reputation-whois to check domain\n registration details (age, registrar, abuse contact).\n- If the URL redirects to a different domain, consider scanning the destination URL separately.\n- If the URL came from an email or text message, consider checking the sender with\n reputation-check_email or reputation-check_phone.\n\nDo not use this for general web searches, content fetching, or webpage analysis."
206606
+ },
206607
+ {
206608
+ "slug": "MALWAREBYTES_MCP_REPUTATION_CHECK_PHONE",
206609
+ "name": "Reputation-check phone",
206610
+ "description": "Use this when you need to check if a phone number is associated with scams or suspicious activity.\n\nProvides reputation verdict and additional phone information. Returns one of:\n- malicious: Confirmed scam or spam phone number\n- suspicious: Potentially dangerous number\n- safe: Verified legitimate number\n- unknown: No threat intelligence available\n\nAlso provides optional details like carrier, location, and phone type when available.\n\nCross-tool workflow:\n- If the caller provided links, consider scanning them with reputation-check_link.\n- If the caller provided email addresses, consider scanning them with reputation-check_email.\n\nDo not use this for phone number lookups, caller ID services, or general phone directory searches."
206611
+ },
206612
+ {
206613
+ "slug": "MALWAREBYTES_MCP_REPUTATION_REPORT",
206614
+ "name": "Reputation-report",
206615
+ "description": "Use this when a user wants to report a suspicious link, email address, or phone number.\n\nSubmits the indicator to the threat intelligence system for analysis.\nOnly use when explicitly requested by the user.\n\nDo not use this to automatically report every checked item."
206616
+ },
206617
+ {
206618
+ "slug": "MALWAREBYTES_MCP_REPUTATION_SCAN_ALL",
206619
+ "name": "Reputation-scan all",
206620
+ "description": "Use this when you need to check multiple links, emails, or phone numbers at once.\n\nScans all indicators concurrently and returns a unified result. Each indicator needs:\n- type: 'url', 'email', or 'phone'\n- value: the URL, email address, or phone number (E.164 format for phones)\n\nReturns a summary with counts per verdict and individual results for each indicator.\nPrefer this over individual scan tools when 3 or more indicators are present.\nMaximum 10 indicators per request.\n\nCross-tool workflow:\n- For unknown URL or email verdicts, consider using reputation-whois on the associated\n domains for additional registration context and abuse contact information."
206621
+ },
206622
+ {
206623
+ "slug": "MALWAREBYTES_MCP_REPUTATION_WHOIS",
206624
+ "name": "Reputation-whois",
206625
+ "description": "Use this when you need to look up domain registration information to verify legitimacy or identify suspicious patterns.\n\nProvides WHOIS/RDAP data including registrar, registration dates, name servers, and abuse contacts.\nParticularly useful for identifying newly registered domains (common in phishing and scams).\nReturns the registrar's abuse contact email when available, which can be used for filing\ncomplaints about fraudulent domains.\n\nCross-tool workflow:\n- Consider using reputation-check_link to check the domain's threat reputation alongside\n WHOIS registration data.\n\nDo not use this for general domain availability checks or bulk domain searches."
206626
+ }
206627
+ ],
206628
+ "triggers": [],
206629
+ "authConfigDetails": [
206630
+ {
206631
+ "mode": "NO_AUTH",
206632
+ "name": "MALWAREBYTES_MCP_NO_AUTH",
206633
+ "fields": {
206634
+ "auth_config_creation": {
206635
+ "required": [],
206636
+ "optional": []
206637
+ },
206638
+ "connected_account_initiation": {
206639
+ "required": [],
206640
+ "optional": []
206641
+ }
206642
+ }
206643
+ }
206644
+ ]
206645
+ },
206646
{
206647
"slug": "manus",
206648
"name": "Manus",
208832
}
208833
]
208834
},
208835
+ {
208836
+ "slug": "mermaid_chart_mcp",
208837
+ "name": "Mermaid Chart MCP",
208838
+ "logo": "https://logos.composio.dev/api/mermaid_chart_mcp",
208839
+ "description": "Validates Mermaid syntax, renders diagrams as high-quality SVG, and displays them in an interactive UI for preview, zoom, and real-time iteration.",
208840
+ "category": "images & design",
208841
+ "authSchemes": [
208842
+ "NO_AUTH"
208843
+ ],
208844
+ "toolCount": 1,
208845
+ "triggerCount": 0,
208846
+ "version": "20260730_01",
208847
+ "tools": [
208848
+ {
208849
+ "slug": "MERMAID_CHART_MCP_VALIDATE_AND_RENDER_MERMAID_DIAGRAM",
208850
+ "name": "Validate and render mermaid diagram",
208851
+ "description": "\nUse this tool to output a Mermaid diagram:\n- The tool will validate the diagram syntax and render it to a UI widget.\n- The widget will contain the diagram code, a \"Copy Code\" button, and a rendered diagram.\n- If the diagram is invalid, the widget will give user a link to repair the diagram in Mermaid Live.\n"
208852
+ }
208853
+ ],
208854
+ "triggers": [],
208855
+ "authConfigDetails": [
208856
+ {
208857
+ "mode": "NO_AUTH",
208858
+ "name": "MERMAID_CHART_MCP_NO_AUTH",
208859
+ "fields": {
208860
+ "auth_config_creation": {
208861
+ "required": [],
208862
+ "optional": []
208863
+ },
208864
+ "connected_account_initiation": {
208865
+ "required": [],
208866
+ "optional": []
208867
+ }
208868
+ }
208869
+ }
208870
+ ]
208871
+ },
208872
{
208873
"slug": "metabase",
208874
"name": "Metabase",
211233
],
211234
"toolCount": 22,
211235
"triggerCount": 0,
210539
- "version": "00000000_00",
211236
+ "version": "20260728_00",
211237
"tools": [
211238
{
211239
"slug": "MICROSOFT_TODO_COMPLETE_TASK",
214671
}
214672
]
214673
},
214674
+ {
214675
+ "slug": "mospi_mcp",
214676
+ "name": "MoSPI MCP",
214677
+ "logo": "https://logos.composio.dev/api/mospi_mcp",
214678
+ "description": "India's official statistics from the Ministry of Statistics and Programme Implementation, queryable via natural language.",
214679
+ "category": "analytics",
214680
+ "authSchemes": [
214681
+ "NO_AUTH"
214682
+ ],
214683
+ "toolCount": 4,
214684
+ "triggerCount": 0,
214685
+ "version": "20260730_01",
214686
+ "tools": [
214687
+ {
214688
+ "slug": "MOSPI_MCP_GET_DATA",
214689
+ "name": "Get data",
214690
+ "description": "Fetches statistical data from a MoSPI dataset.\n\nThis is the final step of the workflow. It requires filter values from\nget_metadata — filter codes are arbitrary (e.g., indicator_code=3 means\n\"Unemployment Rate\" in PLFS but something different in other datasets).\n\nAll filter parameters including limit and page go inside the filters dict,\nnot as top-level arguments.\n\nStep 4 of: list_datasets → get_indicators → get_metadata → get_data"
214691
+ },
214692
+ {
214693
+ "slug": "MOSPI_MCP_GET_INDICATORS",
214694
+ "name": "Get indicators",
214695
+ "description": "Returns the full list of available indicators for a given dataset.\n\nDatasets often have broader coverage than expected — for example, ASI covers\n57 indicators (capital structure, wages, employment, GVA, fuel consumption),\nand GENDER covers 147 indicators across health, education, labor, and crime.\n\nFor PLFS and ASUSE, indicators are grouped by frequency_code:\n - PLFS frequency_code=1 (Annual): all 8 indicators including wages\n - PLFS frequency_code=2 (Quarterly): indicators 1-3 only\n - PLFS frequency_code=3 (Monthly): indicators 1-3 only\n frequency_code selects the indicator set, not time granularity.\n\nStep 2 of: list_datasets → get_indicators → get_metadata → get_data"
214696
+ },
214697
+ {
214698
+ "slug": "MOSPI_MCP_GET_METADATA",
214699
+ "name": "Get metadata",
214700
+ "description": "Returns the valid filter values (states, years, quarters, etc.) for a\ngiven dataset and indicator.\n\nFilter codes are arbitrary and dataset-specific — for example, PLFS\nstate_code 99 means \"All India\", and NAS frequency_code 1 means \"Annual\".\nThese values cannot be inferred or guessed from parameter names alone.\n\nThe returned filter_values and api_params should be used as-is when\ncalling get_data.\n\nStep 3 of: list_datasets → get_indicators → get_metadata → get_data"
214701
+ },
214702
+ {
214703
+ "slug": "MOSPI_MCP_LIST_DATASETS",
214704
+ "name": "List datasets",
214705
+ "description": "Returns an overview of all MoSPI statistical datasets with descriptions and coverage.\nThis is the starting point ΓÇö call this first to identify the right dataset.\n\nThe API covers 500+ indicators across employment, prices, industry, national\naccounts, health, education, disability, housing, environment, trade, and more. Each dataset has\nits own indicator codes, filter parameters, and valid values ΓÇö these are not\nstandardized and cannot be inferred or guessed from parameter names alone.\n\nFour-step workflow (each step depends on the previous):\n 1. list_datasets() ΓÇö identify the dataset\n 2. get_indicators(dataset) ΓÇö list available indicators\n 3. get_metadata(dataset, indicator_code) ΓÇö retrieve valid filter values\n 4. get_data(dataset, filters) ΓÇö fetch the data\n\nReturns:\n dict with 'datasets' (name, description, use_for for each dataset)\n and 'workflow' (the four-step sequence)."
214706
+ }
214707
+ ],
214708
+ "triggers": [],
214709
+ "authConfigDetails": [
214710
+ {
214711
+ "mode": "NO_AUTH",
214712
+ "name": "MOSPI_MCP_NO_AUTH",
214713
+ "fields": {
214714
+ "auth_config_creation": {
214715
+ "required": [],
214716
+ "optional": []
214717
+ },
214718
+ "connected_account_initiation": {
214719
+ "required": [],
214720
+ "optional": []
214721
+ }
214722
+ }
214723
+ }
214724
+ ]
214725
+ },
214726
{
214727
"slug": "motion",
214728
"name": "Motion",
220630
],
220631
"toolCount": 43,
220632
"triggerCount": 0,
219884
- "version": "20260721_00",
220633
+ "version": "20260731_00",
220634
"tools": [
220635
{
220636
"slug": "OMNISEND_ADD_CART_PRODUCT",
224963
],
224964
"toolCount": 78,
224965
"triggerCount": 0,
224217
- "version": "20260721_00",
224966
+ "version": "20260729_00",
224967
"tools": [
224968
{
224969
"slug": "PAYPAL_ACTIVATE_PLAN",
231051
}
231052
]
231053
},
231054
+ {
231055
+ "slug": "pophive_mcp",
231056
+ "name": "PopHIVE MCP",
231057
+ "logo": "https://logos.composio.dev/api/pophive_mcp",
231058
+ "description": "Yale's harmonized US public health surveillance data, covering disease, vaccination, and health outcome trends.",
231059
+ "category": "analytics",
231060
+ "authSchemes": [
231061
+ "NO_AUTH"
231062
+ ],
231063
+ "toolCount": 7,
231064
+ "triggerCount": 0,
231065
+ "version": "20260730_01",
231066
+ "tools": [
231067
+ {
231068
+ "slug": "POPHIVE_MCP_COMPARE",
231069
+ "name": "Compare",
231070
+ "description": "Side-by-side comparison of one disease across 2–5 US places, or\nagreement between surveillance sources in one place. For\nstraightforward single-slice questions only (e.g. \"is RSV worse in CT\nthan NY?\", \"do wastewater and ED visits agree on COVID?\"). If the\nanswer needs anything beyond reading one precomputed evidence block,\nuse get_data.\n\nExamples: \"Is RSV worse in CT than NY?\", \"Compare diabetes in Texas vs\nCalifornia\", \"Do wastewater and ED visits agree on COVID?\"\n\nNot for: one place's status (get_current_status), ranking many places\n(get_map).\n\nCall example: compare(disease='covid', geographies=['Texas', 'Florida'])\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231071
+ },
231072
+ {
231073
+ "slug": "POPHIVE_MCP_GET_COVERAGE",
231074
+ "name": "Get coverage",
231075
+ "description": "US childhood vaccination coverage — the rate for one vaccine in one\nplace and whether it meets targets. For straightforward single-slice\nquestions only (e.g. \"kindergarten MMR rate in Idaho?\", \"is Texas\nbelow 95% MMR?\"). If the answer needs anything beyond reading one\nprecomputed evidence block, use get_data.\n\nExamples: \"Kindergarten MMR rate in Idaho?\", \"Is Texas below 95% MMR?\",\n\"Polio vaccination rate in Connecticut.\"\n\nNot for: disease activity (get_current_status), trends (get_trend),\ncoverage rankings across states (get_map with disease='mmr').\n\nCall example: get_coverage(vaccine='mmr', geography='Idaho')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231076
+ },
231077
+ {
231078
+ "slug": "POPHIVE_MCP_GET_CURRENT_STATUS",
231079
+ "name": "Get current status",
231080
+ "description": "Current-status verdict for one disease in one US place — level,\ndirection, and risk right now. For straightforward single-slice\nquestions only (e.g. \"is flu rising in Texas?\", \"how bad is COVID\nnationally?\"). If the answer needs anything beyond reading one\nprecomputed evidence block, use get_data.\n\nExamples: \"Is RSV rising in Connecticut?\", \"How bad is flu nationally?\",\n\"What is the risk of measles in Texas?\", \"Current COVID situation in\nNew York.\"\n\nNot for: trends over time (get_trend), ranking geographies (get_map),\nvaccination coverage (get_coverage).\n\nCall example: get_current_status(disease='rsv', geography='Connecticut')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231081
+ },
231082
+ {
231083
+ "slug": "POPHIVE_MCP_GET_DATA",
231084
+ "name": "Get data",
231085
+ "description": "Data catalog and raw-data gateway. The six specialized tools answer\nsingle-slice questions — current status, trend, map/ranking, A-vs-B\ncompare, coverage — with server-verified evidence; try them first,\nescalating here costs one call. Use get_data when evidence can't carry\nthe answer: multi-stratum gaps, history beyond the served window,\ncomplete lists, cross-dataset joins, custom math. Flow: (1) catalog,\n(2) disease='about' for the guide, (3) view schema + data_url,\n(4) download and compute — results are yours but carry the caveats and\naren't server-verified. include_query=true returns a runnable pandas\nsnippet.\n\nTopics: adhd, annual_wellness_visit, anxiety, breast_cancer_screening, cardiovascular_screening, cervical_cancer_screening, chlamydia_screening, colorectal_cancer_screening, combined7, covid19, depression, depression_screening, diabetes, diabetes_screening, dtap, firearm_injury, flu_vaccine_adult, heat_illness, hepa, hepb, hib, influenza, injury_deaths, measles, mmr, obesity, opioid_overdose, opioid_use_disorder, pcv, pelvic_exam, pneumococcal_vaccine_adult, polio, prostate_cancer_screening, rotavirus, rsv, vaccine_exemptions, varicella.\n\nExamples: \"What does PopHIVE track?\", \"Do you have Lyme disease data?\",\n\"Vaccination gaps across insurance types\", \"Raw RSV data for\nConnecticut.\"\n\nNot for: 'is flu rising in Texas?' → get_current_status; 'rank states\nby COVID wastewater' → get_map; 'is RSV worse in CT than NY?' → compare.\n\nCall example: get_data(disease='rsv', view='overall_trend')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231086
+ },
231087
+ {
231088
+ "slug": "POPHIVE_MCP_GET_MAP",
231089
+ "name": "Get map",
231090
+ "description": "Geographic ranking — which US states or counties are highest or lowest\non one disease, by current level or recent change. For straightforward\nsingle-slice questions only (e.g. \"which counties have the highest\nRSV?\", \"how does Texas rank on flu?\"). If the answer needs anything\nbeyond reading one precomputed evidence block, use get_data.\n\nExamples: \"What parts of the US have the highest rates of flu right\nnow?\", \"How do diabetes rates differ across the US by county?\", \"How\ndoes Texas rank?\", \"Which states are improving fastest on opioid\noverdose?\"\n\nNot for: trends over time (get_trend), one place's status\n(get_current_status).\n\nCall example: get_map(disease='flu', geo_level='state', top_n=10)\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231091
+ },
231092
+ {
231093
+ "slug": "POPHIVE_MCP_GET_OVERVIEW",
231094
+ "name": "Get overview",
231095
+ "description": "Cross-disease situation report for one US state or the nation — what's\nelevated, rising, declining, or stale across every PopHIVE topic. For\nstraightforward single-slice questions only (e.g. \"anything elevated\nin Connecticut?\", \"public health sitrep for Florida?\"). If the answer\nneeds anything beyond reading one precomputed evidence block, use\nget_data.\n\nExamples: \"What's going on health-wise in Texas?\", \"Public health sitrep\nfor Florida\", \"Anything elevated in Connecticut?\"\n\nNot for: a single disease (get_current_status), time series (get_trend),\nranking states by one disease (get_map).\n\nCall example: get_overview(geography='Texas')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231096
+ },
231097
+ {
231098
+ "slug": "POPHIVE_MCP_GET_TREND",
231099
+ "name": "Get trend",
231100
+ "description": "Trend over time for one disease in one US place — direction, peak, and\nchange, optionally stratified or pinned to one source. For\nstraightforward single-slice questions only (e.g. \"how has RSV changed\nsince January?\", \"flu trend in Ohio\"). If the answer needs anything\nbeyond reading one precomputed evidence block, use get_data.\n\nExamples: \"What are the latest trends in COVID?\", \"How has flu changed\nsince January?\", \"Diabetes trend in Ohio over 5 years.\"\n\nseason_over_season evidence compares the current season to the\nimmediately prior season only; for older seasons use get_data.\n\nNot for: a current-status verdict (get_current_status), ranking\ngeographies (get_map), vaccination coverage (get_coverage).\n\nCall example: get_trend(disease='flu', geography='US', period='12w')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."
231101
+ }
231102
+ ],
231103
+ "triggers": [],
231104
+ "authConfigDetails": [
231105
+ {
231106
+ "mode": "NO_AUTH",
231107
+ "name": "POPHIVE_MCP_NO_AUTH",
231108
+ "fields": {
231109
+ "auth_config_creation": {
231110
+ "required": [],
231111
+ "optional": []
231112
+ },
231113
+ "connected_account_initiation": {
231114
+ "required": [],
231115
+ "optional": []
231116
+ }
231117
+ }
231118
+ }
231119
+ ]
231120
+ },
231121
{
231122
"slug": "postalytics",
231123
"name": "Postalytics",
255867
}
255868
]
255869
},
255870
+ {
255871
+ "slug": "slidesgpt_mcp",
255872
+ "name": "SlidesGPT MCP",
255873
+ "logo": "https://logos.composio.dev/api/slidesgpt_mcp",
255874
+ "description": "Generate presentations and slide decks from a prompt and export them to PowerPoint.",
255875
+ "category": "ai content generation",
255876
+ "authSchemes": [
255877
+ "NO_AUTH"
255878
+ ],
255879
+ "toolCount": 2,
255880
+ "triggerCount": 0,
255881
+ "version": "20260730_01",
255882
+ "tools": [
255883
+ {
255884
+ "slug": "SLIDESGPT_MCP_APPLY_THEME",
255885
+ "name": "Apply theme",
255886
+ "description": "Apply a visual theme to re-style the entire presentation.\n\nWHEN TO USE:\n- User says \"apply Tokyo Dark theme\", \"change theme to Paris\", etc.\n- User wants to customize the presentation appearance\n\nAVAILABLE THEMES (18 total):\n• Urban: copenhagen, tokyo, paris, berlin, new-york, la, zurich, shanghai (each has -light and -dark variants)\n• Gradient: cosmic-pulse-light/dark\n\nREQUIRES: presentation_id from previous slide creation. This re-renders all slides with the new theme."
255887
+ },
255888
+ {
255889
+ "slug": "SLIDESGPT_MCP_CREATE_SLIDES",
255890
+ "name": "Create slides",
255891
+ "description": "Create one or more professional presentation slides. Pass a single slide in the array for one slide, or multiple slides for a full deck.\n\nUse when the user asks for slides, a presentation, or a deck. If the request is ambiguous about count, default to 2-3 slides.\n\nATTACHED PDFs / DOCUMENTS: Claude ingests user-attached files as document content blocks directly in the conversation. Read the document content from the conversation and pass the relevant material (topic, structure, key points) into this tool's slides argument — there is no separate file upload step.\n\nUSAGE NOTES:\n- Pass all slides for one request in a single call rather than multiple sequential calls.\n- To add to an existing presentation, pass the presentation_id from the previous response. For a new presentation, pass an empty string.\n- EDITING an existing slide: pass ONLY that slide, with its existing slidenum (from the previous response) and force_edit: true, plus the same presentation_id. This overwrites the slide in place. Do NOT resend the whole deck and do NOT omit force_edit, or a duplicate slide will be appended instead.\n\nIMAGES: Provide image_caption for every slide — describe the ideal slide image in 5-6 words (subject, setting, mood). Leave image_id empty; the system uses your caption to find the best matching photo.\n\nTHEMES: If the user asked for a specific theme, pass theme_id here rather than calling apply_theme separately afterwards.\n\nLAYOUT VARIETY (for multi-slide decks):\n- Use a variety of layouts across the deck, matching each layout to the slide's content.\n- Prefer \"title_and_two_columns\" (image layout) for the first content slide.\n- Use \"title_and_body\" for at most 1 slide (conclusion only), and avoid repeating the same layout on consecutive slides.\n- Use metric_rings only for percentage-based metrics (0-100).\n- Mix image slides, charts, timelines, grids, and text slides.\n\nLAYOUT OPTIONS (set layout for every slide):\n- \"title_and_two_columns\": Content with image alongside bullets (IMAGE LAYOUT)\n- \"title_and_two_to_four_columns_with_icons\": 2-4 key points with icons (good default)\n- \"title_and_body\": Single-column bullets (use sparingly — AT MOST 1 per deck, conclusion only)\n- \"title_and_subtitle\": Section divider or transition slide (title + subtitle only, minimal body)\n- \"image_full_width\": Full-width image with optional text below (IMAGE LAYOUT)\n- \"image_left_text_right\": Image on the left with bullet points on the right (IMAGE LAYOUT)\n- \"quadrant_grid\": EXACTLY 4 comparable items — SWOT, 2x2 matrices, pros/cons\n- \"data_table\": Structured comparisons in tabular format (key:value pairs in description)\n- \"timeline_horizontal\": Chronological events, milestones, or history (dates in point, short descriptions)\n- \"layered_pyramid\": Hierarchical structures with 3-6 levels (MUST include icon with fa- prefix per item)\n- \"phase_roadmap\": Project phases with milestones — point MUST use \"Period: Title\" format (e.g., \"Q1 2024: Launch\")\n- \"metric_rings\": KPIs, completion rates, market share (1-4 metrics, values 0-100 as percentages)\n\nCONTENT REQUIREMENTS:\n- 3-5 substantial bullet points per slide\n- Each bullet description: 2-4 lines with specific data, evidence, or actionable insights\n- Content should be PhD-level, detailed, and evidence-driven\n- Use FontAwesome 5.15 icons (e.g., fa-bolt, fa-chart-line, fa-lightbulb)\n- EVERY body item MUST include \"value\" (0-100) — enables chart rendering and layout switching\n\nLAYOUT-SPECIFIC FORMATTING:\n- quadrant_grid: EXACTLY 4 items. \"point\" under 15 chars, \"description\" under 80 chars\n- timeline_horizontal: Dates/years in \"point\" (max 15 chars). \"description\" max 50 chars\n- layered_pyramid: \"icon\" with fa- prefix REQUIRED (fa-star, fa-check, fa-rocket). 3-6 items\n- phase_roadmap: \"point\" = \"Period: Title\" (e.g., \"Q1 2024: Launch\"). Max 4 phases. \"description\" = milestones separated by \"; \"\n- metric_rings: 1-4 items. For part-of-whole metrics (market share), values sum to ~100. For standalone KPIs (NPS, satisfaction), each value stands alone\n- data_table: \"description\" should use structured key:value pairs\n\nSCHEMA: Use only the documented schema fields — do not invent custom properties like \"left_content\", \"right_content\", \"table\", \"rows\", or \"headers\". For tables, use the data_table layout with key:value pairs in body[].description."
255892
+ }
255893
+ ],
255894
+ "triggers": [],
255895
+ "authConfigDetails": [
255896
+ {
255897
+ "mode": "NO_AUTH",
255898
+ "name": "SLIDESGPT_MCP_NO_AUTH",
255899
+ "fields": {
255900
+ "auth_config_creation": {
255901
+ "required": [],
255902
+ "optional": []
255903
+ },
255904
+ "connected_account_initiation": {
255905
+ "required": [],
255906
+ "optional": []
255907
+ }
255908
+ }
255909
+ }
255910
+ ]
255911
+ },
255912
{
255913
"slug": "slite",
255914
"name": "Slite",
264160
}
264161
]
264162
},
264163
+ {
264164
+ "slug": "taskrabbit_mcp",
264165
+ "name": "Taskrabbit MCP",
264166
+ "logo": "https://logos.composio.dev/api/taskrabbit_mcp",
264167
+ "description": "Find and book local Taskrabbit services for home repair, moving, cleaning, and handyman tasks.",
264168
+ "category": "scheduling & booking",
264169
+ "authSchemes": [
264170
+ "NO_AUTH"
264171
+ ],
264172
+ "toolCount": 3,
264173
+ "triggerCount": 0,
264174
+ "version": "20260730_01",
264175
+ "tools": [
264176
+ {
264177
+ "slug": "TASKRABBIT_MCP_CHECK_SERVICE_AVAILABILITY",
264178
+ "name": "Check service availability",
264179
+ "description": "Check availability, pricing, and scoping questions for a service in a location. Provide either city + state OR postalCode to specify the location. When the response includes topTaskers, render each tasker as a visual card (not a plain list or table) with a circular avatar showing their initials, name, rating, review count, and description."
264180
+ },
264181
+ {
264182
+ "slug": "TASKRABBIT_MCP_GENERATE_DEEP_LINK",
264183
+ "name": "Generate deep link",
264184
+ "description": "Generate a pre-filled Taskrabbit booking deep link using task template ID."
264185
+ },
264186
+ {
264187
+ "slug": "TASKRABBIT_MCP_LIST_SUPPORTED_SERVICES",
264188
+ "name": "List supported services",
264189
+ "description": "List Taskrabbit services available in a location. Provide either city + state OR postalCode."
264190
+ }
264191
+ ],
264192
+ "triggers": [],
264193
+ "authConfigDetails": [
264194
+ {
264195
+ "mode": "NO_AUTH",
264196
+ "name": "TASKRABBIT_MCP_NO_AUTH",
264197
+ "fields": {
264198
+ "auth_config_creation": {
264199
+ "required": [],
264200
+ "optional": []
264201
+ },
264202
+ "connected_account_initiation": {
264203
+ "required": [],
264204
+ "optional": []
264205
+ }
264206
+ }
264207
+ }
264208
+ ]
264209
+ },
264210
{
264211
"slug": "tave",
264212
"name": "Tave",
266912
"authSchemes": [
266913
"OAUTH2"
266914
],
266010
- "toolCount": 10,
266915
+ "toolCount": 9,
266916
"triggerCount": 0,
266012
- "version": "20260721_00",
266917
+ "version": "20260730_00",
266918
"tools": [
266919
{
266920
"slug": "TIKTOK_FETCH_PUBLISH_STATUS",
266921
"name": "Fetch publish status",
266922
"description": "Check the processing status of a TikTok video or photo post using its publish_id. Use this action to poll the status of content after initiating an upload or post. The API returns detailed information about processing stages (upload, download, moderation) and any errors that occurred. Non-terminal statuses mean processing is still pending — never re-initiate TIKTOK_PUBLISH_VIDEO for the same publish_id. Use exponential backoff when polling (e.g., 5s→10s→20s) to avoid the 30 requests/minute per access token rate limit."
266923
},
266019
- {
266020
- "slug": "TIKTOK_GET_ACTION_CATEGORIES",
266021
- "name": "Get action categories",
266022
- "description": "Tool to retrieve available action categories from TikTok Marketing API. Use when you need to get the list of conversion event categories for creating or managing TikTok ad campaigns with conversion tracking."
266023
- },
266024
- {
266025
- "slug": "TIKTOK_GET_TERM",
266026
- "name": "Get terms",
266027
- "description": "Tool to retrieve terms from TikTok Business API. Use when you need to fetch advertiser or agency terms for a specific advertiser ID."
266028
- },
266924
{
266925
"slug": "TIKTOK_GET_USER_STATS",
266926
"name": "Get user stats",
266927
"description": "Fetches TikTok user information and statistics for the authenticated user. Retrieves user stats (follower_count, following_count, likes_count, video_count) and can optionally fetch profile fields (display_name, username, bio_description, etc.) and basic info (open_id, union_id, avatar URLs). Returns only the fields requested in the fields parameter. Only works for the authenticated account; cannot fetch arbitrary public profiles. Stats may be delayed and not reflect the most recent activity."
266928
},
266034
- {
266035
- "slug": "TIKTOK_LIST_GMV_MAX_OCCUPIED_CUSTOM_SHOP_ADS",
266036
- "name": "List GMV Max occupied custom shop ads",
266037
- "description": "Tool to get GMV Max occupied custom shop ads list for a TikTok advertiser. Use this action when you need to retrieve information about which custom shop ads are currently occupied for GMV Max campaigns. This is part of the TikTok Business API and requires appropriate advertiser access."
266038
- },
266929
{
266930
"slug": "TIKTOK_LIST_VIDEOS",
266931
"name": "List videos",
266042
- "description": "Lists videos for the authenticated user (or specified creator). Does not provide a global TikTok-wide feed."
266932
+ "description": "Lists the authenticated user's own **public** TikTok videos, newest first. Only public posts are returned — private/`SELF_ONLY`, friends-only, and draft videos never appear (this is a property of the underlying `video.list` scope, not a bug), so on an account with no public posts the list is empty. Cannot list an arbitrary creator's videos, and does not provide a global TikTok-wide feed. Returns a single page (up to `max_count`, capped at 20). It does NOT auto-loop: when `has_more` is true, call again passing the returned `cursor` to fetch the next page. Accounts with more than `max_count` public videos are otherwise silently truncated."
266933
},
266934
{
266935
"slug": "TIKTOK_POST_PHOTO",
266941
"name": "Publish video",
266942
"description": "Publishes a video to TikTok by pulling it from a public URL. TikTok downloads the video from the provided URL and publishes it directly to the creator's profile. Publishing is asynchronous — after calling this action, poll TIKTOK_FETCH_PUBLISH_STATUS with the returned publish_id to check completion. For uploading video files instead of URLs, use TIKTOK_UPLOAD_VIDEO."
266943
},
266944
+ {
266945
+ "slug": "TIKTOK_QUERY_CREATOR_INFO",
266946
+ "name": "Query creator info",
266947
+ "description": "Queries the authenticated creator's info and current posting options. Returns the account's available `privacy_level_options` and interaction settings (comment/duet/stitch), which the Content Posting API requires you to read before a direct post — the valid `privacy_level` values for an account are only discoverable here. Call this to pick a real privacy level instead of guessing (unaudited apps only ever get SELF_ONLY)."
266948
+ },
266949
+ {
266950
+ "slug": "TIKTOK_QUERY_VIDEOS",
266951
+ "name": "Query videos",
266952
+ "description": "Fetches metadata for specific TikTok videos by ID (1-20 per request). Verifies the videos belong to the authenticated user and returns their details, refreshing the cover-image URL's expiration. Unlike List videos, this looks up known video IDs rather than walking recent uploads."
266953
+ },
266954
{
266955
"slug": "TIKTOK_UPLOAD_VIDEO",
266956
"name": "Upload video",
266057
- "description": "Uploads a video to TikTok via the Content Posting API (init + single-part upload). This action initializes an upload session to obtain a presigned upload URL, then uploads the entire file with a single PUT request. Use a subsequent action to publish the post. Ensure the video file is fully generated and available before calling this action."
266957
+ "description": "Uploads a video to TikTok via the Content Posting API. This action initializes an upload session to obtain a presigned upload URL, then uploads the file in one or more sequential PUT requests with TikTok-compatible ranges. Use a subsequent action to publish the post. Ensure the video file is fully generated and available before calling this action."
266958
},
266959
{
266960
"slug": "TIKTOK_UPLOAD_VIDEOS",
266961
"name": "Upload videos (batch)",
266062
- "description": "Uploads multiple videos to TikTok concurrently (init + single-part upload per file)."
266962
+ "description": "Uploads multiple videos to TikTok concurrently."
266963
}
266964
],
266965
"triggers": [],
268544
}
268545
]
268546
},
268547
+ {
268548
+ "slug": "trivago_mcp",
268549
+ "name": "Trivago MCP",
268550
+ "logo": "https://logos.composio.dev/api/trivago_mcp",
268551
+ "description": "Compare hotel prices across booking sites and find accommodation deals with Trivago.",
268552
+ "category": "scheduling & booking",
268553
+ "authSchemes": [
268554
+ "NO_AUTH"
268555
+ ],
268556
+ "toolCount": 2,
268557
+ "triggerCount": 0,
268558
+ "version": "20260730_01",
268559
+ "tools": [
268560
+ {
268561
+ "slug": "TRIVAGO_MCP_TRIVAGO_ACCOMMODATION_RADIUS_SEARCH",
268562
+ "name": "Trivago-accommodation-radius-search",
268563
+ "description": "Search for accommodations and hotels using coordinates on trivago.\n\nUse this tool when you want to find accommodations near a specific location (landmark, neighborhood, or address).\n\nAdditional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-07-30\"}}"
268564
+ },
268565
+ {
268566
+ "slug": "TRIVAGO_MCP_TRIVAGO_ACCOMMODATION_SEARCH",
268567
+ "name": "Trivago-accommodation-search",
268568
+ "description": "Search for accommodations and hotels by destination or point of interest on trivago. Additional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-07-30\"}}"
268569
+ }
268570
+ ],
268571
+ "triggers": [],
268572
+ "authConfigDetails": [
268573
+ {
268574
+ "mode": "NO_AUTH",
268575
+ "name": "TRIVAGO_MCP_NO_AUTH",
268576
+ "fields": {
268577
+ "auth_config_creation": {
268578
+ "required": [],
268579
+ "optional": []
268580
+ },
268581
+ "connected_account_initiation": {
268582
+ "required": [],
268583
+ "optional": []
268584
+ }
268585
+ }
268586
+ }
268587
+ ]
268588
+ },
268589
{
268590
"slug": "truvera",
268591
"name": "Truvera",
273307
}
273308
]
273309
},
273310
+ {
273311
+ "slug": "viator_mcp",
273312
+ "name": "Viator MCP",
273313
+ "logo": "https://logos.composio.dev/api/viator_mcp",
273314
+ "description": "Search and book tours, activities, and travel experiences around the world with Viator.",
273315
+ "category": "scheduling & booking",
273316
+ "authSchemes": [
273317
+ "NO_AUTH"
273318
+ ],
273319
+ "toolCount": 2,
273320
+ "triggerCount": 0,
273321
+ "version": "20260730_01",
273322
+ "tools": [
273323
+ {
273324
+ "slug": "VIATOR_MCP_GET_EXPERIENCE_DETAILS",
273325
+ "name": "Get experience details",
273326
+ "description": "Retrieves enriched information for a specific Viator experience, including detailed descriptions, highlights, imagery, pricing, duration, key features, and the click-out URL.The model should call this tool only when the user clearly refers to a specific experience—either by selecting it in the UI or by asking follow-up questions such as “Tell me more about…”;if multiple experiences were shown, the model must resolve ambiguity by asking which one the user means. This tool is intended for deepening experience understanding rather than search, and should only be invoked with a code previously returned by search_experiences."
273327
+ },
273328
+ {
273329
+ "slug": "VIATOR_MCP_SEARCH_EXPERIENCES",
273330
+ "name": "Search experiences",
273331
+ "description": "Retrieves a curated list of Viator experiences based on a free-text search of what the user wants (destination, activity type, and preferences), plus trip dates and optional refiners (budget, duration, etc.).\nThe model must supply a non-blank searchTerm as natural language describing where and what the user is looking for (e.g. \"walking tours in Paris, France\", \"kid friendly food experiences in Rome\"). Dates, prices, duration limits, and currency belong in their dedicated parameters—not inside searchTerm.\nThe model must provide searchTerm and dates before calling this tool. The model may re-issue a refined searchExperiences call whenever the user adds, removes, or adjusts refinement criteria (e.g., kid-friendly, price range, shorter duration) to narrow or improve the results.\nIf the tool returns zero results, the model must proactively guide the user toward a successful refinement. It should review the parameters used in the failed request and recommend the most appropriate based on the proposed logic:\"\nIf > 1 categories applied, suggest removing some categories. Eg: “It looks like those categories combined are too restrictive. Would you like to narrow it down?”\nIf the query requests a specific feature (eg private tour), suggest removing this constraint. Eg: “Private tours may be limited in this area, would you like to consider group options too?”\nIf duration (avg from/to) > XX, suggest trying a shorter duration.\nIf duration (avg from/to) < XX, suggest trying a longer duration.\nIf price constraint was applied, suggest widening (or removing) price limits.\nElse, suggest broaden location search. Eg: “Nothing matches in central Siena, should we try Tuscany or nearby towns?”"
273332
+ }
273333
+ ],
273334
+ "triggers": [],
273335
+ "authConfigDetails": [
273336
+ {
273337
+ "mode": "NO_AUTH",
273338
+ "name": "VIATOR_MCP_NO_AUTH",
273339
+ "fields": {
273340
+ "auth_config_creation": {
273341
+ "required": [],
273342
+ "optional": []
273343
+ },
273344
+ "connected_account_initiation": {
273345
+ "required": [],
273346
+ "optional": []
273347
+ }
273348
+ }
273349
+ }
273350
+ ]
273351
+ },
273352
{
273353
"slug": "virustotal",
273354
"name": "Virustotal",
274701
],
274702
"toolCount": 144,
274703
"triggerCount": 0,
273720
- "version": "20260721_00",
274704
+ "version": "20260729_00",
274705
"tools": [
274706
{
274707
"slug": "WIX_ADD_SPECIAL_PERMISSIONS",
276197
],
276198
"toolCount": 553,
276199
"triggerCount": 13,
275216
- "version": "20260724_00",
276200
+ "version": "20260729_00",
276201
"tools": [
276202
{
276203
"slug": "WORKDAY_APPROVE_BUSINESS_PROCESS_EVENT_STEP",
280313
}
280314
]
280315
},
280316
+ {
280317
+ "slug": "ziprecruiter_mcp",
280318
+ "name": "ZipRecruiter MCP",
280319
+ "logo": "https://logos.composio.dev/api/ziprecruiter_mcp",
280320
+ "description": "Search job listings across ZipRecruiter's marketplace by role, location, and salary.",
280321
+ "category": "hr talent & recruitment",
280322
+ "authSchemes": [
280323
+ "NO_AUTH"
280324
+ ],
280325
+ "toolCount": 1,
280326
+ "triggerCount": 0,
280327
+ "version": "20260730_01",
280328
+ "tools": [
280329
+ {
280330
+ "slug": "ZIPRECRUITER_MCP_SEARCH_JOBS",
280331
+ "name": "Search jobs",
280332
+ "description": "Use this tool whenever the user asks to find, browse, view, recommend, or search for jobs, roles, openings, gigs, internships, or job listings. It only shows jobs that are within the United States or Canada.\nGuidelines:\n- Do not provide fields unless the user explicitly provides them.\n- The tool provides the search results all in one list, so if the user intends to search for multiple job roles, it may be better to invoke the tool for each job role separately.\n- If the user has not provided a location and is not asking for remote jobs, ask the user for a location before calling this tool. If you call without a location, results will default to a United States-wide search and the user will be warned.\n\nNotes:\n- When provided radius_miles, jobs will be included in the result if their location's boundaries approximately fall within radius miles of the requested location's boundaries.\n- If a salary range is provided, a job will be included in the results if the job's salary range overlaps with the requested salary range.\n"
280333
+ }
280334
+ ],
280335
+ "triggers": [],
280336
+ "authConfigDetails": [
280337
+ {
280338
+ "mode": "NO_AUTH",
280339
+ "name": "ZIPRECRUITER_MCP_NO_AUTH",
280340
+ "fields": {
280341
+ "auth_config_creation": {
280342
+ "required": [],
280343
+ "optional": []
280344
+ },
280345
+ "connected_account_initiation": {
280346
+ "required": [],
280347
+ "optional": []
280348
+ }
280349
+ }
280350
+ }
280351
+ ]
280352
+ },
280353
{
280354
"slug": "zixflow",
280355
"name": "Zixflow",