Connect Claude to your JointTex projects
JointTex works as a connector in Claude. Once it is connected, you can ask Claude to read your paper, edit the source, compile it, and reply to review comments, all from a Claude conversation, on the same live project your coauthors have open in the editor.
Setup takes about a minute. There is no token to copy: you paste one address into Claude and sign in to JointTex when it asks.
What you need
- A JointTex account on Education, Plus, or Pro.
- The Claude app, with access to custom connectors.
Step 1: Open Customize and add a connector
In Claude, open Customize in the sidebar and go to the Connectors tab. Click Add and choose to add a custom connector.
Step 2: Enter the JointTex address
Give the connector a name (this is only the label in your connectors list) and paste the server address:
https://jointtex.com/mcp
Then click Continue.
Step 3: Keep the detected sign-in settings
Claude asks the server how it signs people in and marks what it finds as Detected. Leave both as they are:
- Authentication: Sign in now
- OAuth client: Register automatically
You do not need to add any request headers.
Step 4: Connect and sign in
The connector now appears in your list as not connected. Click Connect.
Your browser opens and Claude asks you to confirm that you started this. Click Continue connecting.
You land on a JointTex page titled “Connect Claude to JointTex”. Sign in if you are not already. The page shows which app is asking and where your browser will be sent afterwards, and lets you choose what the app may do and which projects it may open. Click Allow.
Step 5: Choose when Claude may use each tool
Back in Claude, the connector shows “Connected to jointtex” and lists its tools in two groups.
Read-only tools (8): list your projects, get a project’s context, list files, read a file, search files, read comments, read tracked changes, and get the compiled PDF.
Write/delete tools (15): create, replace, edit, rename, copy, move and delete files and folders; compile the project and change its compile settings; add, reply to, resolve and delete comment threads.
Every tool starts at Needs approval, so Claude asks before each call. A setup that works well: set the read-only group to always allowed so Claude can look around without interrupting you, and leave the write/delete group on approval.
Things to try
Start a new conversation and ask in plain language:
- “List my JointTex projects.”
- “In my thesis project, read the introduction and point out claims that have no citation.”
- “Compile the project and fix the errors in the log.”
- “Read the open comments in
methods.texand reply to each one with a proposed change.” - “Give me a link to the compiled PDF.”
Good to know
- It is the same project your coauthors see. Claude’s edits land in the live document, and its comments appear in the same threads as everyone else’s.
- Compile settings are shared. The root file, engine and TeX Live version belong to the project, so a change there affects every collaborator’s compile. Claude is told to change them only when you ask or the build needs it, and to say what it changed.
- PDF links expire. A link from “Get the compiled PDF” works for ten minutes and needs no sign-in, so treat it like the PDF itself and ask for a fresh one when you need it again.
- Usage. Claude’s side of the conversation counts against your Claude plan, not your JointTex AI allowance. Compiles count toward your normal JointTex compile limit.
- A comment thread Claude started is one it can delete. It cannot delete threads other people started; it can only resolve them.
Changing or removing access
In JointTex, open Account settings → Access tokens. Claude is listed under Connected apps, where you can narrow what it may do, change which projects it can open, or disconnect it. A disconnected app loses access immediately. A connection that goes unused for 30 days ends by itself, and you sign in again to bring it back.
You can also click Disconnect on the connector’s page in Claude.
Other apps
Any app that accepts an MCP server URL can connect the same way, with the same address. For clients that send a header instead of signing in, create an MCP token on the same Access tokens page.
Questions or something not working? Reply below.





