Orca MCP Server

io.github.jascalPublished by GitHub account jascalv0.1.30Updated Oct 24, 2026

Go from natural language to verified finite state machines — topology bugs caught before code runs.

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

Lets an assistant turn natural-language descriptions into finite state machines and verify or compile them, catching topology bugs before code runs.

What you can do
Orca MCP Server exposes tools for working with finite state machines: parse_machine, verify_machine and compile_machine handle parsing, verification and compilation, while generate_machine, generate_multi_machine, refine_machine and generate_actions (with use_llm) use an LLM to produce or refine machine definitions from natural language. The stated goal is to catch topology bugs before code runs.
When to use it
Useful when you want an assistant to draft, refine or check state-machine models from a description, and to validate their structure before generating code. Best suited to design and verification work rather than runtime execution.
Requirements
Runs locally as a stdio process, started with npx from the npm package @orcalang/orca-mcp-server, so Node.js and network access for the package download are needed. LLM-backed tools require the ANTHROPIC_API_KEY secret; ORCA_MODEL and ORCA_PROVIDER select the model and provider (anthropic, openai, grok or ollama). The parse, verify and compile tools do not require the API key.
Before you install
The LLM-backed tools send your prompts and machine descriptions to the configured provider, so avoid confidential models. ANTHROPIC_API_KEY is a billable credential and should be supplied through the environment, not hard-coded. Provider selection via ORCA_PROVIDER can route data to a third-party service other than Anthropic.

Installation

In SourceWeft

  1. Open Orca MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.30LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.