Pollinations Computer MCP Server: Setup for Claude, Cursor and More
Gives your assistant a private computer in the cloud, with files that stay between chats, a bash shell and JavaScript.
This Pollinations server gives each account its own persistent workspace. The assistant can save files, run shell commands and run JavaScript there, and the files are still there next time. It runs on Pollinations' servers, and you sign in with a Pollinations API key.
It suits people who want an assistant to keep notes, scripts and project files without using their own machine. It is a limited shell. It has no Node or Python, and every call is billed at a flat rate.
Good for
- People who want an assistant with its own scratch space and memory
- Developers who want a safe place to run small scripts and git clones
Works in
14 should work
Tap an app to see how to set it up and any known problems.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Install Pollinations Computer MCP
Claude Code
- 1
Copy this prompt.
Add the Pollinations Computer MCP server to Claude Code. Run this command: claude mcp add --transport http pollinations-computer https://gen.pollinations.ai/mcp/computer --header "Authorization: Bearer YOUR_KEY" Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Pollinations API key.
Read-only mode: There is no read-only switch.
Get a key at enter.pollinations.ai/keys and replace YOUR_KEY. Pollinations says the Polli CLI can also add this server to each supported client and create a dedicated key for it.
From the vendor's docs. Source.
Tools
Runs a shell command in your private workspace
Runs a command in a shell with coreutils, grep, sed, awk, jq, tar, curl and git. Files in /workspace stay between runs, and curl can reach any public web address.
Try: “Clone this public repo into /workspace and list its files.”
Delete ·
bashRuns JavaScript in your private workspace
Runs a short JavaScript function in a fresh sandbox and returns its output. It can read and write your workspace files and make web requests, but cannot use npm packages.
Try: “Write a script that counts the lines in every file in my notes folder.”
Delete ·
javascript
Read from the source code
Permissions
medium risk · 4 things to watch
Medium risk
The assistant can run commands and code in your private workspace, change or delete its files and fetch any public web address. It runs in Pollinations' sandbox, not on your computer.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It runs commands and code with no read-only mode
Commands run in a sandbox on Pollinations' servers with your workspace files. Keep secrets out of the workspace. github.com
It can fetch any public web address
The README says there is no host allowlist for curl or fetch. The assistant can download from, or call, any public site. github.com
Pushes to collective memory are public
Pollinations says that repository is public and permanent. Tell the assistant never to write private data there. github.com
Published files are open to anyone with the link
The assistant can publish a file to a link that anyone can open for 30 days. github.com
Technical details
| Turning on read-only | No read-only switch is documented. Both tools run commands. |
|---|---|
| Talks to | Any public web address (no allowlist). github.com/pollinations/collective-memory (public pushes). media.pollinations.ai (published files) |
| Sign-in and keys | A Pollinations API key, sent as a Bearer header on every request. The Polli CLI stores it in plain text in your client config, as Pollinations documents. |
Questions
Does it need an API key?
Yes. Every request needs a Pollinations API key, which you create at enter.pollinations.ai/keys. Calls use that key's Pollen wallet and budget.
Is it official?
Yes. Pollinations built and hosts it, and its code is in the Pollinations repo.
Where does the code run?
On Pollinations' servers, in a sandbox tied to your account. It does not run on your computer.
Can it run Node or Python?
No. The shell has no Node or Python. The javascript tool runs a single JavaScript function without npm packages.
Do my files stay between chats?
Yes. Files in your workspace persist between runs, except the /tmp folder, which is emptied after every call.
How much does it cost?
0.0002 Pollen per successful call, a flat rate Pollinations lists in its catalog as a preview price. Discovery and storage are free. The rate can change, so check the catalog.
What is the server URL?
It is https://gen.pollinations.ai/mcp/computer. Send your API key as a Bearer header.
Information
updated Nov 2, 2026
- Publisher
- Official
- Endpoint
https://gen.pollinations.ai/mcp/computer- Transport
- Streamable HTTP
- Auth
- API key
- Version
- 1.0.0
- Last commit
- Oct 31, 2026
- Listed in
- Official MCP registry
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 4Hide
- Pollinations MCP servers docs · github.com
- Computer MCP README · github.com
- Computer MCP server.ts · github.com
- Pollinations MCP catalog · gen.pollinations.ai