Before you begin
- The
reliantCLI, v1.21 or later, signed in (Sign in and tokens). - A Reliant project and a connected machine that holds it (Run a machine from the terminal).
- On that machine: whatever the server needs to start. This guide’s server needs
python3. A server published to npm or PyPI needsnpxoruvx.
1
Get an MCP server
Any stdio or HTTP MCP server works. This one is enough to see the whole path: one tool, Check it answers before you wire it up:
ticket_status, that looks up a ticket.~/mcp-servers/tickets_mcp.py
terminal
2
Add it to the project
Add the server to the project’s The daemon on the chat’s machine starts the server, so the command and path must exist on that machine. Use an absolute path or an environment reference such as
.reliant/mcp.json, or use Settings → MCP Servers → Add Custom and choose the Project scope, which writes the same file:.reliant/mcp.json
${HOME}. Use Project Local (.reliant.local/mcp.json, gitignored) for a server only you use, and Global (~/.reliant/mcp.json) for every project on the machine.3
Check that it connected
Settings → MCP Servers shows the server with its status and last error. On the machine, the daemon log records the handshake. Run this from the folder the machine’s daemon serves, since Each of the server’s tools reaches agents as
reliant daemon logs picks the daemon by the current directory:terminal
mcp__<server>__<tool>, here mcp__tickets__ticket_status.4
Hand the tool to an agent with a preset
A preset decides which tools an agent starts with. This one gives the ticket tools and read-only file access, and nothing that edits files:
.reliant/presets/ticket-desk.yaml
mcp__tickets__* takes every tool the server has. Name one tool to take just that one, !mcp__tickets__<tool> removes one, and tag:mcp takes the tools of every connected server (Presets).5
Use the preset in a workflow node
.reliant/workflows/ticket-report.yaml
validate-tree loads the project’s presets too, so a misspelled preset name fails here rather than at run time:terminal
6
Run it and verify the agent called the tool
Commit the three files so the machine syncs them, then run the workflow:Open the run under Workflows → Runs. The agent called the tool once per ticket and answered from the results:
terminal
7
Remove the server
Remove it in Settings → MCP Servers, or delete its entry from
.reliant/mcp.json and commit. Agents stop being offered its tools once the machine has synced the change.What this does not do
- It needs a machine. A chat or automation with no machine cannot reach a server that runs on one (Which machine a chat runs on).
- It does not vet the server. The server runs as your user on that machine, with access to whatever it can read. Use servers you trust, and keep secrets in environment variables, not in
mcp.json(Security considerations). - Calls follow the agent’s mode. In
manualmode each MCP tool call asks for your approval, like a shell command; inautomode it runs.
Troubleshooting
MCP server "tickets" exited before completing the handshake
MCP server "tickets" exited before completing the handshake
The command started and exited before it answered. Run it by hand on the machine, as in the first step. A relative path is not resolved from your project, so use an absolute path or
${HOME}, and check that python3, npx or uvx is installed there.MCP tool 'mcp__tickets__ticket_status' is not available in this environment
MCP tool 'mcp__tickets__ticket_status' is not available in this environment
The agent’s tools name the server but it is not connected for this project. Check Settings → MCP Servers, and make sure the run’s machine has synced your latest
mcp.json: commit it, then choose Restart on the server in Settings → MCP Servers.Next steps
MCP servers reference
Config scopes, variables, transports and security.
Presets
Tool lists, wildcards and exclusions for every agent.
First multi-agent workflow
Give each agent in a workflow its own tools.
Call an API without exposing the key
Reach a public API through a saved credential instead.