Other · Remote MCP server
puter.com
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.puter/mcp-server- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-06-13
- Updated
- 2026-06-13
- Publisher
- com.puter
- Namespace
- Namespace verified by the MCP Registry via the domain puter.com · how
- Website
- puter.com
- Repository
- github.com/HeyPuter/puter
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.puter.com/ | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect puter.com
puter.com is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.puter.com/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| PusharyThe decision layer for AI agents. Your agent asks, a person approves or denies on their phone. | Remote · HTTP, SSELive check: ✓ handshake |
| Pusher ChannelsTrigger events, query channels, and manage realtime messaging on Pusher Channels. | Local · stdio |
| Pusher MCPQuery the Pusher HTTP API: channels, channel details, channel users. | Local · stdio |
| pushinpay.com.brMCP oficial da PushinPay: cobranças PIX, consulta de transações e saldo via IA. | Local · stdio |
| Putput MCPFile uploads for AI agents. Upload, list, and manage files. No signup required. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Pvpc MCP ServerRetrieve daily PVPC electricity tariffs for 2.0 TD consumers, published by Red Eléctrica. | Local · stdio, HTTP |
| PXL8 verified fight recordsVerified fight records for AI assistants: look up a fighter or fight card, cite the pxl8.io page. | Remote · HTTPLive check: ✓ handshake |
| PyAI Voice AISpeech, transcription, voice agents, Trace, Recap, dubbing and narration with browser OAuth. | Remote & Local · HTTP, stdioLive check: sign-in required |