Skip to content

Drop "MCP built on Redpanda Connect" framing#10

Closed
micheleRP wants to merge 1 commit into
mainfrom
remove-mcp-connect-claim
Closed

Drop "MCP built on Redpanda Connect" framing#10
micheleRP wants to merge 1 commit into
mainfrom
remove-mcp-connect-claim

Conversation

@micheleRP
Copy link
Copy Markdown
Contributor

Summary

  • MCP no longer rides on Redpanda Connect, so reframe both the MCP product description on the home page and the MCP trace-structure docs in observability.
  • ROOT/pages/index.adoc: rewrite the MCP servers paragraph — drop "Built on Redpanda Connect", drop "wrap the same proven connectors", and drop the implied "300 connectors" claim that suggested MCP inherits the Connect catalog. Keep the actual value props (lightweight, OIDC, deterministic policies, YAML, attack-prevention).
  • observability/pages/concepts.adoc: in the MCP trace-structure docs, swap "Redpanda Connect layer / processing / service operations / processor" descriptions for neutral "MCP server" wording. Removes the Redpanda Connect row from the layer table, drops the "redpanda-connect for internal processing" reference in the span-attribute description, and updates the layer-hierarchy ASCII diagram.

Out of scope

  • The BYOA telemetry page (observability/pages/ingest-custom-traces.adoc) still references Redpanda Connect — that's the user's own trace-ingestion pipeline (Connect is the receiver), not MCP internals.
  • Agents docs that say "agents have access to 300+ Redpanda Connect connectors" stay as-is — agents are a separate workflow from MCP and the Connect linkage there isn't part of this update.

Preview pages

Test plan

  • Build locally and confirm the MCP servers paragraph on the home page no longer mentions Redpanda Connect or 300 connectors.
  • Spot-check observability/concepts/ — the layer table no longer includes a Redpanda Connect row, and the MCP trace flow diagram says "MCP Server layer" instead of "Redpanda Connect layer" at the lowest level.

🤖 Generated with Claude Code

MCP no longer rides on Redpanda Connect, so reframe the MCP product
description and the related observability trace structure:

- ROOT/pages/index.adoc: rewrite the MCP servers paragraph; drop the
  "Built on Redpanda Connect" / "wrap the same proven connectors" /
  "300 connectors" claims. Keep the actual value props (lightweight,
  OIDC, deterministic policies, YAML, security).
- observability/pages/concepts.adoc: in the MCP trace structure
  documentation, replace "Redpanda Connect layer / processing /
  service operations / processor" descriptions with neutral "MCP
  server" wording. Removes the "Redpanda Connect" row from the layer
  table, drops the "redpanda-connect for internal processing"
  reference, and updates the layer-hierarchy ASCII diagram.

Out of scope: the BYOA telemetry page (ingest-custom-traces.adoc)
still references Redpanda Connect — that's the user's own
trace-ingestion pipeline (Connect is the receiver), not MCP internals.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@micheleRP micheleRP requested a review from a team as a code owner April 29, 2026 20:51
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 29, 2026

Deploy Preview for redpanda-agentic-data-plane ready!

Name Link
🔨 Latest commit 92c1d6e
🔍 Latest deploy log https://app.netlify.com/projects/redpanda-agentic-data-plane/deploys/69f26f6abc6a380008fb6813
😎 Deploy Preview https://deploy-preview-10--redpanda-agentic-data-plane.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@micheleRP
Copy link
Copy Markdown
Contributor Author

Folded into #9 — both reframings ship together. See commit 7bbcb45 on remove-cluster-framing.

@micheleRP micheleRP closed this Apr 29, 2026
@micheleRP micheleRP deleted the remove-mcp-connect-claim branch April 29, 2026 20:54
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.

1 participant