You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+37-8Lines changed: 37 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,36 +150,58 @@ Executes code in YepCode's secure environment.
150
150
151
151
YepCode MCP server supports the following options:
152
152
153
-
- Disable the run_code tool: In some cases, you may want to disable the `run_code` tool. For example, if you want to use the MCP server as a provider only for the existing tools in your YepCode account.
154
-
- Skip the run_code cleanup: By default, run_code processes source code is removed after execution. If you want to keep it for audit purposes, you can use this option.
153
+
-`runCodeCleanup`: Skip the run_code cleanup. By default, run_code processes source code is removed after execution. If you want to keep it for audit purposes, you can use this option.
155
154
156
-
Options can be passed as a comma-separated list in the `YEPCODE_MCP_OPTIONS` environment variable or as a query parameter in the MCP server URL.
155
+
Options can be passed as a comma-separated list in the `YEPCODE_MCP_OPTIONS` environment variable.
156
+
157
+
##### Tool Selection
158
+
159
+
You can control which tools are enabled by setting the `YEPCODE_MCP_TOOLS` environment variable with a comma-separated list of tool categories and process tags:
-`YEPCODE_MCP_TOOLS=run_code,storage` - Only enables built-in code execution and storage tools
202
+
-`YEPCODE_MCP_TOOLS=core,automation` - Only exposes processes tagged with "core" or "automation" as tools
203
+
-`YEPCODE_MCP_TOOLS=run_code,storage,core` - Enables built-in tools plus all processes tagged with "core"
204
+
183
205
### Environment Management
184
206
185
207
#### set_env_var
@@ -288,10 +310,17 @@ Deletes a file from YepCode storage.
288
310
289
311
### Process Execution
290
312
291
-
The MCP server can expose your YepCode Processes as individual MCP tools, making them directly accessible to AI assistants. This feature is enabled by just adding the `mcp-tool` tag to your process (see our docs to learn more about [process tags](https://yepcode.io/docs/processes/tags)).
313
+
The MCP server can expose your YepCode Processes as individual MCP tools, making them directly accessible to AI assistants. This feature is enabled by specifying process tags in the `YEPCODE_MCP_TOOLS` environment variable.
314
+
315
+
**How it works:**
316
+
1. Tag your YepCode processes with any tag (e.g., `core`, `api`, `automation`, `mcp-tool`, etc.)
317
+
2. Add those tags to the `YEPCODE_MCP_TOOLS` environment variable
318
+
3. All processes with the specified tags will be exposed as individual MCP tools
292
319
293
320
There will be a tool for each exposed process: `run_ycp_<process_slug>` (or `run_ycp_<process_id>` if tool name is longer than 60 characters).
294
321
322
+
For more information about process tags, see our [process tags documentation](https://yepcode.io/docs/processes/tags).
0 commit comments