Skip to content

Tjati MCP

Bring Tjati to your AI assistant

Connect Tjati to the assistants you already use. Bring your plans into the conversation, capture what matters, and move work forward — all from one connection.

Choose your assistant

How to connect Claude to Tjati

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

Remote MCP URL
https://api.tjati.com/mcp
Setup instructions
  1. Open Settings, choose Customize, then open Connectors and select Add custom connector.
  2. Name the connector Tjati, enter https://api.tjati.com/mcp, and choose Connect.
  3. Complete the cloud OAuth flow, then review the requested Tjati scopes before granting access.
  4. Ask Claude to list your areas. A read-only result confirms the connection.

Official client documentation supports this flow. 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

Tjati, wherever you think

Your life in context.
In the tools you already use.

Bring your areas, goals, projects, and tasks into the conversation. Let your assistant help with the next step, with permissions you control.

From conversation to a clear next step

Less moving things around.
More moving things forward.

Ask for context. Capture a thought. Review a plan. Your assistant works with the same structure you use in Tjati.

Connect your assistant
TjatiExample workflow

“Help me turn my launch notes into a plan.”

Proposed plan

A clearer path to launch

  • Review the onboarding flow
  • Prepare the launch checklist
  • Draft the announcement
Ready for your review

Review the proposed changes before they become work.

A thoughtful extension
of your assistant.

Start with the whole picture

Read your Tjati context before making a plan. Areas, goals, projects, and tasks give the conversation somewhere to begin.

Stay in your flow

Connect from Claude, ChatGPT, or another MCP client. Your context travels with the conversation.

Keep the decisions yours

Grant only the permissions you need. Review proposed work, and keep high-impact changes behind your approval.

Pick up where you left off

Durable schedules and signed webhooks let approved work continue after the chat ends.

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

Authority

Permission stays visible.

OAuth is the default for interactive clients. Scoped personal access tokens are the fallback for approved headless hosts.

OAuth for interactive clients

The MCP endpoint advertises protected-resource metadata. A compatible client discovers the authorization server, opens Tjati sign-in, and returns with a scoped installation.

OAuth discovery
https://api.tjati.com/.well-known/oauth-protected-resource/mcp

Recovery

If a refresh token expires or access is revoked, remove the stale client connection and start OAuth again. Reauthorization creates fresh authority; it does not restore a revoked key.

Scoped PAT for headless hosts

  1. Open Settings → Connected agents in Tjati and create an agent installation.
  2. Grant only the scopes the host needs.
  3. Issue a key once, store it in a secret manager, and inject it through the runtime environment.
  4. Send it as Authorization: Bearer <token>.

Never put a PAT in a repository, client profile, prompt, or webhook body. Rotate it after suspected exposure.

Start with the default grant

state:readcapture:creatework:propose. Add stronger authority only when the workflow proves it needs it.

Observe and capture

state:readcapture:createcalendar:read

Plan and act

work:proposework:execute

Automate and communicate

automation:managecommunications:readcommunications:draft

communications:draft Not available in this release: Gmail is deferred, so the mail and draft tools return an unavailable result.

A scope grants eligibility, not unconditional execution. High-impact operations can still pause for member approval.

Always-on

The session can end. The work continues.

Schedules create durable runs. Signed webhooks deliver results with bounded retries, failure evidence, and explicit replay.

Receive a signed event

Generate

Request a 32-byte base64url signing secret. Agent callers retain it before proposing the subscription.

Subscribe

Register an HTTPS endpoint and one or more durable core.* event filters.

Verify

Check the timestamp, delivery ID, event ID, raw body, and HMAC signature before processing.

Dedupe

Use the event ID for logical deduplication and the delivery ID for attempt-chain evidence.

Signature input
const signed = [
  timestamp,
  deliveryId,
  eventId,
  rawBody
].join('.')

const expected = hmacSha256Base64url(secret, signed)
timingSafeEqual(expected, signature)

Replay creates a new auditable delivery chain.

Automatic attempts keep one delivery ID. Manual replay is available for terminal deliveries and links back to the original chain.

Replay a terminal delivery
POST /api/v1/webhook-deliveries/{id}/replay
Idempotency-Key: <unique-key>

{ "reason": "receiver recovered" }

Revocation shuts down future authority.

Revoking an installation or its qualifying grant disables subscriptions and schedules, cancels queued work where possible, and preserves terminal delivery evidence. A request already in flight may still finish remotely.

Contracts

Use the schema. Never a guess.

Use the live generated OpenAPI contract for REST integrations and the concise Tjati index for canonical setup and policy links.

Current

OpenAPI

The live generated REST contract for the currently deployed Tjati API.

Open API contract
Current

Documentation index

A concise, same-origin index of canonical Tjati resources and release status.

Open llms.txt

Commercial model

Agent access is included.

Agent access is bundled into Standard and Max. There is no separate agent add-on in this release. Usage is metered for abuse protection and product learning; billing remains unchanged.