feat(library): How to Turn a Workflow Into a Reusable MCP Tool (Sim vs n8n, Gumloop, and Zapier)

[icecrasher321]

Summary

• Adds the How to Turn a Workflow Into a Reusable MCP Tool (Sim vs n8n, Gumloop, and Zapier)

Type of Change

• New content

Testing

Validated frontmatter/author against the Zod schema and MDX compile (remark-gfm) locally. Tested manually.

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		Aug 14, 2026 12:22am

[cursor]

PR Summary

Low Risk
Documentation-only addition with no application, API, or auth changes.

Overview
Adds a new library article at how-to-turn-a-workflow-into-a-reusable-mcp-tool/index.mdx explaining how to publish a Sim workflow as a reusable MCP tool and when that model differs from REST API deployment.

The piece includes frontmatter (FAQ, tags, canonical URL, ogImage path), a TL;DR and step-by-step Sim MCP publishing flow, sections on MCP vs API and agentic reuse, and competitive coverage of n8n, Gumloop, and Zapier (including when n8n’s MCP Server Trigger fits better). It closes with a comparison table and a get-started CTA linking to Sim MCP deployment docs.

^{Reviewed by Cursor Bugbot for commit adefc92. Configure here.}

[greptile-apps]

Greptile Summary

Adds a new library article explaining how to publish a Sim workflow as an MCP tool and comparing Sim’s model with n8n, Gumloop, and Zapier.

• Documents workflow deployment, MCP server setup, authentication, client connection, and versioning.
• Adds comparison guidance, FAQs, internal references, and a dedicated cover image.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking documentation gap around which API keys private MCP servers authorize.

The article and asset integrate with the existing library structure, but readers can still receive an unexplained authorization failure because the setup guidance does not mention workspace scope or personal-key policy.

Files Needing Attention: apps/sim/content/library/how-to-turn-a-workflow-into-a-reusable-mcp-tool/index.mdx

Important Files Changed

Filename	Overview
apps/sim/content/library/how-to-turn-a-workflow-into-a-reusable-mcp-tool/index.mdx	Adds the complete article and valid content metadata; its private-server authentication guidance omits enforced key-scope restrictions.
apps/sim/public/library/how-to-turn-a-workflow-into-a-reusable-mcp-tool/cover.jpg	Adds the cover asset at the exact public path referenced by the article metadata.

_{Reviews (1): Last reviewed commit: "feat(library): How to Turn a Workflow In..." | Re-trigger Greptile}

[greptile-apps]

Clarify API key restrictions

The article describes any Sim API key as sufficient, but private MCP servers also enforce workspace scope and personal-key policy. Readers using a key from another workspace or a disallowed personal key receive a 403 without enough guidance to select an authorized key.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!