fix: Mcp composer tool header fix

[mfortman11]

Before

after

Summary by CodeRabbit

• Style

  • Updated the layout and alignment of tool-related buttons for a more streamlined appearance.
  • Improved button styling and positioning, including dynamic icon and variant changes based on feature flags.

• New Features

  • Added a descriptive label with tooltip and info icon above the tools list in the MCP server tab for better user guidance.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes update the layout and labeling of the MCP server tools UI. The ToolsComponent's internal structure and button rendering logic are refactored, removing the tooltip label and info icon from within the component. Instead, a descriptive label with a tooltip is introduced above the tools list in the McpServerTab component.

Changes

File(s)	Change Summary
src/frontend/src/components/core/parameterRenderComponent/components/ToolsComponent/index.tsx	Refactored layout and button rendering; removed internal tooltip label; updated button styling and icon logic.
src/frontend/src/pages/MainPage/pages/homePage/components/McpServerTab.tsx	Added tooltip-wrapped "Flows/Tools" label above tools list; updated layout with nested flex containers.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant McpServerTab
    participant ToolsComponent

    User->>McpServerTab: View MCP Server Tab
    McpServerTab->>ToolsComponent: Render ToolsComponent
    ToolsComponent-->>McpServerTab: Rendered tools UI (without internal label)
    McpServerTab-->>User: Display tools list with external tooltip label

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• fix: make MCP naming changes, change actions to tools #8860: Updates UI text labels and terminology from "actions" to "tools" across various components, including ToolsComponent; related by context but not overlapping in code-level modifications.

Suggested labels

size:M, lgtm

Suggested reviewers

• edwinjosechittilappilly

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch mcp-composer-tool-header-fix

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[lucaseduoli]

LGTM

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	81.44% (373/458)	64.82% (223/344)	67.69% (44/65)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
93	0 💤	0 ❌	0 🔥	2.909s ⏱️

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.83%. Comparing base (b5b9d7e) to head (e50471e).
Report is 1 commits behind head on main.

❌ Your project status has failed because the head coverage (51.83%) is below the target coverage (60.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9161   +/-   ##
=======================================
  Coverage   51.83%   51.83%           
=======================================
  Files         633      633           
  Lines       43407    43407           
  Branches      125      125           
=======================================
  Hits        22500    22500           
  Misses      20857    20857           
  Partials       50       50           

Flag	Coverage Δ
frontend	69.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.