Liatir

Appearance

Local MCP ​

Local MCP lets an MCP-compatible client ask Liatir to run a pipeline you have already saved. Liatir keeps control of the scientific workflow: the client can request a run, but you must approve that request in the app before anything starts.

The server is local to your computer, off by default, and is not required for using Liatir normally.

Connect a client ​

  1. Build and save the pipeline you want to reuse.
  2. Open Settings → Local MCP.
  3. Select Turn on.
  4. Select Allow beside the saved pipeline.
  5. Copy the current Server URL and Bearer token into your MCP client.

Configure the client to use Streamable HTTP and send the token as:

text
Authorization: Bearer <token copied from Liatir>

The server URL uses a local address such as http://127.0.0.1:49152/mcp. Its port can change when Liatir restarts, so copy the current URL again after restarting the app. Liatir must remain open while a client is connected.

Treat the bearer token like a password. Rotate token immediately disconnects clients that still use the old token.

What a client can do ​

The first Liatir MCP surface exposes exactly two tools:

  • start_saved_pipeline requests one allowed saved pipeline by pipeline_id;
  • cancel_pipeline_run requests cancellation of one run that was started through MCP, by its stable run_id.

A start request returns its run ID immediately with awaiting-authorization. Liatir then shows a dialog with the client, workspace, pipeline and run identity. Approving it starts that exact saved revision; denying it creates no pipeline execution, Job or Result.

An approved run follows the normal Liatir lifecycle. Its work appears in Jobs, and its terminal outcome appears in Results with MCP initiator and run identity. A client reads progress separately through these resources:

  • liatir://workspace/active — active workspace identity;
  • liatir://workspace/active/pipelines — currently allowed pipeline revisions;
  • liatir://runs — MCP-owned runs in the active workspace;
  • liatir://runs/{run_id}/status;
  • liatir://runs/{run_id}/logs;
  • liatir://runs/{run_id}/result.

Safety boundary ​

Allowing a pipeline applies only to its exact saved revision. Editing and saving the pipeline makes the grant stale; return to Settings and review the new revision before allowing it again.

An MCP client cannot:

  • change pipeline inputs or parameters;
  • edit or construct a pipeline;
  • choose scientific preprocessing or model settings;
  • run arbitrary shell commands;
  • browse arbitrary files or other workspace state;
  • cancel work that was not started through MCP.

The saved pipeline itself still has the capabilities you configured in Liatir. For example, it may contain an API Connector, External Workflow, heavy AI Model or other step that uses the network or local dependencies. Review the complete saved pipeline before allowing it.

Every authenticated tool request is recorded in the local MCP audit log, whether it succeeds or is rejected. Successful resource listings and reads are recorded too. The most recent security activity is visible in Settings → Local MCP. Turning the server off rejects new requests and any request still waiting for approval; it does not silently stop a run you already approved. Cancel that run explicitly from Liatir or the MCP client.

Troubleshooting ​

The client reports unauthorized ​

Copy the bearer token again, including no spaces before or after it. If the token was rotated, replace the old value in the client.

The client cannot connect ​

Confirm that Liatir is open and Local MCP says Ready for local clients. Copy the current Server URL again after every Liatir restart. The endpoint is loopback-only and cannot be used from another computer.

A pipeline is not listed or the request says it is not allowed ​

Save the pipeline, then allow it in Settings → Local MCP. If it says Changed since it was allowed, review it and select Allow new revision. Only pipelines in the active workspace are exposed.

A request is waiting ​

Bring Liatir to the foreground and approve or deny the authorization dialog. The client identity shown there is self-reported metadata; base your decision on the pipeline, workspace and request you expected, not the client name alone.

Liatir implements MCP protocol revision 2026-07-28 over local Streamable HTTP.