Set Up X02 in Claude, ChatGPT, Grok and More

Step-by-step setup for connecting X02 to Claude, ChatGPT, Grok, Cursor, Windsurf and VS Code, with a general recipe for any other MCP app and the plan requirements that trip people up.

By X02 Team · 2026-09-22 · MCP, AI, Tutorial, Claude, ChatGPT, Grok, Developer Tools

Your AI assistant can work with the files in your X02 account directly — find them, look at them, add new ones, sort them into folders and hand you share links. You ask in ordinary words and it does the clicking.

Once it is connected, this works:

"Find the screenshot I uploaded last Tuesday and tell me what's in it."

"Put this week's uploads in a folder called Client Work and share it."

"I've got a photo on my laptop I want up there."

Connecting takes about thirty seconds and one address that you copy and paste. There is nothing to install and nothing to configure.

Never done this before? You do not need to understand anything technical to follow this page. You need two things: an X02 account, and an AI app that supports connections — Claude, ChatGPT, Grok, Cursor, Windsurf and VS Code all do, and so do a growing number of others. Find yours in the list below, or use Any other app if it is not there. Every app hides the setting somewhere different, and a few have requirements nobody mentions until it quietly fails, which is why each one gets its own steps rather than a single instruction.

Curious what is underneath it, or what an assistant is and is not allowed to do with your account? Connect AI Assistants to X02 with MCP covers that. You do not need it to get set up.

[!TIP] Quick Navigation:

Part 1 — for everyone

• The one thing you need
• Claude
• ChatGPT
• Grok
• Gemini
• Le Chat (Mistral)
• Any other app
• Check it worked
• If something is not working

Part 2 — for developers

• Claude Code
• Cursor, Windsurf and VS Code
• MCP Inspector
• More troubleshooting

Part 1: The Easy Guide (For Everyone)

Claude, ChatGPT, Grok, Gemini and Le Chat — and a general recipe for anything else. No typing beyond a copy and paste, and nothing to install.

The one thing you need

https://up.x02.me/mcp

That address is the whole setup. Copy it now — every section below asks you to paste it somewhere.

It is not a password and it is not secret, so it does not matter who sees it. It is closer to a shop address than a key: it tells your AI app where X02 lives. When you paste it in, the app works the rest out by itself, opens your browser so you can sign in to X02 the normal way, and remembers its own permission slip afterwards. You never copy a password or a key into the AI app.

[!NOTE] You need an X02 account before you start, because the assistant works on your files and you are the one who approves it. If you have only ever dropped files on the homepage without signing up, make an account first — it takes a moment and raises your upload limits at the same time.

Claude (web, desktop and mobile)

The short way

X02 is listed in Anthropic's own directory, so there is nothing to type:

1. Open the + menu and choose Browse connectors
2. Search for X02 and click Add
3. A window opens on x02.me — sign in, read what it is asking permission to do, and click Allow Access

That is it. Skip to Check it worked.

The manual way

Use this if you cannot see the directory, or you would rather paste the address yourself. The result is identical — same connection, same sign-in, same everything.

1. Open Customize → Connectors — the toolbox icon at the bottom of the sidebar, then Customize, then Connectors
2. Click + in the top right, then Add custom connector
3. Name it x02, paste https://up.x02.me/mcp, and save
4. A window opens on x02.me — sign in, review the permissions, and click Allow Access

Either way, you add it once and it follows you across claude.ai, the desktop app and mobile, because the connection lives on your account rather than on one device.

On Team and Enterprise plans, custom connectors are added by an organization owner under Organization settings → Connectors; members then connect their own X02 account to it. If you cannot see Add custom connector at all, that is why.

[!NOTE] Claude connects from Anthropic's servers, not your computer. That is invisible for X02, which is on the public internet. It matters if you ever connect a different MCP server running on localhost or behind a company VPN — those cannot work this way, however well they run on your machine.

ChatGPT

ChatGPT calls these apps, and the setting is behind a flag:

1. Open Settings → Apps & Connectors
2. Scroll to the bottom, open Advanced settings, and turn on Developer mode — it is one level deeper than most guides suggest, which is why people report not finding it
3. Add a connector and paste https://up.x02.me/mcp
4. Sign in when the browser opens

Three requirements that are easy to miss:

• A paid plan is required — Plus, Pro, Business, Enterprise or Edu. Custom connectors are not available on the free tier.
• It is web only. Custom MCP apps do not run in the ChatGPT mobile apps, so a connection you add on the web will not follow you to your phone. This is a ChatGPT limitation, not an X02 one — Claude does sync across devices.
• On Business and Enterprise, an admin may have to allow developer mode first. If the toggle simply is not there, this is almost always why, and no amount of retrying will reveal it.

[!WARNING] Developer mode is not optional here. Added as an ordinary connector, ChatGPT exposes only two tools from any MCP server — search and fetch — and X02 has neither. The connection looks fine, and then ChatGPT says the file operation "isn't exposed to me in the current toolset" and falls back to searching the web. Nothing is wrong with your account: turn developer mode on, re-add the server, and all fifteen tools appear.

A quick check before anything else: ask "what x02 tools do you have?" If it cannot name list_files, developer mode is off.

One quirk worth knowing

Ask ChatGPT to show you an image and it will not appear in the conversation. ChatGPT does not render images returned by an MCP server — Cursor and several others behave the same way, and it is filed as a bug against them rather than something a server can fix.

The picture does reach the model, so "describe what's in it" works and is accurate. Every view_file reply also carries a direct link to the full image, which opens normally in a browser. In Claude the image appears inline.

Grok

1. Go to grok.com/connectors
2. Click New Connector, then Custom
3. Paste https://up.x02.me/mcp and sign in when it asks

