Pi Babysit: address PR #8251 feedback

Author: Sim Pi Agent

apps/sim/content/library/best-ai-agent-builders-with-mcp-support/index.mdx

@@ -62,15 +62,11 @@ The table separates platforms that consume external MCP tools from those that ma
 
 | Platform | MCP client support | Publishes workflows or actions as MCP tools | Transport | Authentication | Deployment | Model choice | Enterprise controls | Human approval | Observability | Coding requirements |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| **Sim** | [Yes](https://docs.sim.ai/agents/mcp) | [Yes, deployed workflows](https://docs.sim.ai/workflows/deployment/mcp) | See the [current deployment configurations](https://docs.sim.ai/workflows/deployment/mcp) | See the [current deployment guide](https://docs.sim.ai/workflows/deployment/mcp) | [Hosted or self-hosted](https://docs.sim.ai/platform/self-hosting) | Hosted multi-model access and BYOK; local-model workflows require [Enterprise access](https://docs.sim.ai/platform/enterprise) | [Enterprise controls](https://docs.sim.ai/platform/enterprise) and self-hosting | Available, but the reviewed MCP documentation does not establish MCP-specific approval behavior | Run logs are available, but the reviewed MCP documentation does not establish MCP-specific logging coverage | Low-code; technical work may be needed for custom integrations or self-hosting |
+| **Sim** | [Yes](https://docs.sim.ai/agents/mcp) | [Yes, deployed workflows](https://docs.sim.ai/workflows/deployment/mcp) | See the [current deployment configurations](https://docs.sim.ai/workflows/deployment/mcp) | See the [current deployment guide](https://docs.sim.ai/workflows/deployment/mcp) | [Hosted or self-hosted](https://docs.sim.ai/platform/self-hosting) | Hosted multi-model access and BYOK; self-hosted deployments can use [locally configured Ollama models](https://docs.sim.ai/platform/self-hosting/environment-variables) | [Enterprise controls](https://docs.sim.ai/platform/enterprise) and self-hosting | Available, but the reviewed MCP documentation does not establish MCP-specific approval behavior | Run logs are available, but the reviewed MCP documentation does not establish MCP-specific logging coverage | Low-code; technical work may be needed for custom integrations or self-hosting |
 | **n8n** | [Yes](https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp) | [Yes](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger) | Confirm against the [client](https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp) and [server](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger) node documentation | [Bearer, header, or OAuth, depending on the node](https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp) | [Cloud or self-hosted](https://n8n.io/) | [Multiple model providers](https://n8n.io/) | [Features vary by plan](https://n8n.io/pricing/) | Unclear from the reviewed first-party MCP documentation | Execution visibility should be tested for the selected MCP node | [Low-code, with code nodes available](https://docs.n8n.io/build/code-in-n8n/using-the-code-node) |
 | **Zapier** | [Yes](https://help.zapier.com/hc/en-us/articles/38777069364109-Connect-remote-MCP-servers-to-Zapier-using-MCP-Client) | [Selected app actions, not arbitrary existing Zaps](https://help.zapier.com/hc/en-us/articles/36265551472781-Manage-tools-for-your-Zapier-MCP-server) | Unclear from the reviewed first-party documentation | [Managed connections and authorization](https://docs.zapier.com/mcp/home) | [Managed cloud](https://docs.zapier.com/mcp/home) | Product-dependent | [Features vary by plan](https://zapier.com/pricing) | Unclear from the reviewed first-party MCP documentation | Unclear from the reviewed first-party MCP documentation | [No-code configuration](https://zapier.com/mcp) |
 | **Make** | [Yes](https://apps.make.com/c5ZhYquO55e90hoCJ0rzt) | [Yes, eligible scenarios](https://help.make.com/get-started-with-make-mcp-server) | Unclear from the reviewed first-party documentation | [Configured connections and toolbox access](https://help.make.com/mcp-toolboxes) | [Managed cloud](https://www.make.com/) | [Multiple providers through integrations](https://www.make.com/) | [Features vary by plan](https://www.make.com/en/pricing) | Unclear from the reviewed first-party MCP documentation | Unclear from the reviewed first-party MCP documentation | [No-code to low-code](https://www.make.com/en/pricing) |
 | **Gumloop** | [Yes](https://docs.gumloop.com/nodes/mcp/custom_mcp_servers) | [Yes](https://docs.gumloop.com/mcp-server/overview) | Unclear from the reviewed first-party documentation | See the [MCP server documentation](https://docs.gumloop.com/mcp-server/overview) | [Managed cloud](https://docs.gumloop.com/) | [Multiple models](https://docs.gumloop.com/core-concepts/ai_models) | [Enterprise identity controls](https://docs.gumloop.com/enterprise-features/sso_saml_scim) | Unclear from the reviewed first-party MCP documentation | Unclear from the reviewed first-party MCP documentation | [No-code builder](https://docs.gumloop.com/core-concepts/workbooks) |
-| **Dify** | Not verified from reviewed first-party documentation | Not verified from reviewed first-party documentation | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear |
-| **Langflow** | Not verified from reviewed first-party documentation | Not verified from reviewed first-party documentation | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear |
-| **Flowise** | Not verified from reviewed first-party documentation | Not verified from reviewed first-party documentation | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear |
-| **Microsoft Copilot Studio** | Not verified from reviewed first-party documentation | Not verified from reviewed first-party documentation | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear | Unclear |
 
 Authentication methods, enterprise controls, human approval features, and observability can vary by plan and MCP connection type. During evaluation, record the supported transport, credential method, approval behavior, and execution data available for each product. Buyers should confirm current limits before choosing a production deployment.
 
@@ -80,7 +76,7 @@ Sim is an open, extensible, multi-model agent workspace for building custom agen
 
 Sim can [consume tools from external MCP servers](https://docs.sim.ai/agents/mcp) and turn a deployed workflow into a tool that other applications call through an MCP server. After you create a server and add the workflow as a tool, Sim provides [connection configurations for supported MCP clients](https://docs.sim.ai/workflows/deployment/mcp). Supported clients include Cursor, Codex, Claude Code, Claude Desktop, VS Code, and Sim itself. Each client can then invoke the workflow through the tool interface instead of reproducing its logic locally.
 
-Sim supports hosted model access and bring-your-own-key connections for provider accounts. Local-model workflows are not available on regular plans; they require [Enterprise access](https://docs.sim.ai/platform/enterprise). Model and deployment availability can vary by plan and environment, so buyers should verify current terms for their intended setup. The [BYOK and multi-model agent builder guide](https://www.sim.ai/library/byok-multi-model-ai-agent-builder) covers the tradeoffs behind provider choice.
+Sim supports hosted model access and bring-your-own-key connections for provider accounts. Self-hosted deployments can use [locally configured Ollama models](https://docs.sim.ai/platform/self-hosting/environment-variables). Model and deployment availability can vary by plan and environment, so buyers should verify current terms for their intended setup. The [BYOK and multi-model agent builder guide](https://www.sim.ai/library/byok-multi-model-ai-agent-builder) covers the tradeoffs behind provider choice.
 
 **Best for:** Sim fits technical buyers who want to build custom, multi-model agents and expose their workflows to several MCP clients. It also suits buyers who need source access or the option to self-host.
 
@@ -200,8 +196,7 @@ Before selecting a platform, test a representative workflow rather than relying
 - Verify that a remote client can reach the production endpoint through the intended proxy, firewall, and load balancer.
 - Confirm plan limits, preview or beta status, data retention, identity controls, and production support with the vendor.
 - Authenticate with the production credential method and verify how credentials are stored and rotated.
-- Inspect the tool name, description, and input schema that the model receives.
-- Test the required model provider and verify any plan restrictions, including Enterprise access for Sim workflows that use local models.
+- Test the required model provider and verify any plan or deployment restrictions.
 - Confirm whether the platform can run in the required cloud, self-hosted, or private-network environment.
 - Estimate usage with a realistic number of agent loops and tool calls rather than a single successful run.
 - Ask the intended maintainer to modify the workflow and recover from a failed execution.