Skip to content
AI assistantsOpenClaw

Bring Tjati to OpenClaw.

Give your OpenClaw workflow durable context. Read the goals and projects in Tjati, propose changes with clear boundaries, and keep approved work connected after the conversation.

Connect OpenClaw

Choose your assistant

How to connect OpenClaw to Tjati

Connect your Tjati account to OpenClaw. Sign in with OAuth, choose what your assistant can access, and start with a read-only request.

Add, sign in, and probe
openclaw mcp add tjati --url https://api.tjati.com/mcp \
  --transport streamable-http --auth oauth --no-probe
openclaw mcp login tjati
openclaw mcp doctor tjati --probe
Setup instructions
  1. Add Tjati as a streamable HTTP server with OAuth. The no-probe flag defers authorization until login.
  2. Run the login command and complete the Tjati OAuth flow in the browser.
  3. Run the doctor probe to check transport, auth, and server health.
  4. Verify a read-only Tjati tool before enabling the connection for background work.

Official client documentation supports these commands. End-to-end compatibility soak remains a publish gate.

Docs-supportedRevoke access in Tjati anytime
One connection. Your Tjati context.https://api.tjati.com/mcp

Try it with OpenClaw

Start with a connection you can inspect.

Example requests to try after you verify the connection. Your granted scopes determine which tools are available.

  1. 01

    Read the current state

    Establish a baseline before enabling a broader workflow.

    “List my active Tjati projects and summarize which ones have unresolved next steps. Keep this read-only.”

  2. 02

    Propose a routine

    Design the recurring work around the goals it should support.

    “Use my Tjati goals to propose a weekly review checklist. Show me the checklist before creating work.”

  3. 03

    Define the boundaries

    Keep background work tied to explicit authority and a clear result.

    “Review this proposed Tjati workflow. Explain which steps read information and which would need permission to change it.”

Before you connect

OpenClaw + Tjati, explained.

Why does the OpenClaw command include --no-probe?
The documented setup defers the initial probe until OAuth login. After adding Tjati, run openclaw mcp login tjati and then openclaw mcp doctor tjati --probe to inspect transport and authorization.
Which transport should OpenClaw use?
This guide uses Streamable HTTP with the remote endpoint https://api.tjati.com/mcp. It does not start a local Tjati server.
Should an OpenClaw session stay open for scheduled Tjati work?
Tjati has durable schedules and signed webhooks for approved background workflows. An open interactive client session is not the durable record of the schedule.

Read this page without this page

A direct lane for agent runtimes.

No visual parsing and no JavaScript required. Start with the concise guide, then load only the contract depth the task needs.

Start small. Go deeper when needed.

  1. Recommended

    The concise first read for connection, authority, safe defaults, and operating rules.

    /agent.mdtext/markdownOpen resource

  2. Discovery

    A low-token map of canonical Tjati resources and their purpose.

    /llms.txttext/plainOpen resource

  3. Complete

    Every client setup, scope, delivery rule, and readiness check in one context file.

    /llms-full.txttext/plainOpen resource