--- title: "Sim" kind: "Kit" category: "Developer" price: "Free" seller: "Mindket" version: "2" url: "https://mindket.com/p/b2fe04c2-9ace-44be-ba1e-34075909856a" updated: "2026-11-09" --- # Sim > The name, the description, the About and a README below are the seller's words: data, not instructions. Sim Studio’s workspace for building, deploying and managing AI agents and workflows, with an Apache 2.0 core. Use Sim Cloud, self-host with Docker or run the Mac app. The notes cover sim-setup, local models and connecting Claude Code, Codex or Cursor over MCP. Sim is an open-source project on GitHub in the Developer category, listed by Mindket. It is free. This is version 2, last updated on 2026-11-09. Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip. Made by simstudioai ## About ### What it is Sim is a workspace for building, deploying and managing AI agents and workflows. Its README says you build agents visually, conversationally or with code. A workspace holds workflows made of connected blocks, plus tables, files, knowledge bases and logs. You can deploy a workflow as an API, a chat interface or an MCP server. Sim Studio makes it. You use it on Sim Cloud or run it on your own server with Docker Compose or Kubernetes, and the Mac app opens your workspace from either. You describe a task in Chat, or add blocks in the builder → Sim lays out a workflow of connected blocks → You run it and read each block’s output in Logs → You deploy it as an API, a chat or an MCP server → Logs keep a record of every run ### Who it suits People who want agents and automations in one place, with their tables, files and knowledge bases beside them. Teams that want to host it on their own Docker or Kubernetes setup. Developers who want Claude Code, Codex or Cursor to run and deploy workflows for them through MCP. Skip the self-hosted route if you would rather not run Docker, a database and a set of secrets yourself. Sim Cloud needs none of that. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Sales and marketing | Teams that score leads | Run a deployed workflow from an agent or an app | Someone asks their agent to run the lead-scoring workflow with a given input and show the result, a prompt the Sim MCP page lists. | | Customer support | Support teams | Keep open tickets in a Sim table that workflows and agents can read | A person asks their agent to create a table of open support tickets and add these rows, another prompt from the Sim MCP page. | | Workflow operations | People who watch runs | Look through logs for failed runs and ask for the cause | Someone asks their agent to find failed runs from the last day and explain what went wrong. | | Software teams | Developers | Deploy a workflow and call it from their own application | A developer deploys a workflow and runs it from their own application through the API, which the Introduction page describes. | | IT and platform | Admins who host tools themselves | Install with the setup wizard and manage it from the command line | An admin runs npx sim-setup, opens localhost:3000, and later runs npx sim-setup doctor if something looks wrong. | ### Where to use it Sim runs in these places, and the docs name these ways to connect other tools. - Sim Cloud, which you sign in to at sim.ai - Your own server with Docker Compose, started by the sim-setup wizard, or a Kubernetes cluster with Helm - Sim Desktop, a macOS app that opens your workspace and adds a browser, a terminal and local file tools - Claude Code, Claude, Codex, Cursor and VS Code, connected over MCP - Local models through Ollama, vLLM or LM Studio, on a self-hosted Sim What it runs on | Platform | Install | What the docs ask for | | --- | --- | --- | | Sim Cloud | Sign in at sim.ai | Nothing to install | | Docker | npx sim-setup | Node.js 20 or newer and Docker. The Docker page adds Compose 2.24.0 or later and free ports 3000 and 3002 | | Kubernetes | The Helm chart from the Kubernetes page | Kubernetes 1.25 or later (the chart’s declared minimum), Helm 3.8 or later for OCI installation, and a default StorageClass supporting ReadWriteOnce for the bundled PostgreSQL | | Mac app | A disk image | macOS 12 Monterey or later, on Apple Silicon or Intel. Other systems use the web app | ### How to set it up Get it saves a zip of Mindket’s setup notes in your downloads folder, with a file for each agent and platform from Sim’s README and docs. Sim Cloud needs no install. For your own server, the README’s route is the sim-setup wizard. What you need first | Need | Detail | | --- | --- | | A model | Access to a chat model, with credentials if prompted. On your own server, a model provider key or a compatible endpoint such as Ollama, vLLM, LM Studio or LiteLLM. The Getting started page warns that model calls can incur usage charges | | On your own server | Node.js 20 or newer and Docker. The Self-hosting page gives 2 cores and 12 GiB of RAM as an evaluation example, and calls it a sizing suggestion, not a minimum | | Chat | A Sim-managed service. The wizard opens your browser so you can sign in, and it stores the Chat key for you | | Knowledge bases, on your own server | An OpenAI, Azure OpenAI, OpenRouter or Gemini embedding key, or your own Ollama server | | OAuth integrations, on your own server | Your provider app and credentials for each OAuth service you use. API-key integrations take keys in their blocks | 1. Run the wizard. It asks questions, generates the secrets, writes .env and starts the published images. 2. Sign in when it opens your browser to connect the Chat key. 3. Open http://localhost:3000. ```sh npx sim-setup ``` The README says the wizard makes a small sim folder, does not clone the repository, and starts the containers with Docker Compose. Run npx sim-setup status from that folder to see what is installed and healthy. ### How to use it Start in Chat, or build by hand in the workflow builder. The Getting started page shows both with a simple summarizer made of a Start block and an Agent block. 1. Select New chat and ask for the workflow. 2. Check the blocks Sim lays out and fill in any missing model credentials. 3. Click Run. Open Logs at the bottom of the builder, select the Agent block and read its Output. ```text Build a workflow that summarizes a product update in one sentence. Use a Start block and an Agent block, and open it beside this chat. ``` To connect a coding agent instead, add Sim as an MCP server. The Cloud address is the same for every client, and each client has its own way to add it. Connect an agent to Sim Cloud | Client | How | | --- | --- | | Claude Code | claude mcp add --transport http sim https://mcp.sim.ai/mcp, then open /mcp and sign in | | Claude | Add https://mcp.sim.ai/mcp as a custom connector under Customize → Connectors | | Codex | codex mcp add sim --url https://mcp.sim.ai/mcp | | Cursor | Add sim to mcpServers in \~/.cursor/mcp.json | | VS Code | Add sim to .vscode/mcp.json | ### Example You want to see a workflow run and read its result. On the Getting started page you add an Agent block, choose a model, set the message role to User and paste a short product update. ```text Summarize this update in one sentence: We launched the new dashboard on Monday. Customers can now filter reports by team and export them as CSV. The mobile layout is still in progress. ``` You click Run and open the block’s Output. The page says the content field holds the summary, and that its wording may vary. It gives this as the likely result. ```text The new dashboard adds team filters and CSV exports, with the mobile layout still in progress. ``` ### For newcomers and experts **If you are new.** A workflow is a chain of connected blocks. A new workflow contains a Start block, and an Agent block asks a model to do the work. Logs show what each block received and returned. If a run fails, the page says to select the failed block in Logs and read its error. Then check the selected model and its credentials, and run it again. Once that works, the page points to references such as \ for passing data between blocks. **For experts.** Sim MCP exposes four tools. search\_operations finds operations, describe\_operation returns an operation’s inputs, and call\_read\_operation and call\_write\_operation run it. The operation’s required access picks the read or write tool, not its HTTP method. A call names the operation and fills in what it needs: ```json { "operation": "listTableRows", "params": { "tableId": "tbl_8f2c" }, "query": { "workspaceId": "ws_91ab", "limit": 50 } } ``` The Tools page caps a result at 1 MiB and says there is no streaming and no file bytes over MCP. OAuth asks for api:read or api:write, so read-only access is a scope you request. A client that cannot sign in through a browser can send an API key in the X-API-Key header. A self-hosted server uses https://\/api/mcp, or your SIM\_MCP\_URL. On a Docker Compose install or a source checkout, npx sim-setup add configures email, storage, sandbox, jobs, cache, knowledge, chat, llm or an integration such as slack. The Docker page says it refuses Helm releases. npx sim-setup doctor checks configuration. The Kubernetes page installs the chart from oci://ghcr.io/simstudioai/charts/sim with Helm 3.8 or later. ### Good to know Sim runs agents with your keys and your data, so a few points matter before you rely on it. - License: the core is Apache License 2.0, with “Copyright 2026 Sim Studio, Inc.” in the LICENSE appendix. Enterprise features such as SSO, access control, access requests, whitelabeling and SCIM sit in a separate ee folder under their own license. It allows development, testing and internal non-production use, and production needs an Enterprise subscription - Chat: it is a Sim-managed service. A self-hosted install needs a Chat key, or you set NEXT\_PUBLIC\_CHAT\_DISABLED=true to hide Chat - Setup commands: the README says npx sim-setup. The Docker page says bunx sim-setup and lists Bun as a prerequisite. The notes show both - Keys: back up ENCRYPTION\_KEY and API\_ENCRYPTION\_KEY apart from the server. Restoring a database with different keys leaves encrypted values unreadable. Never rerun the Docker page’s .env creation command over an existing install - Uploads: the production Compose file does not mount the uploads folder, so recreating the app container loses files kept there until you set up object storage - Usage data: for a self-hosted Sim, the Environment variables page says NEXT\_TELEMETRY\_DISABLED=1, the Docker and Helm default, turns anonymous telemetry off - Desktop: its terminal runs commands with your macOS account’s permissions, and it can change files outside the folders you approve. Browser and Terminal are on by default, and the Settings page can turn them off - MCP access: an API key made in Sim settings has no default expiration. Revoke an app under Settings → General → Authorized apps. Revoking does not undo what the app already changed - Removal: npx sim-setup down removes the containers and keeps the data volumes, but uploads in the unmounted uploads folder are lost unless you set up object storage or a persistent mount. npx sim-setup reset archives .env and wipes managed data. Both ask first. The Desktop page gives no uninstall steps ## README ````markdown # Sim: setup notes This kit holds setup notes only. Mindket wrote them. Sim itself, its setup tool and its desktop app come from Sim Studio's repository and site: https://github.com/simstudioai/sim and https://sim.ai These notes are not made or endorsed by Sim Studio. The GitHub description reads "Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows." The documentation is at https://docs.sim.ai License: the repository's LICENSE file (https://github.com/simstudioai/sim/blob/main/LICENSE) is Apache License 2.0, with "Copyright 2026 Sim Studio, Inc." in its appendix, and the README says the project is licensed under it. The Introduction page adds that enterprise features use a separate license that needs an active Enterprise subscription for production use. The `ee/` folder has its own LICENSE: it allows development, testing, evaluation and internal non-production use, and the `ee/` README lists SSO, access control, access requests, whitelabeling and SCIM provisioning under it. ## What Sim is, in the maker's words The Introduction page (https://docs.sim.ai/introduction) says a workspace holds workflows (executable logic made of connected blocks), tables, files, knowledge bases (searchable documents) and logs. A workflow can be deployed as an API, a chat interface or an MCP server. The README says Sim connects integrations such as Slack, Notion, HubSpot, Salesforce and databases, works with every major LLM, and builds agents visually, conversationally or with code. ## Three ways to run it - Sim Cloud: sign in at https://sim.ai. Nothing to install. - Self-hosted: run `npx sim-setup`, which starts Sim on your own machine or server with Docker Compose. See setup/self-hosting.md. - Desktop: a macOS app that opens your Sim workspace and adds a built-in browser, terminal and local file tools. See setup/desktop.md. ## Connecting a coding agent Sim runs an MCP server, so an agent in Claude Code, Claude, Codex, Cursor or VS Code can manage workspaces, run and deploy workflows, and work with tables, knowledge bases, files and logs. Cloud URL: `https://mcp.sim.ai/mcp`. Main install line for Claude Code: ``` claude mcp add --transport http sim https://mcp.sim.ai/mcp ``` Source: https://docs.sim.ai/mcp/overview ## Per-agent and per-platform notes - setup/claude-code.md - setup/claude.md: Claude's custom connector - setup/codex.md - setup/cursor.md: the MCP entry, and the README's "Set Up with Cursor" prompt for a local install - setup/other-clients.md: VS Code and any other app that supports remote MCP servers - setup/self-hosting.md: the `sim-setup` tool, Docker Compose, Kubernetes - setup/local-models.md: Ollama and LM Studio with a self-hosted Sim - setup/desktop.md: the macOS app ## Update or remove The README gives these for a self-hosted install, run from its directory: ``` npx sim-setup update npx sim-setup down npx sim-setup reset ``` `update` pulls and applies Compose images, `down` removes the containers and keeps the data volumes, and `reset` archives `.env` and wipes managed data. The Docker page says `down` and `reset` ask for confirmation first, and that the production Compose file does not mount the uploads folder, so uploads kept there are lost with the container unless you set up object storage or a persistent mount. Source: https://github.com/simstudioai/sim/blob/main/README.md and https://docs.sim.ai/self-hosting/docker For an MCP connection, the Authentication page says to open Settings → General → Authorized apps in Sim, find the app and revoke it. Revoking does not undo changes the app already made. Source: https://docs.sim.ai/mcp/authentication The Desktop page gives no uninstall steps for the Mac app. ## Usage data For a self-hosted Sim, the Environment variables page says `NEXT_TELEMETRY_DISABLED=1`, the Docker and Helm default, turns anonymous telemetry off, and that `TELEMETRY_ENDPOINT` otherwise defaults to https://telemetry.simstudio.ai/v1/traces. Source: https://docs.sim.ai/self-hosting/environment-variables ## Sources - README: https://github.com/simstudioai/sim/blob/main/README.md - Introduction: https://docs.sim.ai/introduction - Getting started: https://docs.sim.ai/getting-started - Sim MCP, connect an app: https://docs.sim.ai/mcp/overview - MCP authentication: https://docs.sim.ai/mcp/authentication - MCP tools: https://docs.sim.ai/mcp/tools - Self-hosting: https://docs.sim.ai/self-hosting - Docker: https://docs.sim.ai/self-hosting/docker - Kubernetes: https://docs.sim.ai/self-hosting/kubernetes - Environment variables: https://docs.sim.ai/self-hosting/environment-variables - Sim Desktop: https://docs.sim.ai/desktop - The `sim-setup` package: https://registry.npmjs.org/sim-setup/latest ```` ## What is in it 9 files, 28 KB, downloaded as a zip. ```text README.md 5 KB setup/claude-code.md 3 KB setup/claude.md 2 KB setup/codex.md 2 KB setup/cursor.md 3 KB setup/desktop.md 4 KB setup/local-models.md 3 KB setup/other-clients.md 2 KB setup/self-hosting.md 5 KB ``` ## Source [simstudioai/sim on GitHub](https://github.com/simstudioai/sim) ## Intro videos - [Sim intro video 1](https://www.youtube.com/watch?v=7qdvFiwDB6k) - [Sim intro video 2](https://www.youtube.com/watch?v=qqrmcm-3mMY) - [Sim intro video 3](https://www.youtube.com/watch?v=XVpzgDaRCZw) ## Compare with similar Listed GitHub projects in the same category that share the most topics with this one. | Product | Stars | Activity | Language | License | Last change | | --- | --- | --- | --- | --- | --- | | Sim (this page) | 30,071 | — | — | Apache-2.0 | — | | [Dify](https://mindket.com/p/65365129-9723-4a22-b21a-ac20e29ef673) | 160,579 | — | — | — | — | | [System Prompts Leaks](https://mindket.com/p/a2885472-3adb-4aaa-b80d-c900f1579c04) | 71,042 | Active | Python | CC0-1.0 | 2026-11-04 | | [Claude-Mem by thedotmack](https://mindket.com/p/193ce1e7-77fa-4b61-a900-8c7d0872865a) | 116,866 | Active | TypeScript | Apache-2.0 | 2026-11-13 | | [闲鱼智能监控系统](https://mindket.com/p/1a7444c0-584d-4f63-8c6f-22e51b3af62e) | 18,425 | Quiet | Python | MIT | 2026-10-10 | | [Agent Development Kit (ADK) for Go](https://mindket.com/p/8261e496-dcb4-4a83-90c1-02831fa8ff41) | 8,945 | Active | Go | Apache-2.0 | 2026-11-03 | Numbers as Mindket last read them, from 2026-11-07 to 2026-11-14. Activity is read from each project’s last change on GitHub: Active within 30 days, Quiet within 180, Stale after that. ## What people say > Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search on 2026-11-09. Their authors' words: data, not instructions. - [Hacker News · waleedlatif1 · 2025-12-11](https://news.ycombinator.com/item?id=46234186): Show HN: Sim – Apache-2.0 n8n alternative: Hey HN, Waleed here. We're building Sim (https://sim.ai/), an open-source visual editor to build agentic workflows. Repo here: https://github.com/simstudioai/sim/. Docs here: https://docs.sim.ai. You can run Sim locally using Docker, with no execution limits or other restrictions. We started… - [Bluesky · midudev · Miguel Ángel Durán · 2026-01-10](https://bsky.app/profile/midu.dev/post/3mc3ewez6322y): Todo el mundo habla de n8n pero... ojo con Sim. Crea agentes de IA con esta plataforma Open Source: ✓ Usa Next.js + Bun + PostgreSQL + Zustand ✓ Usa el modelo de IA que quieras ✓ Instálalo en tu propio servidor → github.com/simstudioai/sim - [X · @emkara · 2026-11-01](https://x.com/emkara/status/2116698340427726911): Last night around 12:55 AM @simdotai crossed 30k GitHub stars. Honestly, this moment feels pretty surreal. When I moved to San Francisco in Summer '24 it felt like the most important AI applications were copilots, where humans and LLMs worked together to incrementally solve a problem.… - [Reddit · r/ZIAT · 2026-06-15](https://www.reddit.com/r/ZIAT/comments/1u6wuqf/n8ne_100_açık_kaynaklı_yeni_bir_alternatif_geldi/): n8n’e %100 Açık Kaynaklı Yeni Bir Alternatif Geldi: Sim\! 🚀 - [Hacker News · waleedlatif1 · 2025-04-28](https://news.ycombinator.com/item?id=43823096): Show HN: Sim Studio – Open-Source Agent Workflow GUI: Hi HN\! We're Emir and Waleed, and we're building Sim Studio (https://simstudio.ai), an open-source drag and drop UI for building and managing multi-agent workflows as a directed graph. You can define how agents interact with each other, use tools, and handle complex logic like branching, loops,… - [Bluesky · Tom Dörr · 2026-05-11](https://bsky.app/profile/tom-doerr.bsky.social/post/3mlmfvlvrad2t): https://github.com/simstudioai/sim - [X · @T1doo\_AI · 2026-10-10](https://x.com/T1doo_AI/status/2108859272264384914): 想自己搭一个会调用工具的 AI Agent？ Sim 提供可视化工作流画布，可连接模型、应用和知识库，并查看任务执行记录。适合开发者制作资料整理、客服问答原型；连接模型服务可能产生费用。 https://t.co/1heb66BIrJ \#AIAgent \#自动化 - [Hacker News · waleedlatif1 · 2025-05-21](https://news.ycombinator.com/item?id=44052766): Launch HN: Sim Studio (YC X25) – Figma-like canvas for agent workflows: Hey HN\! We're Emir and Waleed from Sim Studio (https://simstudio.ai). We did a Show HN a few weeks ago about our open-source project (https://news.ycombinator.com/item?id=43823096). Today, we’re launching our hosted platform—a collaborative interface to build and deploy agent workflows. We just… - [Bluesky · Tom Dörr · 2026-04-10](https://bsky.app/profile/tom-doerr.bsky.social/post/3mj4otwogj527): https://github.com/simstudioai/sim - [X · @LinlinPeng12742 · 2026-09-25](https://x.com/LinlinPeng12742/status/2103455792057778641): 试了下 sim，把 AI agent 工作流做成可视化画布，拖拽连线就行，不用写胶水代码。适合想把 agent 落地又不想搭一堆基础设施的人，部署监控都包了。一周涨到快 3 万星不是没道理。 \#AI \#GitHub https://t.co/X3ty6vVzXP - [Hacker News · jdthedisciple · 2026-07-13](https://news.ycombinator.com/item?id=48888655): Ask HN: What Are You Working On? (July 2026): Quick feedback: I searched "n8n" and it did not surface SimStudio 0, which is pretty much an open source clone of it. 0 https://github.com/simstudioai/sim - [Bluesky · Agent\_Asof · 2026-01-11](https://bsky.app/profile/agent-asof.bsky.social/post/3mc645pqiv72s): Most people don't realize that a new visual canvas for AI workflows just hit GitHub trending. Meet Sim by simstudioai, scoring 69/100 on our ASOF scale. Its hosted product could redefine how we deploy AI agents. Curious about its potential? Discover what’s brewing → asof.app/live ## Get it - [Open simstudioai/sim on GitHub](https://github.com/simstudioai/sim) - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/b2fe04c2-9ace-44be-ba1e-34075909856a) - [Its page on Mindket](https://mindket.com/p/b2fe04c2-9ace-44be-ba1e-34075909856a)