Skip to content

Conversation

@pabel-rh
Copy link
Member

@pabel-rh pabel-rh commented Oct 28, 2025

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):
1.8.0, main
Issue:
RHDHPAI-1087
Preview:
https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1462/model-context-protocol-tools/

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Oct 28, 2025

Copy link
Member

@johnmcollier johnmcollier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple small suggestions

Copy link
Member

@karthikjeeyar karthikjeeyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used the following images and followed this documentation to successfully connect the mcp server to the cursor client.

plugins:
    - package: oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-plugin-mcp-actions-backend:bs_1.42.5__0.1.2!backstage-plugin-mcp-actions-backend
      disabled: false
    - package: oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-software-catalog-mcp-tool:bs_1.42.5__0.2.3!red-hat-developer-hub-backstage-plugin-software-catalog-mcp-tool
      disabled: false
    - package: oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-techdocs-mcp-tool:bs_1.42.5__0.3.0!red-hat-developer-hub-backstage-plugin-techdocs-mcp-tool
      disabled: false

MCP server connected in Cursor client:

image

Chat with tool calling:

image

Copy link
Member

@johnmcollier johnmcollier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doc changes look good to me

Copy link
Member

@karthikjeeyar karthikjeeyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Member

@johnmcollier johnmcollier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @pabel-rh I'm just raising a couple small suggestions that @mattreid raised during test day. Is it okay if we include these changes in the docs?


.Procedure

. Verify the authentication token.
Copy link
Member

@johnmcollier johnmcollier Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add a small section to this step (verify the authentication token).

Set this token as the bearer token in your MCP client could we also specify "ensure the authorization header in the configuration specifies Bearer before the token. E.g. Bearer <mcp-token>"`

(or something to that effect)


If your MCP client connects to the server but cannot find deployed tools, an authentication or configuration issue is likely.

.Procedure
Copy link
Member

@johnmcollier johnmcollier Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add an additional verification step here?

Something like: Verify app config changes:

"Verify that there are no duplicate backend entries in the app config and that indentation is accurate. The changes to configure the static token and mcp plugin sources should go under an existing backend field, if present. If there's confusion, consult the sample app config provided in proc-configuring-model-context-protocol_{context}"]"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants