In Claude, ChatGPT, Gemini, Grok, Cursor and Microsoft 365 Copilot
From the chat.
To the device.
pipeit is built into ChatGPT, Codex, Claude, Gemini and Grok. Say where: the AI sends the file to your device, to a person, to a server or into your cloud – and organizes your storage if you want.
Proposal_North_v3.pdf → Your MacBookConfirm
Invoice_October.pdf (340 KB) ← Anna's iPhoneAccept
Proposal_North_v3.pdf → Your MacBookConfirm
Invoice_October.pdf (340 KB) ← Anna's iPhoneAccept
Proposal_North_v3.pdf → Your MacBookConfirm
Invoice_October.pdf (340 KB) ← Anna's iPhoneAccept
Proposal_North_v3.pdf → Your MacBookConfirm
Invoice_October.pdf (340 KB) ← Anna's iPhoneAccept
Connect once
One address. Four assistants.
Copy the server address and follow the steps for ChatGPT, Codex, Claude and Claude Code. Gemini and Grok connect to the same address over MCP.
https://mcp.pipeit.now/mcpConnection: Streamable HTTP. Sign-in: OAuth with your pipeit account – client ID and secret stay empty.Claude
Interface: Claude connector and Claude Code via MCP
In Claude, open Customize → Connectors and add a custom connector “pipeit” with the address, sign in and release devices. Claude Code once per user:
claude mcp add --transport http --scope user pipeit https://mcp.pipeit.now/mcpChatGPT & Codex
Interface: ChatGPT app and Codex via MCP
In ChatGPT, add your own MCP connection “pipeit” with OAuth, in developer mode depending on your account. Codex in the terminal:
codex mcp add pipeit --url https://mcp.pipeit.now/mcp codex mcp login pipeit --scopes targets:read,transfers:read,offline_accessGemini
Interface: Gemini and Gemini CLI via MCP
In the MCP settings of Gemini or the Gemini CLI, add a custom server “pipeit” with the address, choose OAuth and sign in.
Grok
Interface: Grok via MCP
In the connector settings of Grok, add a custom MCP server “pipeit” with the address, choose OAuth and sign in.
One sentence is enough
Send. Receive. Tidy up.
You say where or what. pipeit shows you first what will happen – you confirm in the chat.
- Send – to your device, a person, a server or into pipeit Cloud.
- Receive – what has arrived lands straight in the chat.
- Tidy up – sort cloud folders, find duplicates.
- Check – the status of a transfer and the devices you released.
A task. Not unrestricted access.
You see it first. You confirm.
An integration may use only the destinations you authorize. Connecting it does not give general access to your computer.
What you release.
- Send to released devices, people, servers and your cloud – the planned transfer is shown first.
- Bring arrived files into the chat, check the status of a transfer.
- Read your cloud folders, sort them and find duplicates – only in the cloud spaces you choose.
What is not part of the connector.
- A shell, remote login or foreign URLs on your computer.
- Private device keys or general read access to your account.
- A change without your confirmation in the chat.
You set the file source and the permissions once, when you connect.
Connect once.
Then a sentence is enough.
Any MCP-capable client can use pipeit, Cursor included.
Nothing happens without your confirmation in the chatOnly released devices and destinationsOAuth with your pipeit account
Connect an AI assistant