[!NOTE] xAI documents custom connectors under Business and Enterprise, where an admin has to provision the connector in the cloud console before anyone on the team can use it. If you cannot see New Connector at all, that is the likely reason rather than anything you have done wrong.

Grok will only talk to servers that are on the public internet. X02 is, so there is nothing extra to do — but it is why a server running on your own computer cannot be added this way.

Gemini

Google calls these custom apps:

1. On gemini.google.com, open Settings → Connected Apps
2. Under Custom apps, click Add a custom app and paste https://up.x02.me/mcp
3. Click Next and sign in to X02 when asked

Add it on the web; once connected it works in the Gemini mobile app as well.

[!NOTE] Google currently limits custom apps to personal Google accounts (not Workspace), in the US, aged 18 or over, with Keep Activity turned on. If you do not see Custom apps under Connected Apps, one of those is almost always why.

Le Chat (Mistral)

1. Open Connectors from the sidebar and click + Add Connector
2. Switch to the Custom MCP Connector tab, name it x02, and paste https://up.x02.me/mcp
3. Click Connect — Le Chat works out the sign-in method by itself — and sign in to X02 when asked

Custom connectors are available on every Mistral plan, including Free. On a team plan, only an admin can add them.

Any other app

New apps add support for this every month, and the wording differs in each one. The shape is always the same:

1. Open the app's settings and look for Connectors, Integrations, Tools or MCP — one of those four covers almost everything
2. Choose whatever means add your own: Custom, Add custom connector, Add server
3. Paste https://up.x02.me/mcp
4. If it asks you to pick a type, choose HTTP or Streamable HTTP. Do not pick stdio, local or command — those are for programs running on your own machine, and X02 is not one
5. Sign in when your browser opens, check the permissions, approve

Two things will stop it working, and neither is a setting you can find:

• The app has to support remote servers. Some only run local ones. If the only option asks for a command to run rather than an address, X02 cannot be added there.
• The app has to support signing in. A few older ones only take an API key in a header. X02 deliberately does not work that way, because the whole point is that you never paste a key into someone else's software.

If you get stuck, the MCP Inspector in Part 2 will tell you within a minute whether the problem is the app or X02.

Check it worked

Ask your assistant:

"What x02 tools do you have?"

You are looking for fifteen. If it lists them, you are connected. The quickest real test:

"Upload https://x02.me/favicon.ico to my account and give me the link."

That exercises the connection, the permissions and an actual write, all in one.

If something is not working

The three people hit most often are below. For the longer list — refused permissions, expired sign-ins, quota errors and the rest — see Troubleshooting X02 MCP Connections.

The connector is added, but the assistant has no tools. Almost always an out-of-date list. Your app asks X02 what it can do once, when you first connect, and then remembers the answer. Disconnect it and connect again — closing and reopening the app is usually not enough. Do the same whenever X02 adds new tools, or you will keep seeing the old set.

It says it cannot upload a file I attached to the chat. Expected, and not a misconfiguration. An assistant can look at an attachment but has no way to pass the bytes to a remote server — that is a gap in the protocol itself, not in X02. Ask it to upload anyway and it will hand you a drop link. Or paste files into your tray at x02.me/drop beforehand and they will be waiting.

Sign-in opens but nothing happens after I approve. Two likely causes. Your browser may be blocking the jump back to the app — check for a blocked-popup warning. Or you took longer than ten minutes to approve, in which case the request has quietly expired. Either way, start the connection again from the app.

One thing worth doing every time: before you click Allow, read the address the consent screen says it will send you back to. Anyone can build an app and name it whatever they like, including "X02 Official" — the name proves nothing, the address does. If it is not the app you just clicked in, click Deny.

Part 2: The Developer & Power User Guide

Editors and command-line tools, plus the things worth knowing when a connection misbehaves.

Claude Code

One command in your terminal:

claude mcp add --transport http x02 https://up.x02.me/mcp

Your browser opens for sign-in, and you are done.

If your shell says claude: command not found, the CLI is not installed — it is separate from the Claude desktop app:

npm install -g @anthropic-ai/claude-code

Reopen your terminal afterwards so it picks up the new command.

Cursor, Windsurf and VS Code

All three support remote MCP servers. Look for MCP or Model Context Protocol in settings, add a new server, and give it the same URL. Some versions ask you to pick a transport — choose HTTP or Streamable HTTP, not stdio, since X02 is a hosted server rather than a local program.

MCP Inspector, for when something breaks

The official inspector is the fastest way to see what is actually happening, because it shows each step of the handshake instead of a generic failure:

npx @modelcontextprotocol/inspector

Connect it to https://up.x02.me/mcp. If it works here but not in your assistant, the problem is the client's configuration, not X02 — which narrows things down considerably.

More troubleshooting

The drop link expired before I got to it. They stay open for fifteen minutes. Ask the assistant for a new one — or paste files into your tray at x02.me/drop ahead of time instead, where a drop waits twenty-four hours for whichever assistant asks next.

I approved the wrong app, or want to revoke access. Open Dashboard → Account → Connected apps and click Disconnect beside it. That kills its tokens immediately, whatever the client does. The same list has Edit permissions, to take individual permissions away from an app you want to keep. Your API key, folder keys and every other connected app are unaffected — revocation is per app, which is the main reason to use MCP over handing out a key.

Removing the connector in the client works too, but how fast depends on the client. Ones that call X02's revocation endpoint on disconnect kill the token immediately; ones that simply forget it leave the access token valid until it expires, which is at most an hour. If you need a connection dead right now, use Connected apps.

I use two assistants and one cannot see the other's file. Working as intended. A file requested by one app is delivered only to that app. If you want something available to whichever assistant asks next, drop it into your tray at /drop instead of using a request link.

Next Steps & Related Tutorials

Read this article on X02