feat(library): How to Turn a Workflow Into a Reusable MCP Tool (Sim vs n8n, Gumloop, and Zapier) - #6687
Conversation
…s n8n, Gumloop, and Zapier)
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryLow Risk Overview The piece includes frontmatter (FAQ, tags, canonical URL, Reviewed by Cursor Bugbot for commit adefc92. Configure here. |
Greptile SummaryAdds 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.
Confidence Score: 4/5The 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
|
| 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
| - q: "Can Claude or another assistant call a Sim workflow?" | ||
| a: "Yes, when the assistant supports MCP connections. Sim provides connection configurations for Claude Desktop, Cursor, VS Code, and Claude Code, while other compatible clients can use the same server details." | ||
| - q: "How is a published Sim MCP server authenticated?" | ||
| a: "A Sim MCP server can use API Key access, where clients send an X-API-Key header containing a Sim API key, or Public access without authentication. Tool calls run the live deployment and consume workspace credits like other executions." |
There was a problem hiding this comment.
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!
Summary
Type of Change
Testing
Validated frontmatter/author against the Zod schema and MDX compile (remark-gfm) locally. Tested manually.
Checklist