Skip to content

Bring Tjati to GrokBot.

Give your Bot a shared plan to work from. Bring in Tjati project context, capture what a conversation uncovers, and review the next steps before they become work.

Connect GrokBot

How to connect GrokBot to Tjati

Ask GrokBot to add Tjati as a custom remote MCP server. Copy this request into your Bot conversation to get started.

Copy and send to GrokBot
Add Tjati as a custom remote MCP server.
Server URL: https://api.tjati.com/mcp
Use OAuth to connect my Tjati account.
Read https://tjati.com/agent.md for the access rules.
Start by listing my areas. Ask before making changes.
Setup instructions
  1. Copy the request below into your Grok Bot conversation.
  2. Ask the Bot to add Tjati as a custom Remote HTTPS MCP server.
  3. Complete the Tjati OAuth sign-in when requested and review the granted scopes.
  4. Ask the Bot to list your areas first and confirm the read-only result before allowing changes.

Grok Bot supports custom remote MCP servers. This Tjati setup is not yet verified end to end and has no one-click marketplace listing.

Custom setupRevoke access in Tjati anytime
One connection. Your Tjati context.https://api.tjati.com/mcp

Try it with GrokBot

A Bot with a plan to refer back to.

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

  1. 01

    Brief the Bot

    Start the conversation from the structure already in your account.

    “Read my Tjati launch goal and its linked projects. Summarize the next decisions I need to make.”

  2. 02

    Keep the open question

    Keep a useful question connected to the work it can unblock.

    “Capture this question in Tjati and suggest a project for it: what should the first customer onboarding experience include?”

  3. 03

    Review before acting

    Make the Bot’s proposed changes easy to inspect in context.

    “Propose three follow-up tasks from our launch discussion. Show their project links and wait before applying them.”

Before you connect

GrokBot + Tjati, explained.

How does GrokBot reach Tjati?
Ask your Bot to add https://api.tjati.com/mcp as a custom Remote HTTPS MCP server with OAuth. The setup prompt above is a starting point; this Tjati connection still needs end-to-end verification.
Is there a one-click Tjati GrokBot plugin?
No one-click marketplace listing is claimed here. Use the custom remote MCP setup and verify a read-only call before delegating any changes.
Does a local server URL work for this connection?
The Tjati endpoint is public HTTPS. A cloud Bot cannot generally reach a server bound only to localhost on your laptop; use the published endpoint in this guide.

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