improvement(mcp): add all MCP server tools individually instead of as single server entry

[waleedlatif1]

Summary

• "Use all tools" now adds each MCP tool individually as mcp StoredTools instead of one mcp-server entry
• Users can configure params per-tool and remove individual tools after bulk-adding
• Right-click X on MCP tools shows "Remove all from [server]" option
• Removed mcp-server StoredTool type and all backend expansion logic
• Drill-down navigation (server folders → tools) stays

Type of Change

• New feature / Enhancement

Testing

Tested manually. 44 agent-handler tests + 39 tool-validation tests pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 27, 2026 9:31pm

[greptile-apps]

Greptile Summary

Replaces server-level MCP tool selection with individual tool entries. Previously, selecting "all tools" from an MCP server stored a single mcp-server entry that the backend expanded at execution time. Now the frontend immediately adds each tool as a separate mcp StoredTool, enabling per-tool configuration and selective removal.

Key changes:

• Frontend now stores individual mcp tool entries instead of single mcp-server entry
• Added right-click context menu on MCP tool X buttons to "Remove all from [server]"
• Backend removed all mcp-server expansion logic (processMcpServerSelections, createMcpToolFromDiscoveredServerTool)
• Removed isMcpServerAlreadySelected helper and getMcpServerIssue validation

Already flagged in previous review:

• tool-input.tsx:1298 - "Use all tools" overwrites existing tool configurations
• tool-input.tsx:1821 - O(n²) filter performance issue

Confidence Score: 3/5

• Safe to merge with two known issues already flagged in previous review that should be addressed
• Core logic is sound and backend changes are clean, but has performance concerns and UX issues in the frontend that were already identified
• Pay attention to tool-input.tsx lines 1298-1322 (config overwrite) and 1821-1824 (performance)

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/sub-block/components/tool-input/tool-input.tsx	Removed mcp-server type handling and added right-click context menu for MCP tools, but has performance issue and overwrites existing tool configurations
apps/sim/executor/handlers/agent/agent-handler.ts	Removed mcp-server type checks and backend expansion logic cleanly

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph Before ["Before: Server-Level Selection"]
        A1[User clicks 'Use all tools'] --> A2[Frontend stores single mcp-server entry]
        A2 --> A3[Agent execution starts]
        A3 --> A4[Backend processMcpServerSelections]
        A4 --> A5[Backend discovers all tools from server]
        A5 --> A6[Backend expands to individual tools]
        A6 --> A7[LLM receives all tools]
    end
    
    subgraph After ["After: Individual Tool Selection"]
        B1[User clicks 'Use all tools'] --> B2[Frontend immediately creates individual mcp entries]
        B2 --> B3[User can configure each tool]
        B3 --> B4[Agent execution starts]
        B4 --> B5[Backend receives individual tools]
        B5 --> B6[LLM receives configured tools]
    end
    
    style Before fill:#fee,stroke:#c88,stroke-width:2px
    style After fill:#efe,stroke:#8c8,stroke-width:2px

Loading

_{Last reviewed commit: fb3fd2d}

[greptile-apps]

_{5 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR