MCP for programs
A program can give a run extra tools and resources by passing MCP servers to it. This page covers the options a script uses. The server formats, scopes and sign-in steps are on the MCP guide.
The Syntic Code SDK packages are not released yet. The options on this page are the ones the syntic command supports today.
Pass servers for one run
--mcp-config adds servers for this run only. It takes a file or inline JSON, and you can repeat it:
syntic -p "check the staging database for failed migrations" --mcp-config db-server.jsonAdd --strict-mcp-config to use only the servers you passed and ignore everything set up in settings or plugins. For a fully repeatable run, --bare also skips settings hooks, plugins, skills and memory, and loads only the servers from --mcp-config:
syntic -p "review this diff" --bare --mcp-config review-tools.jsonIf a server in --mcp-config has the same name as one in your settings, the one from --mcp-config is used.
Slow servers
By default a print run waits for its MCP servers before the first request. Set MCP_CONNECTION_NONBLOCKING=true so the run gives every server a short window instead (5 seconds, changed with MCP_CONNECT_TIMEOUT_MS): servers ready in time bring their tools, and the rest are left out of that run. Passing only the servers a script needs also keeps a slow one from holding up the run.
Transports
A server can run as a local program over standard input and output, or as a remote server over HTTP or server-sent events. The transport is picked from the config. Remote servers that need sign-in use OAuth, and the sign-in happens in a browser the first time. A run that is not attended cannot complete a sign-in, so complete it once beforehand with syntic mcp login <name> (--no-browser prints the sign-in URL instead of opening a browser). syntic mcp list shows which servers are connected and which need sign-in.
Permissions and scope
Each server’s tools go through the same permission rules as built-in tools, so --allowed-tools and --disallowed-tools apply to them too. An administrator can limit which servers may be used with the managed allow and deny lists described on managed MCP settings.
Subagents can use their own MCP servers, set in the agent definition, so a server does not have to be shared with the main run.
Limits to plan for
- A server’s request for information from the person (MCP elicitation) is cancelled in a plain
-prun. In a stream-json run, it is passed to the driving program as anelicitationrequest, which answers withaccept,declineorcancel. - When the tool list is large, only the core tools are sent in full and the rest are loaded on demand through
ToolSearch. Passing only the servers a run needs still keeps requests small. See Tool search. - A server’s instructions are added to the system prompt, so a verbose server adds to every run.
Run Syntic Code as a server
The reverse also works. syntic mcp serve exposes Syntic Code’s own tools to another MCP client, so another agent can use them. See Run Syntic Code as an MCP server.