Auto-building agents

io.github.rohanarunPublished by GitHub account rohanarunv1.0.1Updated Nov 14, 2026

Build, run, inspect, and continue AgentScript workflows on connected Super Chrome and Mac clients.

The publisher's own server: Auto.dev

VerifiedStreamable HTTPWeb executableBrowser AutomationAI & ML

Overview

AI-generated overview

Lets an assistant build, run, inspect and continue AgentScript agent workflows on your connected Super Chrome extension or Mac app.

What you can do
  • Build and continue agents from stated goals, with the assistant writing AgentScript directly from the current script context
  • Run and inspect workflows on connected Super clients, with completion reported from observed execution results
  • Discover connected devices and their current capabilities before running a task
  • Read existing projects and their progress to resume a task
  • Hand off runtime model calls to the connected assistant conversation through pause-and-resume
When to use it
Use it when you want an assistant to author and execute multi-step agent workflows on your own connected Super devices, such as research or web tasks, and to pick up earlier projects where they left off.
Requirements
Remote MCP endpoint at app.getsupers.com over streamable HTTP with OAuth authentication. A Super account, plus a signed-in Super client (Mac app or Chrome extension) connected to the same account. Chrome access may require a subscription link and extension installation. Optional OpenRouter keys or Super credit-backed models must be explicitly selected.
Before you install
Task prompts, project and chat content, device identifiers, generated scripts and execution results are sent to the Super service, and model requests may be routed to third-party model providers. Connected clients can read websites and local applications, so results may contain personal data. External sends, purchases and deletions need authorization in your request. Projects and chat history persist. A generated script does not prove successful execution.

Installation

In SourceWeft

  1. Open Auto-building agents in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.rohanarun%2Fauto-building-agents/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "auto-building-agents": {
      "type": "http",
      "url": "https://app.getsupers.com/mcp"
    }
  }
}

README

Auto-building agents

Build and continue agents from your goals through Super and your connected Mac app or Chrome extension. The plugin includes the build-agents skill and the Super remote MCP connection. Execution requires a Super account and a connected Super client.

Connect

Enable the plugin and authenticate the Super MCP connection through OAuth at https://app.getsupers.com/mcp. Sign into your Super client with the same account. Claude discovers your connected devices and their current capabilities before running a task. Immediately after connecting, Claude checks your Super account and presents its account-linked subscription link if Chrome access is required, before requiring extension installation. Claude writes AgentScript directly using the current script context from MCP; no separate extension-selected model builds the script. Runtime model functions default to the connected assistant conversation through a pause-and-resume MCP handoff. Optional OpenRouter keys and Super credit-backed models require explicit selection. Host handoff requires an active conversation. Prefer deterministic workflow code where possible. Follow the live MCP account response for current access, pricing, and recurring credits.

Ask: “Build an agent that researches a topic using my connected Super Chrome extension.” To continue a task, ask Claude to read your existing project and its progress. Completion is reported from observed execution results.

Recorded walkthrough

Watch the recorded Amazon checkout walkthrough. The demo uses pencils and stops on the checkout payment selection screen without confirming payment or placing an order. Personal address and payment information is masked in the recording.

This recording illustrates a user-authorized workflow. The plugin bundles no executable scripts or checkout template. Claude authors scripts for the requested task using the Super MCP API; execution takes place through the declared connector on the user’s connected client. A generated script alone does not prove successful execution.

Data and permissions

The declared Super MCP connector sends task prompts, project/chat content, selected device identifiers, generated scripts, and execution results to the Super service. Connected clients can read or interact with websites and local applications within the user's authorized task; those results can contain personal data. Super may route model requests to model providers used by the selected model. Projects and chat history persist to support continued agents. Refer to the privacy policy for data handling and retention. The plugin does not install hooks, change Claude permissions, or bundle an executable. OAuth secrets and reviewer credentials are not included.

External sends, purchases, deletions, and other consequential operations require authorization within the user's request. Only the authenticated user's devices and projects may be accessed.

Support · Terms. Plugin use is subject to the included LICENSE and Super's terms.

Source: README.md at commit cf2a76c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestNov 14, 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 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Auto integrations