feat(workflow-as-mcp): wrapping workflows in the same workspace as MCP tools to particular MCP servers

apps/docs/content/docs/en/mcp/deploy-workflows.mdx

@@ -0,0 +1,108 @@
+---
+title: Deploy Workflows as MCP
+description: Expose your workflows as MCP tools for external AI assistants and applications
+---
+
+import { Video } from '@/components/ui/video'
+import { Callout } from 'fumadocs-ui/components/callout'
+
+Deploy your workflows as MCP tools to make them accessible to external AI assistants like Claude Desktop, Cursor, and other MCP-compatible clients. This turns your workflows into callable tools that can be invoked from anywhere.
+
+## Creating and Managing MCP Servers
+
+MCP servers group your workflow tools together. Create and manage them in workspace settings:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp/mcp-server.mp4" width={700} height={450} />
+</div>
+
+1. Navigate to **Settings → MCP Servers**
+2. Click **Create Server**
+3. Enter a name and optional description
+4. Copy the server URL for use in your MCP clients
+5. View and manage all tools added to the server
+
+## Adding a Workflow as a Tool
+
+Once your workflow is deployed, you can expose it as an MCP tool:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp/mcp-deploy-tool.mp4" width={700} height={450} />
+</div>
+
+1. Open your deployed workflow
+2. Click **Deploy** and go to the **MCP** tab
+3. Configure the tool name and description
+4. Add descriptions for each parameter (helps AI understand inputs)
+5. Select which MCP servers to add it to
+
+<Callout type="info">
+The workflow must be deployed before it can be added as an MCP tool.
+</Callout>
+
+## Tool Configuration
+
+### Tool Name
+Use lowercase letters, numbers, and underscores. The name should be descriptive and follow MCP naming conventions (e.g., `search_documents`, `send_email`).
+
+### Description
+Write a clear description of what the tool does. This helps AI assistants understand when to use the tool.
+
+### Parameters
+Your workflow's input format fields become tool parameters. Add descriptions to each parameter to help AI assistants provide correct values.
+
+## Connecting MCP Clients
+
+Use the server URL from settings to connect external applications:
+
+### Claude Desktop
+Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json`):
+
+```json
+{
+  "mcpServers": {
+    "my-sim-workflows": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote", "YOUR_SERVER_URL"]
+    }
+  }
+}
+```
+
+### Cursor
+Add the server URL in Cursor's MCP settings using the same mcp-remote pattern.
+
+<Callout type="warn">
+Include your API key header (`X-API-Key`) for authenticated access when using mcp-remote or other HTTP-based MCP transports.
+</Callout>
+
+## Server Management
+
+From the server detail view in **Settings → MCP Servers**, you can:
+
+- **View tools**: See all workflows added to a server
+- **Copy URL**: Get the server URL for MCP clients
+- **Add workflows**: Add more deployed workflows as tools
+- **Remove tools**: Remove workflows from the server
+- **Delete server**: Remove the entire server and all its tools
+
+## How It Works
+
+When an MCP client calls your tool:
+
+1. The request is received at your MCP server URL
+2. Sim validates the request and maps parameters to workflow inputs
+3. The deployed workflow executes with the provided inputs
+4. Results are returned to the MCP client
+
+Workflows execute using the same deployment version as API calls, ensuring consistent behavior.
+
+## Permission Requirements
+
+| Action | Required Permission |
+|--------|-------------------|
+| Create MCP servers | **Admin** |
+| Add workflows to servers | **Write** or **Admin** |
+| View MCP servers | **Read**, **Write**, or **Admin** |
+| Delete MCP servers | **Admin** |
+

apps/docs/content/docs/en/mcp/index.mdx

@@ -1,8 +1,10 @@
 ---
-title: MCP (Model Context Protocol)
+title: Using MCP Tools
+description: Connect external tools and services using the Model Context Protocol
 ---
 
 import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
 import { Callout } from 'fumadocs-ui/components/callout'
 
 The Model Context Protocol ([MCP](https://modelcontextprotocol.com/)) allows you to connect external tools and services using a standardized protocol, enabling you to integrate APIs and services directly into your workflows. With MCP, you can extend Sim's capabilities by adding custom integrations that work seamlessly with your agents and workflows.
@@ -20,14 +22,8 @@ MCP is an open standard that enables AI assistants to securely connect to extern
 
 MCP servers provide collections of tools that your agents can use. Configure them in workspace settings:
 
-<div className="flex justify-center">
-  <Image
-    src="/static/blocks/mcp-1.png"
-    alt="Configuring MCP Server in Settings"
-    width={700}
-    height={450}
-    className="my-6"
-  />
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp/settings-mcp-tools.mp4" width={700} height={450} />
 </div>
 
 1. Navigate to your workspace settings
@@ -40,6 +36,10 @@ MCP servers provide collections of tools that your agents can use. Configure the
 You can also configure MCP servers directly from the toolbar in an Agent block for quick setup.
 </Callout>
 
+### Refresh Tools
+
+Click **Refresh** on a server to fetch the latest tool schemas and automatically update any agent blocks using those tools with the new parameter definitions.
+
 ## Using MCP Tools in Agents
 
 Once MCP servers are configured, their tools become available within your agent blocks:

apps/docs/content/docs/en/mcp/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "MCP",
+  "pages": ["index", "deploy-workflows"],
+  "defaultOpen": false
+}

apps/sim/app/(landing)/careers/page.tsx

@@ -3,6 +3,7 @@
 import { useRef, useState } from 'react'
 import { createLogger } from '@sim/logger'
 import { X } from 'lucide-react'
+import { Textarea } from '@/components/emcn'
 import { Button } from '@/components/ui/button'
 import { Input } from '@/components/ui/input'
 import { Label } from '@/components/ui/label'
@@ -13,7 +14,6 @@ import {
   SelectTrigger,
   SelectValue,
 } from '@/components/ui/select'
-import { Textarea } from '@/components/ui/textarea'
 import { isHosted } from '@/lib/core/config/feature-flags'
 import { cn } from '@/lib/core/utils/cn'
 import { quickValidateEmail } from '@/lib/messaging/email/validation'

apps/sim/app/(landing)/studio/[slug]/page.tsx

@@ -1,7 +1,7 @@
 import type { Metadata } from 'next'
 import Image from 'next/image'
 import Link from 'next/link'
-import { Avatar, AvatarFallback, AvatarImage } from '@/components/ui/avatar'
+import { Avatar, AvatarFallback, AvatarImage } from '@/components/emcn'
 import { FAQ } from '@/lib/blog/faq'
 import { getAllPostMeta, getPostBySlug, getRelatedPosts } from '@/lib/blog/registry'
 import { buildArticleJsonLd, buildBreadcrumbJsonLd, buildPostMetadata } from '@/lib/blog/seo'

apps/sim/app/(landing)/studio/post-grid.tsx

@@ -2,7 +2,7 @@
 
 import Image from 'next/image'
 import Link from 'next/link'
-import { Avatar, AvatarFallback, AvatarImage } from '@/components/ui/avatar'
+import { Avatar, AvatarFallback, AvatarImage } from '@/components/emcn'
 
 interface Author {
   id: string

apps/sim/app/api/mcp/discover/route.ts

@@ -0,0 +1,88 @@
+import { db } from '@sim/db'
+import { permissions, workflowMcpServer, workspace } from '@sim/db/schema'
+import { createLogger } from '@sim/logger'
+import { and, eq, sql } from 'drizzle-orm'
+import { type NextRequest, NextResponse } from 'next/server'
+import { checkHybridAuth } from '@/lib/auth/hybrid'
+import { getBaseUrl } from '@/lib/core/utils/urls'
+
+const logger = createLogger('McpDiscoverAPI')
+
+export const dynamic = 'force-dynamic'
+
+/**
+ * Discover all MCP servers available to the authenticated user.
+ */
+export async function GET(request: NextRequest) {
+  try {
+    const auth = await checkHybridAuth(request, { requireWorkflowId: false })
+
+    if (!auth.success || !auth.userId) {
+      return NextResponse.json(
+        { success: false, error: 'Authentication required. Provide X-API-Key header.' },
+        { status: 401 }
+      )
+    }
+
+    const userId = auth.userId
+
+    const userWorkspacePermissions = await db
+      .select({ entityId: permissions.entityId })
+      .from(permissions)
+      .where(and(eq(permissions.userId, userId), eq(permissions.entityType, 'workspace')))
+
+    const workspaceIds = userWorkspacePermissions.map((w) => w.entityId)
+
+    if (workspaceIds.length === 0) {
+      return NextResponse.json({ success: true, servers: [] })
+    }
+
+    const servers = await db
+      .select({
+        id: workflowMcpServer.id,
+        name: workflowMcpServer.name,
+        description: workflowMcpServer.description,
+        workspaceId: workflowMcpServer.workspaceId,
+        workspaceName: workspace.name,
+        createdAt: workflowMcpServer.createdAt,
+        toolCount: sql<number>`(
+          SELECT COUNT(*)::int 
+          FROM "workflow_mcp_tool" 
+          WHERE "workflow_mcp_tool"."server_id" = "workflow_mcp_server"."id"
+        )`.as('tool_count'),
+      })
+      .from(workflowMcpServer)
+      .leftJoin(workspace, eq(workflowMcpServer.workspaceId, workspace.id))
+      .where(sql`${workflowMcpServer.workspaceId} IN ${workspaceIds}`)
+      .orderBy(workflowMcpServer.name)
+
+    const baseUrl = getBaseUrl()
+
+    const formattedServers = servers.map((server) => ({
+      id: server.id,
+      name: server.name,
+      description: server.description,
+      workspace: { id: server.workspaceId, name: server.workspaceName },
+      toolCount: server.toolCount || 0,
+      createdAt: server.createdAt,
+      url: `${baseUrl}/api/mcp/serve/${server.id}`,
+    }))
+
+    logger.info(`User ${userId} discovered ${formattedServers.length} MCP servers`)
+
+    return NextResponse.json({
+      success: true,
+      servers: formattedServers,
+      authentication: {
+        method: 'API Key',
+        header: 'X-API-Key',
+      },
+    })
+  } catch (error) {
+    logger.error('Error discovering MCP servers:', error)
+    return NextResponse.json(
+      { success: false, error: 'Failed to discover MCP servers' },
+      { status: 500 }
+    )
+  }
+}