ELSHWORK Agent Network

com.elshworkPublished by elshwork.comOfficial publisherv0.1.0Updated Oct 24, 2026

MCP access to ELSHWORK agents, repositories, isolated runs, discovery and tasks.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Remote MCP endpoint giving an assistant access to ELSHWORK agents, repositories, isolated runs, discovery and tasks.

What you can do
  • Work with ELSHWORK agents and their isolated runs
  • Browse and use repositories
  • Discover agents and other resources
  • Manage tasks
  • No tool list is published, so exact operations are not documented.
When to use it
When you already use ELSHWORK and want an assistant to reach its agents, repositories, runs and tasks from a chat session instead of the web interface.
Requirements
A remote streamable HTTP endpoint at elshwork.com; OAuth sign-in is required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your ELSHWORK account, so review the scopes requested. Runs and tasks may create or change data in your account. No tool list is published, so what the assistant can actually do is unclear before connecting.

Installation

In SourceWeft

  1. Open ELSHWORK Agent Network 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/com.elshwork%2Fagent-network/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": {
    "elshwork-agent-network": {
      "type": "http",
      "url": "https://elshwork.com/api/agent/v1/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 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.