Skip to content

docs(mcp): retire the dev MCP page, redirect to help (PRDCT-580) - #405

Merged
jordanrburger merged 2 commits into
mainfrom
docs/retire-dev-mcp
Aug 5, 2026
Merged

docs(mcp): retire the dev MCP page, redirect to help (PRDCT-580)#405
jordanrburger merged 2 commits into
mainfrom
docs/retire-dev-mcp

Conversation

@Iamfle4ka

Copy link
Copy Markdown
Collaborator

Jira issue(s): PRDCT-580 — companion delete-from-dev PR for connection-docs#1050 (merged 2026-08-03).

The dev MCP page was merged into help.keboola.com/ai/mcp-server/. Leaving it up means two competing MCP overviews, which is exactly what the migration is supposed to remove — so the page becomes a redirect stub instead of a duplicate.

Changes:

  • integrate/mcp.md → front-matter-only redirect_to: https://help.keboola.com/ai/mcp-server/ stub (jekyll-redirect-from, already enabled in _config.yml). The URL stays alive for bookmarks and for the one inbound reference in the keboola org; the duplicate content is gone.
  • Dropped the MCP Integration entry from _data/navigation.yml.
  • Repointed the two dev pages that linked here (index.md, overview/index.md) straight at help, so they don't bounce through the stub.

Coverage check before stubbing: everything the dev page documented is on the help page, in most cases fresher — MCP clients, the Claude Messages API connector (help has the current anthropic-beta: mcp-client-2025-11-20 header), OpenAI Agents SDK (help has the correct agents imports), LangChain (help uses the official langchain-mcp-adapters; the dev copy still says no connector exists), CrewAI, building your own client, tool-authorization headers, local Docker/uv execution, remote OAuth setup and the mcp-remote fallback.

The only dev-only section is the MCP Server Capabilities support matrix (Transports/Prompts/Tools/Resources/Sampling/Roots). It is intentionally dropped, not ported — per the review note on #1050.

Not in this PR: real 301s for developers.keboola.com. redirect_to emits a meta-refresh page (HTTP 200 + canonical); a 301 needs an S3 routing-rule / CloudFront change outside this repo.

The dev /integrate/mcp/ page was merged into help.keboola.com/ai/mcp-server/
in keboola/connection-docs#1050. Everything it covered — MCP clients, the
Claude Messages API connector, OpenAI Agents SDK / LangChain / CrewAI,
building your own client, tool-authorization headers, local Docker/uv
execution and the remote (OAuth) setup — now lives on the help page, in most
cases in a fresher form (correct `anthropic-beta` header, the official
`langchain-mcp-adapters` package, fixed Agents SDK imports).

Leaving the dev page up means two competing MCP overviews, so it becomes a
`redirect_to` stub: the URL stays alive for the one inbound reference in the
org and for bookmarks, but the duplicate content is gone.

The only dev-only section, the "MCP Server Capabilities" support matrix, is
intentionally dropped rather than ported.

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

linear-code Bot commented Aug 3, 2026

Copy link
Copy Markdown

PRDCT-580

@Iamfle4ka

Copy link
Copy Markdown
Collaborator Author

Sibling of #406 — same pattern (redirect_to stub, front matter kept), and it inherits the same fallback page: the branded "this page has moved" note lives in _layouts/redirect.html, added in #406. Merged in either order this PR works; if it lands first, /integrate/mcp/ shows jekyll-redirect-from's default "Redirecting… Click here if you are not redirected." until #406 follows.

Note this one is not an identical-path move: /integrate/mcp/help.keboola.com/ai/mcp-server/, so the note correctly omits the "the path did not change" line.

@jordanrburger
jordanrburger enabled auto-merge August 5, 2026 16:20
@jordanrburger
jordanrburger merged commit b20fa1b into main Aug 5, 2026
1 check passed
@jordanrburger
jordanrburger deleted the docs/retire-dev-mcp branch August 5, 2026 16:21
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.

2 participants