🧭 Type of Feature

Please select the most appropriate category:

• Enhancement to existing functionality
• New feature or capability
• New MCP-compliant server
• New component or integration
• Developer tooling or test improvement
• Packaging, automation and deployment (ex: pypi, docker, quay.io, kubernetes, terraform)
• Other (please describe below)

🧑🏻‍💻 User Story

As a: user
I want: to refresh an MCP
So that: I can access the latest tools an MCP might have released

✅ Acceptance Criteria

Scenario: New MCP Tools
  An MCP has added new tools since it was registered in CF
  When the user clicks the `Refresh tools` button
  Then the MCP tools are refreshed, and the user is notified that the new tools are registered to CF

Scenario: No new MCP Tools
  An MCP has not added new tools since it was registered in CF
  When the user clicks the `Refresh tools` button
  Then the MCP tools are refreshed, and the user is informed no updates were made.

📐 Design Sketch (optional)

Include a diagram, sketch, or flow (use Mermaid if desired):

flowchart TD
    A[Client] -->|POST /gateway/gateway_id/refresh/tools| B(MCPGateway)
    B -->|/tools/list| C[MCP]
    B -->|Response - HTMX| A

🔗 MCP Standards Check

• Change adheres to current MCP specifications
• No breaking changes to existing MCP-compliant integrations
• If deviations exist, please describe them below:

🔄 Alternatives Considered

• Pooling for new tools periodically was considered, but the performance costs out-weight the benefits. It may be added in the future as an optional, flag-based feature.

🔄 Additional information

The button should be available both in the MCP table and the virtual server creation/editing forms, which may require separate admin_route endpoints, for the different HTMX responses (success message for mcp table, tools checkbox list for the virtual server forms).