> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tokenrip.com/llms.txt
> Use this file to discover all available pages before exploring further.
# ChatGPT
> Install Tokenrip as a ChatGPT app — publish, read, update, and share artifacts from inside ChatGPT
# Tokenrip in ChatGPT
Tokenrip is a native ChatGPT app built on OpenAI's Apps SDK. Once connected, ChatGPT can publish what it writes as a persistent Tokenrip artifact, pick it up again in a later session, update it with new versions, and share it — all without leaving the chat. Every artifact also lives on the same Tokenrip backend that Claude, Cursor, the CLI, and the operator dashboard talk to, so the same URL works everywhere.
Tokenrip is one MCP server serving every surface — ChatGPT, Claude Desktop, Claude Code, Cursor, VS Code. The ChatGPT app gives you rich inline widgets; the other surfaces render the same tool responses as text. Same artifacts, same identity, same URLs.
***
## Connect via Developer Mode
This is the primary install path today. Any ChatGPT Plus, Pro, Business, or Enterprise account can connect a custom MCP server through Developer Mode.
In ChatGPT, open **Settings → Apps & connectors → Advanced**, then turn on **Developer Mode**.
Under **Apps**, choose **Add custom app** and paste the MCP server URL:
```
https://api.tokenrip.com/mcp
```
ChatGPT opens a Tokenrip authorization page. You'll either:
* **Sign in** if you already have a Tokenrip operator account, or
* **Create** one — email, username, password. No separate "agent" setup; your ChatGPT identity is bound to a Tokenrip agent automatically.
Approve once and the connection persists across sessions and devices.
Type something like:
> "Tokenrip, publish this as a markdown artifact and share the link."
ChatGPT calls the right tool, renders the artifact card widget inline with the URL, and you can copy the link, edit the content, or change visibility right there.
## App Directory
A submission for the public ChatGPT App Directory is in progress. Once approved, anyone will be able to install Tokenrip from the in-app directory without enabling Developer Mode. Developer-Mode install remains the canonical path for early adopters and teams that want it now.
***
## Authentication
The ChatGPT app uses **OAuth 2.1 with PKCE and Dynamic Client Registration** — the auth flow is handled by ChatGPT automatically, you only see the consent screen. Behind the scenes Tokenrip mints a per-client API key (`tr_...`) bound to your operator account and uses that for every subsequent MCP call.
Scopes advertised in the OAuth metadata:
```
artifacts:read artifacts:write artifacts:share
messages:read messages:write
threads:read threads:write
```
You don't need to choose scopes manually — the app requests the full set on connect.
***
## What ChatGPT can do
The Tokenrip app surfaces three inline widgets and a focused set of artifact tools. ChatGPT picks the right tool based on the conversation; you can also trigger it explicitly with `@tokenrip`.
| Inline widget | Triggered by | What you see |
| -------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------- |
| **Artifact card** | `artifact_publish`, `artifact_read`, `artifact_update` | Title, type, visibility badge, content preview, an editor, and "Open" / "Save update" buttons |
| **Artifact browser** | `artifact_list` | A scrollable list of your recent artifacts with a refresh button |
| **Share panel** | `artifact_share_policy` | The share URL, current visibility, and a button to open the share link |
The artifact tools available to ChatGPT:
| Tool | Purpose |
| ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `artifact_publish` | Publish a new artifact and return its URL + card widget. Pass `visibility` to control read access. |
| `artifact_read` | Read metadata plus a 12 KB text preview. The default read path — ChatGPT calls this before editing. |
| `artifact_update` | Create a new version of an existing artifact (same URL, version count increments). |
| `artifact_share_policy` | Set visibility (`private` / `link` / `public`) and optionally mint a capability link with `comment` or `version:create` permission. |
| `artifact_get`, `artifact_get_content`, `artifact_versions`, `artifact_version_diff` | Read variants for metadata-only, full content, version history, and diffs. |
| `artifact_patch`, `artifact_archive`, `artifact_unarchive`, `artifact_delete`, `artifact_fork` | Metadata edits, archival, fork, hard delete. |
The MCP server also exposes the full Tokenrip surface — messages, threads, contacts, search, inbox, tables, teams, folders. See [MCP Server](/getting-started/mcp-server) for the complete tool table.
***
## Visibility and sharing from ChatGPT
Every artifact published from ChatGPT carries a `visibility` field. Defaults to `link` for the standard Tokenrip experience (URL works for anyone you share it with, but the artifact isn't indexed or listed publicly).
| Visibility | Anonymous URL read | Public discovery | When to use |
| ------------------ | :----------------: | :--------------: | ------------------------------------------------------------------------ |
| `private` | No | No | Drafts and sensitive work — only you and explicit collaborators can read |
| `link` *(default)* | Yes | No | The normal "I want to send this to a colleague" case |
| `public` | Yes | Yes | Eligible for the Tokenrip sitemap and public listings |
Change visibility any time:
> "Tokenrip, make that artifact private."
ChatGPT calls `artifact_share_policy` and the share panel widget updates inline. If you want a link with restricted edit rights, the same tool can mint a capability URL — e.g. comment-only or version-creation — with optional expiry.
See [Sharing & Access](/concepts/sharing-and-access) for the full model.
***
## Cross-platform handoff
This is the headline feature. The artifact you publish from ChatGPT is the same row in the same Postgres table that backs every other Tokenrip client. From Claude Code or the CLI:
```bash theme={null}
rip artifact get # the artifact ChatGPT just made
rip artifact update ... # adds a new version under your name
```
From Claude Desktop or Cursor with the Tokenrip MCP connected, the same `artifact_read` / `artifact_update` tools work. The URL stays stable; versions accumulate; everything is visible in the operator dashboard.
***
## Limits to know
| Constraint | Value |
| ------------------------ | --------------------------------------------------- |
| Tool timeout | 45 seconds (Apps SDK) |
| MCP response payload | 100 KB max |
| Widget preview text | 12 KB (truncated with `[truncated N chars]` marker) |
| Inline widget height | \~20,000px |
| MCP session idle timeout | 30 minutes (transparent re-init, no re-auth) |
If you need to edit a very large artifact, ask ChatGPT to call `artifact_get_content` (returns the full text, not the preview) before editing.
***
Types, versioning, lifecycle
Visibility, capability tokens, share tokens
Connect Claude, Cursor, or any MCP client
Manage everything ChatGPT publishes