docs: add synonyms so Algolia surfaces the hybrid/self-hosted pages - #1144
Open
teallarson wants to merge 5 commits into
Open
docs: add synonyms so Algolia surfaces the hybrid/self-hosted pages#1144teallarson wants to merge 5 commits into
teallarson wants to merge 5 commits into
Conversation
…yms so Algolia surfaces the page
…golia surfaces the page
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
teallarson
marked this pull request as draft
August 27, 2026 15:18
teallarson
commented
Sep 1, 2026
teallarson
marked this pull request as ready for review
September 1, 2026 20:11
sdreyer
reviewed
Sep 1, 2026
| </Callout> | ||
|
|
||
| 1. **Navigate to the MCP Servers page** in your [Arcade dashboard](https://app.arcade.dev/servers) | ||
| 1. **Navigate to the MCP Servers page** in your [Arcade dashboard](https://api.arcade.dev/dashboard/servers) |
Contributor
Author
There was a problem hiding this comment.
No and agents won't stop doing it 😖
teallarson
commented
Sep 1, 2026
…-synonyms # Conflicts: # app/en/operate/deploy/warp-pipes/page.mdx
evantahler
reviewed
Sep 2, 2026
| <GuideOverview.Outcomes> | ||
|
|
||
| An on-premises MCP server deployment allows you to execute tools in your own environment while still leveraging Arcade's cloud Engine infrastructure. This gives you the flexibility to access private resources, maintain data security, and customize your environment while leveraging Arcade's MCP server management and federation capabilities. | ||
| A hybrid MCP server deployment — also called a self-hosted worker or hybrid worker — runs the MCP server on infrastructure you control (on-premises, private cloud, VPC, or any private network) while Arcade's cloud Engine keeps handling identity, routing, and governance. This gives you the flexibility to access private resources behind a firewall, keep sensitive data inside your network, and customize your environment while leveraging Arcade's MCP server management and federation capabilities. |
Contributor
There was a problem hiding this comment.
This is all technical correct!
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
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.
From Teal, the human
🚨 I think my agent may be wrong on some of these changes, but I don't know these product surfaces well enough to say how. Please DO read them.
Problem
The latest Algolia weekly summary (application
BJB8PBSQ9T, Arcade Docs, Aug 17–23) reports a 32.76% no-result rate ondocs_arcade_dev_bjb8pbsq9t_docsearch. Several of the zero-hit queries point at pages that already exist in this repo but use different words than the users typing them.Zero-result search queries in scope
From the Algolia “Searches with no results” list:
hybrid worker deploymentself-hosted mcp server private networkhybrid deployment self-hosted worker vpc private network cloud engineip allowlist firewall egressThe rest of the report's zero-hit list (kept here for context, not addressed by this PR because they're real content gaps rather than terminology mismatches):
railwayherokuredact pii from tool outputs response transformation middlewaregateway oauth token expiration refresh token session lifetime mcp client re-authenticategoogle cloud console create oauth client redirect url arcade dashboard add provideradd secrets to deployed mcp server dashboard secrets page requires_secretsWhy the four in-scope queries returned zero
app/en/operate/deploy/on-prem/page.mdxis titled Hybrid MCP servers, but the body only ever uses “on-premises.” The words worker, self-hosted, hybrid worker, VPC, private network, and firewall never appear on the page, so Algolia can't match them.app/en/operate/deploy/warp-pipes/page.mdxdescribes the SSRF allowlist and outbound connections, but never uses IP allowlist, firewall, or egress — the exact wording of the user query.Fix
Add the missing synonyms naturally into the prose of both pages so the crawler indexes them without changing meaning or introducing new concepts.
app/en/operate/deploy/on-prem/page.mdxapp/en/operate/deploy/warp-pipes/page.mdxNo behavior, no config, no restructuring — just terminology the crawler was missing.
Effect on the Algolia index
On merge to
main,algolia-reindex.ymlfires (the paths touched are underapp/en/**), which triggers a fresh crawl. The four zero-hit queries above should now surface the corresponding pages.Test plan
algolia-reindex.ymlto completedocs.arcade.devand confirm the on-prem / warp-pipes page appearsNote
Low Risk
Documentation-only wording changes; the only behavioral risk is losing the Arcade vs Remote MCP callout during registration.
Overview
Updates the Hybrid MCP servers (
on-prem) docs so Algolia can match queries like “hybrid worker,” “self-hosted MCP,” “VPC,” and “private network,” without changing the underlying setup flow.The frontmatter description and early overview now name a self-hosted / hybrid worker deployment on private network or VPC, and prose repeats those terms in the “how it works” and benefits sections (including firewall and internal APIs). Registration is described as registering the server as a worker where relevant.
Removes the info Callout that contrasted the Arcade server type with Remote MCP and linked to the remote MCP governance page—worth confirming that distinction isn’t still needed for readers on this page.
Reviewed by Cursor Bugbot for commit 17abc55. Bugbot is set up for automated code reviews on this repo. Configure here.