OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Orquestra

Orquestra is a Solana developer platform that converts Anchor and Codama IDLs into hosted REST APIs, AI-readable documentation and MCP tools. It supports program and account inspection, PDA derivation, account-data decoding, unsigned transaction building and optional simulation.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Orquestra — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Orquestra when you have an Anchor or Codama IDL and want API or MCP access to its instructions and account data, or need to prepare and optionally simulate unsigned transactions.

Who it is for

  • Solana developers working with Anchor or Codama program IDLs.
  • Teams that want to expose program instructions and account queries through generated REST endpoints.
  • Developers connecting compatible AI agents or MCP clients to Solana program data and transaction-preparation tools.

Documented uses

  • Generate REST endpoints and documentation from a Solana program IDL.
  • Inspect program instructions and query or decode program account data.
  • Discover and derive program-derived addresses.
  • Construct unsigned transactions from IDL-defined instructions and optionally simulate them.
  • Expose program research and transaction-preparation tools through an MCP server.
Before you choose

Requirements & limits

The repository is public and specifies an MIT license. It documents a hosted API and MCP endpoint, as well as a local development setup.

  • The documented IDL inputs are Anchor and Codama.
  • Generated interfaces include endpoints for instructions, accounts, program-account queries, errors, events, types and documentation.
  • Transaction construction is unsigned; the documented agent workflow places signing in a separate skill after explicit user approval.
  • The hosted MCP endpoint is available over Streamable HTTP, and a companion Rust CLI supports local IDL and API-backed workflows.
  • The repository documents a TypeScript web frontend and Cloudflare Workers API/MCP server, with D1 and KV in its deployment stack.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Connect an MCP client to Orquestra

Add Orquestra’s published MCP server to a compatible client.

Before you start

  • An MCP-compatible client such as Claude Code, Claude Desktop, Cursor or VS Code.

Steps

  1. For Claude Code, run claude mcp add --transport http orquestra https://api.orquestra.dev/mcp.

  2. For Claude Desktop, Cursor or VS Code, add an MCP server entry named orquestra with type http and URL https://api.orquestra.dev/mcp to the client’s MCP configuration.

Expected outcome

The client is configured to connect to Orquestra’s Streamable HTTP MCP endpoint.

Guide limitations

  • This setup connects the client to the MCP server; it does not itself upload an IDL or perform a program workflow.
Documentation 1 ↗
Source-based practical guide

Start the local development environment

Set up and start Orquestra’s local frontend and worker environment.

Before you start

  • Git
  • Bun

Steps

  1. Clone https://github.com/berkayoztunc/orquestra.git and change into the orquestra directory.

  2. Run bun install.

  3. Run bun run db:migrate:dev.

  4. Run bun run dev.

Expected outcome

The documented local frontend is served at `http://localhost:5173` and the API at `http://localhost:8787`.

Guide limitations

  • These steps cover local development startup; they do not document production deployment.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
berkayoztunc/orquestra · Official homepage title · retained in its source language
How we review sourcesSuggest a correction