Configuration
Processes as tools
Section titled “Processes as tools”The MCP server can expose your Factorial Code processes as individual MCP tools. Each process becomes a callable tool that AI assistants can invoke.
Default tag: mcp-tool
Section titled “Default tag: mcp-tool”Tag a process with mcp-tool and it is automatically exposed as an MCP tool. No configuration needed.
Custom tags
Section titled “Custom tags”For custom tags, add them to the tools query param so the MCP server discovers those processes:
- Tag your process (e.g.
core,automation) - Include that tag in the
toolsquery param (see below) - The process appears as a tool named after its slug (or
fc_<processId>if the slug is longer than 60 characters)
Input schema and execution
Section titled “Input schema and execution”- Each process tool accepts parameters according to the process input schema (JSON Schema). Define a proper schema for better AI behavior.
- Sync (default): waits for completion, returns
executionId,logs,returnValue,error - Async: pass
synchronousExecution: falseto getexecutionIdimmediately
Common issues: No process tools with custom tags? Add those tags to the tools query param. Tool not found? Ensure tag spelling matches. See Process tags for how to add and manage tags.
Tool selection and options
Section titled “Tool selection and options”The hosted endpoint is configured through URL query params on the connection URL:
https://code.factorialhr.com/mcp?tools=run_code,fc_api,core&mcpOptions=runCodeCleanupAuthenticate with the Authorization header (never the URL) — see the Quickstart for how to pass your API token.
CSV of tool categories and custom process tags. When omitted, built-ins are on and mcp-tool processes are auto-exposed; custom tags must be listed explicitly.
- Built-in categories:
run_code,fc_api,fc_api_full - Individual tools: e.g.
execute_process_sync,get_execution - Custom process tags: e.g.
core,automation— add tags to expose those processes (processes taggedmcp-toolare always exposed; see “Processes as tools” above)
mcpOptions
Section titled “mcpOptions”CSV of MCP options.
| Option | Default | Effect |
|---|---|---|
runCodeCleanup | on | Keeps run_code source for audit when enabled |
skipCodingRules | off | Omits coding rules from run_code schema (smaller defs, less AI guidance) |
Examples
Section titled “Examples”Tool selection — enable run_code, basic API, and processes tagged core:
https://code.factorialhr.com/mcp?tools=run_code,fc_api,coreOptions — keep run_code source for audit and skip coding rules in the tool schema:
https://code.factorialhr.com/mcp?mcpOptions=runCodeCleanup,skipCodingRulesBoth — combine tool selection and options:
https://code.factorialhr.com/mcp?tools=run_code,fc_api,core&mcpOptions=runCodeCleanup,skipCodingRules