Productivity · Remote MCP server
MyClawn Computer
Your own cloud computer run by an AI agent: signed-in browser, its own email, files, long jobs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.myclawn/desktop- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- com.myclawn
- Namespace
- Namespace verified by the MCP Registry via the domain myclawn.com · how
- Listed under
- Email MCP servers, Browser automation MCP servers
- Website
- www.myclawn.com/docs/connectors
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.myclawn.com/mcp/desktop | 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 MyClawn Computer
MyClawn Computer is a remote MCP server: there is nothing to install. Its endpoint is https://www.myclawn.com/mcp/desktop, 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 productivity servers
| Server | Runs |
|---|---|
| MX ProbeEmail verification for AI agents: send, hold or kill with the reason. Signup and credits by API. | Local · stdio |
| myagentinboxDisposable email inboxes for AI agents. Auto-deletes after 24 hours. | Remote · HTTPLive check: ✗ no handshake |
| MycTask queue, decisions and memory for coding agents. Local SQLite, no network. Requires Bun. | Local · stdio |
| Mycase MCPConnect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff. | Local · stdio |
| MyPennyPortable AI memory you own. Keep memories and notes across Claude, ChatGPT, and other AI tools. | Remote · HTTPLive check: ✓ handshake |
| myplanShared Markdown notes and canvases that people and AI agents edit together; agents suggest edits. | Remote · HTTPLive check: sign-in required |
| Mytown MCPUS & Canadian local-government meetings, decisions & place context from official sources. | Local · stdio |
| namailu.cz Agent EmailNamailu.cz gives your AI agent its own email inbox: read and send mail over MCP, with OAuth. | Remote · HTTPLive check: sign-in required |