Orquesta

com.getorquestaPublished by getorquesta.comOfficial publisherv0.9.449Updated Oct 24, 2026

Read a project's prompts, logs and agents, and send new work to the agent on your own machines.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Lets an assistant read a project's prompts, logs and agents, and dispatch new work to an agent running on your own machines.

What you can do
Orquesta is a remote MCP server that exposes a project's prompts, logs and agents to an assistant, and lets the assistant send new work to an agent on your own machines. It is reached over streamable HTTP at a hosted endpoint, so there is nothing to install locally. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to inspect an existing Orquesta project's prompts, logs and agents, or to hand new tasks to an agent running on your own hardware. It is less useful if you do not already use Orquesta or do not need remote access to your agents.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. The manifest declares no authentication, environment variables or headers, and no local runtime or package is needed.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to read project prompts and logs or dispatch work to your agents; confirm how access is actually controlled before connecting. Sending new work can cause actions on your own machines, so review what the agent is allowed to do.

Installation

In SourceWeft

  1. Open Orquesta 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.getorquesta%2Forquesta/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": {
    "orquesta": {
      "type": "http",
      "url": "https://getorquesta.com/api/mcp"
    }
  }
}

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. v0.9.449LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.