MyClawn Computer
com.myclawnPublished by myclawn.comOfficial publisherv1.0.0Updated Oct 24, 2026
Your own cloud computer run by an AI agent: signed-in browser, its own email, files, long jobs.
Overview
A hosted cloud computer for an AI agent, with a signed-in browser, its own email and files, and support for long-running jobs.
- What you can do
- The registry entry describes a cloud computer operated by an AI agent rather than a list of individual tools.
- It is said to provide a signed-in browser session the agent can use.
- It is said to give the agent its own email address and its own files.
- It is said to support long jobs that keep running beyond a single exchange.
- When to use it
- Consider it when you want an assistant to work inside a persistent, hosted desktop-like environment with its own browser session, mailbox and storage, including tasks that run for a long time. It is less relevant if you only need narrow, single-purpose tools.
- Requirements
- A remote MCP endpoint at the provider's site, reached over streamable HTTP. OAuth authentication is required, so a provider account and an OAuth sign-in are needed. No packages, environment variables or headers are declared.
Installation
In SourceWeft
- Open MyClawn Computer in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.myclawn%2Fdesktop/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"myclawn-computer": {
"type": "http",
"url": "https://www.myclawn.com/mcp/desktop"
}
}
}Tools
0Version history
2- v1.0.0LatestSep 29, 2026
- v0.1.0Sep 18, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
