DEV-124 Adding overview page for frameworks and MCP clients

[nearestnabors]

Preview: https://docs-git-framework-overview-arcade-ai.vercel.app/en/home/agent-frameworks-overview

A simple overview of the supported Agentic Frameworks and MCP Clients in our docs base. If this meets with approval, I'll clean up the icons so they look nicer on the background and try to reuse the same component from the MCP Servers page

---

Note

Adds a new frameworks/MCP overview with platform cards, introduces PagerDuty MCP server docs with examples, and updates PagerDuty auth guidance (Classic, provider id pagerduty).

• Docs:
  • Agent Frameworks/MCP Overview: New page app/en/home/agent-frameworks-overview/page.mdx with tabs and PlatformCard links for LangChain, CrewAI, OpenAI Agents, Google ADK, Mastra, Vercel AI, and MCP clients (Claude Desktop, Cursor, VS Code).
  • PagerDuty MCP Server: New docs at app/en/mcp-servers/customer-support/pagerduty/page.mdx describing available tools and usage; menu entry added in app/en/mcp-servers/customer-support/_meta.tsx.
  • PagerDuty Auth Provider: Revised to Classic OAuth, provider id pagerduty, empty scopes in samples, updated link targets, and new PagerDuty() auth class usage in custom tools (app/en/home/auth-providers/pagerduty/page.mdx).
• UI Component:
  • PlatformCard: New component app/_components/platform-card.tsx used by the overview page.
• Examples:
  • Added JS/Python example scripts under public/examples/integrations/mcp-servers/pagerduty/* for each PagerDuty tool (authorize + execute).

^{Written by Cursor Bugbot for commit a32aae7. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Dec 19, 2025 1:29am

[vfanelle]

This page is so needed. Mateo and I envisioned this page would collect both your agent framework and language of choice (python, typescript/javascript), and then route you to the agent framework with your preferred language's code snippets selected. To that end, the agent framework buttons are top notch. We need some way to collect your preferred language for the multi-language frameworks (LangGraph, OpenAI Agents, Google ADK, Crew AI). Can you add that?

We also planned to move MCP Clients from this page/section, and instead place them inside the set of documents for tool calling in 3rd party agents (e.g. gateway). Can we remove MCP Clients from this page?

[nearestnabors]

@vfanelle Cool idea! I need some more clarity on how this is expected to work/what the outcomes look like. It might be easier to chat, so I've put time on your calendar! Could you share any links to pages that exhibit the behavior you're thinking of?

[nearestnabors]

Because currently the Python and JS content live on a single page filtering isn't really possible with the content we have. So I updated it to have little tags that indicate which languages are supported!

[nearestnabors]

I had to

• leave out the tabs (we currently have combined pages, not individual pages for each laungage), so I added little tags to them.
• leave the MCP Clients because they will be migrated to a new section later. I made an issue to remind us about that 🙂

This page now exists, though! We can mod it further as we move along.

[vfanelle]

Because currently the Python and JS content live on a single page filtering isn't really possible with the content we have. So I updated it to have little tags that indicate which languages are supported!

Uploading Screenshot 2025-12-18 at 6.38.13 PM.png…

Adding @sdserranog as a reviewer, who can share how we can use language buttons to set the preferredLanguage when landing on each agent framework page

[sdserranog]

A bit of context on how we handle language selection in the docs.

The preferred language is already stored in localStorage under the key preferredLanguage, with the following values:

0 → Python

1 → JavaScript

Because of this, any page can filter or conditionally render content by checking:

localStorage.getItem("preferredLanguage")

Given that, we don’t need to introduce tabs specifically for language switching. Any UI control (toggle, dropdown, button, etc.) that updates this key should work across the docs.

// Set preferred language to Python
localStorage.setItem("preferredLanguage", "0");

[vfanelle]

Agreed we don’t need to introduce tabs specifically for language switching if the language is set on other pages.

Devs who already have an agent framework in mind will come straight to this page to integrate Arcade with their framework. Alternatively, if a user completes the tool calling quickstart, they'd come to this page to learn about and pick an agent framework. Their language is one part of that decision.

So, I think this page is one of the first places where a user will set their language. Which is why it'd be nice to build a tab like this to hold the agent framework blocks:

I think I'm hearing from Sergio that we can set preferredLanguage via tabs like those, such that when a user lands on an agent framework page, their preferred language is selected in the code snippets.

[sdserranog]

We can use those same Tabs if you'd like, as they already have the logic to set the preferred language.

<Tabs items={["Python", "JavaScript"]} storageKey="preferredLanguage">
  <Tabs.Tab>
    Frameworks for Python
  </Tabs.Tab>
  <Tabs.Tab>
    Frameworks for JavaScript
  </Tabs.Tab>
</Tabs>

[nearestnabors]

I do know how to use the tabs code and have used it before! That's not my concern..

The problem we do not have separate pages for Python and JavaScript code. Both approaches live on single Pages. We have to split those out into separate pages ala the new IA, and we haven't done that yet. If I were to implement these tabs, what pages would they link to?

Or are you suggesting we use the tabs even if they are linking to the same pages? Kinda seems to remove the need for filtering...

[nearestnabors]

Added the tabs. Please approve!