docs: promote remote MCP servers to a first-class capability - #1139
Merged
Conversation
Registering an MCP server that Arcade does not host was documented only at operate/governance/mcp-gateways/add-remote-servers — five levels deep, framed as a gateway setting. No entry-point page mentioned it, and the glossary said the feature was still unreleased. Move the page to operate/governance/remote-mcp-servers (sibling of MCP Gateways, with redirects) and add a "Types of MCP servers in Arcade" section covering the two axes the dashboard exposes but the docs never explained: Arcade Native/HTTP vs remote/MCP, and Project vs Global scope. Promote the capability on the landing page, About Arcade's Execute pillar, the MCP Servers catalog, and the Operate/Governance hubs, quickstart, and FAQ. Also: correct the glossary's "in the future" claim, disambiguate building a new MCP server from registering an existing one, document the Server Type selection the canonical page omitted, give Tavily and Nimble sidebar entries under a new Partners separator, normalize the dashboard URLs and "Add Server" labels, and wire up the orphaned advanced-settings screenshot. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The page had moved out from under MCP Gateways but its content was still gateway-first: "Why use MCP Gateways for remote MCP servers" sat above the registration steps, and both the Outcomes and You Will Learn lists named gateways as the destination. That misstates the model — you register a server once to a project (or globally to the org), and from then on every gateway, Playground session, and SDK call in that scope can use its tools. Lead with that. Drop the gateway-first section, add "Where the server's tools become available" stating the one-registration-many-gateways relationship explicitly, and note on the scope table that scope is set on the server rather than on any gateway. Tavily and Nimble said "add it to an MCP Gateway", which was simply the wrong operation; they now say register it to the project. Also promote the per-user auth behavior out of a run-on paragraph buried in setup step 3 into its own section. The admin's credentials determine the tool list Arcade discovers and curates from, while each end user authenticates separately at runtime and gets their own narrower effective set — so a tool present in a gateway is not a guarantee that a given user can call it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…tion The "Types of MCP servers in Arcade" section described the Project/Global and Arcade Native/remote axes in tables. The dashboard shows the whole point in one frame: Arcade-hosted and remote servers sitting as peer rows in a single list, with Arcade's own catalog as the Global group below. Adds a short caption walking the reader through which row is which, so the image carries the argument rather than just decorating it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replaces the single light-mode capture with a light/dark pair rendered via the repo's dual-theme pattern, so the taxonomy section's screenshot matches the reader's theme. The two source captures differed in size (2800x1858 and 2808x1848) and in vertical content offset. Both were cropped to their content box and padded onto a common 2799x1837 canvas, so the pair is dimensionally identical with nothing clipped and no layout shift when switching themes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
evantahler
commented
Aug 24, 2026
Registration scope is a project or an organization, not only a project. Trims the redundant "you do not add a remote server to a gateway" sentence, now that the surrounding paragraph already makes the point, and takes two wording fixes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Applying the "project or organization" correction to line 21 left the rest of the docs contradicting it: the paragraph right after still treated global registration as an afterthought, and five other places said a server is scoped to a project full stop. Reframe scope as one choice made when you register — a single project, or the whole organization — with everything downstream following from it. The scope table now leads with "How far it reaches, chosen when you register it," the "where tools become available" bullets are scope-relative rather than project-relative, and the glossary, MCP Gateways hub, integrations catalog, Tavily, and Nimble all match. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
teallarson
reviewed
Aug 24, 2026
teallarson
reviewed
Aug 24, 2026
…ervers Review caught that api.arcade.dev/dashboard/* is stale — the dashboard lives at app.arcade.dev with no /dashboard prefix, which is what DashboardLink already resolves to. An earlier commit here normalized toward the stale host because it was the more common form in the repo; that was the wrong direction. Fixes every occurrence in the files this PR touches, including two the review didn't flag (the on-prem Playground link and the Cisco Duo dashboard link). Also adds a callout steering readers to the pre-built catalog first, so the page doesn't read as recommending a vendor's remote server for a service Arcade already ships an agent-optimized one for. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registering an MCP server that Arcade does not host was documented only at
operate/governance/mcp-gateways/add-remote-servers— five levels deep, framed as a gateway setting, unmentioned by the landing page, About Arcade, the MCP Servers catalog, the Operate/Governance hubs, the quickstart, or the FAQ, and contradicted by a glossary line claiming the feature was still unreleased.The framing fix is the substance here. A remote server is registered once, to a project (or globally to the org) — not to a gateway — and from then on every gateway, Playground session, and SDK call in that scope can use its tools. The old page inverted that: "Why use MCP Gateways for remote MCP servers" sat above the registration steps, and Tavily and Nimble both told you to "add it to an MCP Gateway," which is the wrong operation. The page now leads with project scope, a new Where the server's tools become available section states the one-registration-many-gateways relationship, and the scope table notes that scope is set on the server rather than on any gateway.
It also moves to
operate/governance/remote-mcp-servers(sibling of MCP Gateways; redirects for both old paths, and the legacy/guides/one repointed to avoid a chain), and adds a Types of MCP servers in Arcade section covering the two axes the dashboard exposes but the docs never explained: Arcade Native/HTTPvs remote/MCP, andProjectvsGlobal. Two behaviors that were buried or missing are now their own sections: Who authenticates, and when — the admin's credentials determine the tool list Arcade discovers and curates from, while each end user authenticates separately at runtime and gets their own narrower effective set, so a tool present in a gateway is not a guarantee a given user can call it — and the Server Type → Remote MCP step the page omitted entirely.Promotion surfaces: a "Bring your own MCP server" card on the landing page beside the pre-built-integrations one, About Arcade's Execute pillar, a "Don't see the server you need?" section on the catalog, plus the Operate/Governance hubs, operator quickstart, and FAQ. Cleanup: the glossary's stale "in the future" claim plus new Remote/Project/Global entries, build-vs-register callouts, sidebar entries for Tavily and Nimble (previously reachable only via catalog cards) under a new Partners separator, normalized dashboard URLs and "Add Server" labels across five pages, and the orphaned
remote-mcp-server-advanced-settings.pngwired into the section it documents.Verified:
pnpm test(847 passing),pnpm lint,pnpm check-meta,pnpm check-redirects,pnpm build, plus a manual dev-server walkthrough confirming all routes resolve, both old paths 308 without chaining, and the new nav/cards/screenshots/anchors render. One gap —pnpm vale:checkcannot run in this checkout: Vale's MDX parsermdx2vastis required and its GitHub repo returns "Repository not found," so it fails on unmodified files too. Worth a separate look.🤖 Generated with Claude Code
Note
Low Risk
Documentation, redirects, and marketing copy only; no application runtime or security logic changes.
Overview
Remote MCP servers are documented as a governance capability at
/operate/governance/remote-mcp-servers, not as an MCP Gateway sub-page. The oldadd-remote-serversguide is removed; permanent redirects cover the legacy/guides/andmcp-gateways/URLs (including Salesforce).The new guide reframes registration as once per project or org scope, with tools available to every gateway, Playground, and SDK in that scope. It adds Types of MCP servers (Arcade Native vs remote; Project vs Global), Who authenticates, and when (admin at setup vs end user at runtime), the Remote MCP server-type step, dashboard screenshots, and cross-links from build vs register flows.
Discovery updates: Governance/Operate hubs, landing Bring your own MCP server card, About Arcade Execute pillar, integrations Don't see the server you need?, operator quickstart, FAQ, and glossary (replacing the stale “in the future” note). MCP Gateways page now points to remote servers for federating external tools. Nimble/Tavily partner pages and nav get corrected links and a Partners sidebar section; several pages normalize dashboard URLs to
app.arcade.devand Add Server wording.public/llms.txtis regenerated.Reviewed by Cursor Bugbot for commit a680edf. Bugbot is set up for automated code reviews on this repo. Configure here.