Skip to content

[AUTO] Adding MCP Servers docs update - #1191

Open
github-actions[bot] wants to merge 6 commits into
teallarson/simplify-ci-env-varsfrom
automation/toolkit-docs
Open

github-actions[bot] wants to merge 6 commits into
teallarson/simplify-ci-env-varsfrom
automation/toolkit-docs

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

This PR was generated after a Porter deploy succeeded.


Note

Medium Risk
CI credential and workflow coupling changes affect all automated docs PRs; removing i18n and translation tooling is a broad product/UX shift, though OAuth guidance changes are documentation-only.

Overview
This PR reshapes docs automation, drops translated locales, and expands MCP/OAuth guidance, plus a regenerated public/llms.txt.

CI and automation: Docs Bot’s composite app-token action and DOCS_BOT_* secrets are removed. Toolkit docs, llmstxt, and design-system update workflows now open PRs and push with GITHUB_TOKEN (as github-actions[bot] where needed). generate-toolkit-docs runs pnpm llmstxt in the same job so automation PRs stay self-contained—GITHUB_TOKEN PRs do not chain-trigger llmstxt.yml. The workflow adds a manual public_catalog_url input, pins Anthropic models in the generate step, and documents OPENAI_API_KEY. translate-docs.yml, context7.yml, and context7.json are deleted; tests/docs-automation-tokens.test.ts guards against regressing to the app token.

English-only docs: es / pt-BR dictionaries, the translation banner, scripts/i18n-sync, and the translate npm script go away; i18n.locales is ["en"] only. Layout and 404 UI stop loading locale-specific copy (legacy /es / /pt-BR URLs still redirect to /en via proxy.ts).

Content: New Connect the AWS MCP Server guide and nav entry; Claude custom-connector docs emphasize Detected defaults (Sign in now, Use Claude’s published identity / CIMD) across Claude Desktop, gateway creation, and consent allowlisting. Salesforce auth docs expand required custom scopes and auth.start() examples. README points at .env.local.example.

Generated output: public/llms.txt refresh (including AWS page and refreshed integration blurbs from the toolkit pipeline).

Reviewed by Cursor Bugbot for commit b8b6f88. Bugbot is set up for automated code reviews on this repo. Configure here.

@vercel

vercel Bot commented Sep 14, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
docs Ready Ready Preview Sep 14, 2026 5:25pm UTC

Request Review

teallarson and others added 2 commits September 14, 2026 20:38
* docs: add AWS MCP Server remote connection guide

Mirrors the other remote MCP server guides. AWS's setup is DCR-based
like Atlassian: no manual OAuth app, Client ID/Secret, Authorization
URL, and Token URL all stay empty in Arcade. Access is governed
entirely by IAM: authorizing an agent grants no additional AWS
permissions, every tool call runs under the authorizing identity's
existing IAM policies, and the guide leads with this since it's the
whole security model. No Arcade AWS toolkit exists today, so this is
framed as a fixed-surface, currently-only-path guide (same tier as
Dynamics 365 and Atlassian), not a customer-extensible one.

Does not document the non-interactive SigV4/client-credentials path
(single shared machine identity, doesn't fit Arcade's per-user OAuth
model) by design.

BLOCKED ON AWS: Arcade's redirect URI is not yet on AWS Sign-In's DCR
allowlist as of this commit (verified against AWS's live docs). This
PR is opened as a draft until AWS completes that change; see PR
description for the verification method and result.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* 🤖 Regenerate LLMs.txt

* docs: drop the DCR-allowlist setup step from the AWS guide

This step only made sense while Arcade wasn't yet on AWS Sign-In's
DCR allowlist. Once that gate clears, there's nothing for a reader to
confirm here, so it becomes dead weight in Set up AWS. The
troubleshooting entry for the same failure mode stays, since that's a
standard "if you see this error, here's why" reference regardless of
when it occurs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* docs: correct the AWS MCP Server region example and DCR troubleshooting

The guide used us-west-2 as its worked example, inherited from AWS's own
CloudTrail samples, but that endpoint does not resolve. Only us-east-1 and
eu-central-1 are served today, so a reader following the example verbatim
got a DNS failure rather than anything the guide accounted for. Point the
example at a region that resolves and name the unserved-region failure mode.

AWS's published Supported Redirect URIs table also lags their actual DCR
allowlist: Arcade is approved and working, but absent from that table. The
troubleshooting entry told readers to verify against it, which now fails for
someone whose setup is correct.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* docs: stop pointing readers at AWS's redirect URI table

AWS's published table lags their actual DCR allowlist, so sending a reader
there to verify Arcade's redirect URI gives a misleading answer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* docs: drop semicolon in AWS DCR troubleshooting entry

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* 🤖 Regenerate LLMs.txt

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: arcade-docs-bot[bot] <321924871+arcade-docs-bot[bot]@users.noreply.github.com>
* docs: document all 11 Salesforce MCP custom OAuth scopes

The toolkit requests four write/read scopes that were missing from the auth provider page, and the samples told people to pass only read_account.

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: mark Salesforce org subdomain as a placeholder in auth endpoints

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: keep Salesforce subdomain placeholders visible in MDX

Angle brackets were parsed as HTML tags, so the preview dropped them from the auth endpoint URLs.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Valerie Fanelle <valeriefanelle@mac.local.meter>
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: tell admins to keep Claude's detected connector defaults

Claude's Add custom connector dialog now shows Authentication and OAuth client options. The Detected values already match Arcade Auth, so operators should leave them selected.

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: replace Claude connector screenshot and capitalize Authenticate

Use the full Add custom connector dialog (api.arcade.dev, request headers visible) and sentence-case the auth step heading.

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: crop leftover chrome from the Claude connector screenshot

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: rename Claude connector screenshot to bust the image cache

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Valerie Fanelle <valeriefanelle@Valeries-MacBook-Pro.local>
Co-authored-by: Cursor <cursoragent@cursor.com>
kamath and others added 2 commits September 16, 2026 15:23
* ci: open automation PRs with GITHUB_TOKEN instead of Docs Bot

Drop the GitHub App token helper and generate llms.txt in the toolkit
docs workflow so automation PRs no longer depend on a second workflow
starting from the bot push.

Co-authored-by: Anirudh Kamath <kamath@users.noreply.github.com>

* fix: avoid Biome noTemplateCurlyInString in workflow test

The assertion for github.token used a GitHub Actions expression inside a
regular string, which Ultracite flagged as a leftover template placeholder.

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Anirudh Kamath <kamath@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants