Os Automation Mcp

io.github.varvararattaPublished by GitHub account varvararattav1.0.0Updated Oct 24, 2026

MCP server for OS Automation

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Hosted MCP endpoint for OS automation, part of a public MCP server farm; free health and discovery tools, paid tools via x402.

What you can do
  • No tool list is published; the description only says it is an MCP server for OS automation.
  • The README describes a hosted farm of MCP servers on MCPize with zero-auth public APIs.
  • Free tools include a health check and discovery tools; other tools are paid.
  • Payment for paid tools is handled through x402 in USDC on Base.
When to use it
Consider it if you want a hosted, no-setup endpoint for OS automation tasks and your MCP client can handle x402 payments for the paid tools.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared and no authentication is declared. An x402-capable MCP client is required for paid tools; network access to the hosted endpoint is needed.
Before you install
Paid tools require x402 payments in USDC on Base, so using them spends cryptocurrency; check pricing before calling. The server is a third-party hosted service with no declared authentication, and its actual tool set is not documented here.

Installation

In SourceWeft

  1. Open Os Automation Mcp in the dashboard and add it to a workspace.
  2. 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/io.github.varvararatta%2Fos_automation_mcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "os-automation": {
      "type": "http",
      "url": "https://os-automation-mcp.mcpize.run/mcp"
    }
  }
}

README

BotFactory MCP Farm

Hosted MCP servers on MCPize — zero-auth public APIs, freemium x402 (USDC on Base).

Catalog

See CATALOG.md for the full list with gateway URLs.

Connect

https://<slug>.mcpize.run/mcp

Requires an x402-capable MCP client for paid tools. health_check and discovery tools are free.

Awesome list entries

See AWESOME_ENTRIES.md.

Source: README.md at commit 14e36b4

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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 listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.