jinionDocs
TRjinion.co

Guides

Codex, Claude Code and Cursor

Give the agent you already use your team's decisions and the project map, with jinion mcp.

View as MarkdownOpen in ClaudeOpen in ChatGPT

Not everyone on a team moves to Jinion at once. jinion mcp gives the agent you already use what your team's agents share: the decisions that apply to the commit you're on, and the map of what your project's files already offer. Your agent reads them before it changes your code, names a teammate's decision when it shapes the work, and records one when you ask it to. You don't need Jinion installed.

Add it to your agent

Run it in a linked repository, the one with jinion.config.json at its root.

Codex

Terminal
codex mcp add jinion -- npx -y @jinion/cli mcp

Claude Code

Terminal
claude mcp add jinion -- npx -y @jinion/cli mcp

Cursor

In .cursor/mcp.json at the repository's root, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "jinion": {
      "command": "npx",
      "args": ["-y", "@jinion/cli", "mcp"]
    }
  }
}

It works in the folder your agent names as its root, or else in the folder it starts in.

Sign in once

The first time your agent asks for the team's decisions, it gives you a link and a code:

To read your team's decisions, Codex needs you to sign in to Jinion once. Open
https://cloud.jinion.co/connect?code=WDJB-MJHT, check that it shows the code WDJB-MJHT, and approve it.

Open the link, sign in with your email or GitHub, check that the page shows the same code, and click Connect. Then ask your agent again. The link works for 10 minutes, and only once.

If Jinion's apps are already signed in on your machine, jinion mcp uses that account and asks nothing.

An invite to the team's workspace is enough: you don't need an invite code for the private beta to use jinion mcp. You still need one to use Jinion's apps.

When it can't help yet

Your agent tells you what's missing and what to do:

It saysDo
The repository isn't linked to a teamAsk a teammate to link it, commit jinion.config.json, and pull
You aren't in the workspaceAsk to join from the link it gives you, or ask an admin to invite you
You asked to join, and nobody answered yetWait for an admin; the decisions are there as soon as they approve
Jinion can't be reachedIt uses the copy on your machine; with none yet, try again once you're online

What it does, and what it doesn't

Through jinion mcpOnly in Jinion
Reads the decisions that apply to your commit, and marks the ones not pulled yet or on other branchesRecords the decisions that matter as it works, without being asked
Records a decision when you ask your agent toHolds each turn against the decisions, and warns before one is broken
Finds what your project's files already offer, before your agent writes anotherChecks a turn's code against the project's habits and design tokens

Decisions recorded through jinion mcp are drafts until a commit carries them, as in Jinion, and then apply to your teammates once they pull. On cloud.jinion.co, the workspace's Members page shows that you connect through your agent, and each decision you recorded says through which.

Privacy

jinion mcp sends api.jinion.co the decisions you ask it to record, with the branch, the commit, the files they concern and the names those files declare; your repository's address and first commit, which tell the project's repository from any other; and the name of your agent, such as Codex, so your workspace can show how you connect. It doesn't send your conversation or your code. The project map is read on your machine and stays there.