Skip to content

Commit 5d971e6

Browse files
committed
Merge main into docs/warp-tunnels: resolve llms.txt conflict
1 parent bce8c42 commit 5d971e6

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

public/llms.txt

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- git-sha: e6a07f547b94a742ec2d2b95daf8cdb6ba2a80a6 generation-date: 2026-06-25T19:20:07.652Z -->
1+
<!-- git-sha: e6a07f547b94a742ec2d2b95daf8cdb6ba2a80a6 generation-date: 2026-06-25T19:20:07.622Z -->
22

33
# Arcade
44

@@ -25,6 +25,7 @@ Arcade delivers three core capabilities: Deploy agents even your security team w
2525
- [Auth Providers](https://docs.arcade.dev/en/references/auth-providers): This documentation page provides a comprehensive registry of authentication providers available within the Arcade ecosystem, enabling users to securely connect Arcade tools to various data sources. It outlines the benefits of using Arcade's built-in auth providers versus configuring custom ones, including branding and rate limit
2626
- [Calendly](https://docs.arcade.dev/en/references/auth-providers/calendly): This documentation page provides guidance on configuring the Calendly authentication provider for use with Arcade, allowing users to integrate Calendly APIs into their applications using OAuth 2.0. It outlines the steps for creating a Calendly developer account, registering an OAuth application
2727
- [Changelog](https://docs.arcade.dev/en/references/changelog): The Changelog documentation page provides users with a comprehensive overview of the latest updates, features, bug fixes, and improvements made to Arcade.dev, organized by date. It helps users stay informed about new functionalities and changes that enhance their development experience and platform usability
28+
- [Cisco Duo](https://docs.arcade.dev/en/references/auth-providers/cisco-duo): Documentation page
2829
- [ClickUp](https://docs.arcade.dev/en/references/auth-providers/clickup): This documentation page provides guidance on configuring and using the ClickUp authentication provider within the Arcade platform, enabling users to call the ClickUp API on behalf of their users. It outlines the steps for creating a ClickUp app, setting up OAuth credentials, and
2930
- [Context](https://docs.arcade.dev/en/references/mcp/python/context): This documentation page provides a comprehensive reference for the `Context` class used in MCP tools, detailing its role as the primary interface for interacting with the server, client, and runtime environment. Users will learn how to utilize the automatically managed `Context` instances
3031
- [Discord](https://docs.arcade.dev/en/references/auth-providers/discord): This documentation page provides guidance on how to configure and use a custom Discord authentication provider within the Arcade platform, as Arcade does not offer a default option. Users will learn how to create a Discord application, set up OAuth 2.0 credentials, and

0 commit comments

Comments
 (0)