Connect your agent · Docs

One address for every client

artifact.guru plugs into AI clients through the Model Context Protocol (MCP), the standard way to give an agent new tools. Every client uses the same address:

MCP server

https://mcp.artifact.guru/mcp

There are no keys to copy. The first time a client connects, your browser opens, you sign in, tick the workspaces it may use and approve. That's the whole setup.

Claude Code

Run once in your terminal

claude mcp add --transport http --scope user artifact-guru https://mcp.artifact.guru/mcp

--scope user makes it work in every folder; without it, Claude Code keeps the server to the folder you ran the command in. Then type /mcp in Claude Code, choose artifact-guru and approve in your browser. After that, ask Claude in any session to publish something.

Claude.ai and Claude Desktop

Open Settings → Connectors
On claude.ai or in the Claude desktop app.
2
Add a custom connector
Name it artifact.guru and paste the address.
Copy
```
https://mcp.artifact.guru/mcp
```
Approve
Sign in and pick workspaces in the window that opens.

Once added, the connector also works in the Claude mobile apps.

ChatGPT

ChatGPT connects through developer mode, on the web. Publishing and editing are write actions, which OpenAI's help center lists for Business, Enterprise and Edu workspaces. On Pro, it says connected apps can read but not write: ChatGPT can find and read your files, and you upload new ones in the browser.

Turn on developer mode
On Business, only admins can use it: each admin turns it on under Settings → Apps → Advanced settings. On Enterprise and Edu, an admin grants it, then you turn it on there.
2
Create the app
Under Apps, choose Create, paste the address, choose OAuth and Scan Tools.
Copy
```
https://mcp.artifact.guru/mcp
```
Approve
Sign in and pick workspaces in the window that opens.

The app starts as a draft for you. To offer it to everyone in the workspace, an admin publishes it under Workspace settings → Apps. ChatGPT asks you to confirm before it publishes or changes something, unless you tell it to remember your choice for that conversation.

Codex

Run once in your terminal

codex mcp add artifact-guru --url https://mcp.artifact.guru/mcp

Your browser opens right away to sign in and pick a workspace. If it doesn't, run codex mcp login artifact-guru. It works in the Codex CLI, the IDE extension and the desktop app, which share one setup.

Gemini CLI

Run once in your terminal

gemini mcp add --transport http --scope user artifact-guru https://mcp.artifact.guru/mcp

Then type /mcp auth artifact-guru inside Gemini CLI to sign in and pick a workspace. Gemini CLI turns MCP servers off in folders you haven't trusted, so trust the folder when it asks.

Grok Bot and Grok Build

1
Ask the Bot to add it
In a Grok Bot chat, say: “add a custom MCP server called artifact-guru, Remote HTTPS, at this address”. Plugins live in the Bot’s setup, not in Settings; on a Team Bot, the owner adds it from the Plugins card under Setup.
Copy
```
https://mcp.artifact.guru/mcp
```
Authorize
Choose Authorize on the connect card, sign in and pick workspaces. Then type @ in a chat to attach artifact.guru to a task.

No headers are needed: sign-in happens on the connect card. Grok Bot runs on its own cloud computer, so it can upload binary files as well as text.

Grok Build, once in your terminal

grok mcp add --transport http artifact-guru https://mcp.artifact.guru/mcp

Any other MCP client

Any app or agent that supports remote MCP servers with OAuth sign-in can connect. Look for a setting to add an MCP server, a connector, a plugin or an integration, and fill it in like this:

Field	What to enter
Name	`artifact-guru`, or any name you like
URL or server address	`https://mcp.artifact.guru/mcp`
Transport	HTTP, also called Streamable HTTP. Not SSE, not stdio.
Authentication	OAuth. Leave API key, token and header fields empty.

Save it, and the client opens the approval page in your browser the first time it connects. Approve and pick a workspace, as with any other agent.

Clients that only run local (stdio) servers can bridge to it

npx -y mcp-remote https://mcp.artifact.guru/mcp

Approving the connection

The approval page: tick the workspaces this agent may use. The first one ticked is where new files go.

The approval page lists all your workspaces, ticked. One connection can use several, for example your personal workspace and your team's. New artifacts go to the first ticked workspace unless you name another: “publish this to the Acme workspace”.

A connection stays signed in for months while you use it. To disconnect an agent, remove the artifact.guru server in that client. If you leave a team, your agents lose access to it at once: membership is checked on every call.

Things to ask

“Publish this Markdown report privately and give me its link.”
“Find my launch plan and change the delivery date to 14 November. Keep the same link.”
“Make the pricing prototype public.”
“Put everything about Q3 into a project called Q3 planning.”
“Roll the roadmap back to yesterday's version.”

If something doesn't work

What you see	What to do
The browser never opened	Run the sign-in step again (`/mcp` in Claude Code, `codex mcp login artifact-guru`, `/mcp auth artifact-guru` in Gemini CLI, or Authorize on Grok Bot's connect card), or remove the server and add it again.
Claude Code can't see it in another folder	It was added without `--scope user`, so it stays in the folder it was added in. Remove it with `claude mcp remove artifact-guru` and add it again with the command above.
Calls fail with “401” or “invalid token”	The client lost its sign-in. Reconnect it from the client's MCP settings and approve again.
The file went to the wrong workspace	New files go to the first ticked workspace. Name the workspace in your request, or ask the agent to move it.
The agent can't send a local file	The server can't read paths on your computer. Agents with file access (Claude Code, Codex, Gemini CLI, Grok Bot) upload the bytes; chat apps can publish text formats such as Markdown and HTML directly.