io.github.westonhancock/orcha MCP Server

The io.github.westonhancock/orcha MCP server securely searches and manages workspace context files for AI agents and teams. It focuses on workspace context retrieval and organization to support downstream agent workflows that rely on those files.

🛠️ Key Features

Secure search for workspace context files
Workspace context file management

🚀 Use Cases

Finding relevant workspace context files for AI agents
Coordinating context access across AI teams

⚡ Developer Benefits

Centralized access to workspace context files for agents
Supports team use cases involving shared workspace information

⚠️ Limitations

Available server details include only description-level behavior; specific tools, capabilities, and constraints are not provided

Orcha MCP server

Orcha is a unified context layer for AI tools and agents. It stores, indexes, and exposes organizational, team, or individual knowledge. Files, structured databases, and connected sources live in one workspace, and agents reach them through Model Context Protocol (MCP), CLI with virtual file system, or REST API, with permissions, citations, and provenance.

This repository is the public connection guide and registry listing for Orcha's hosted MCP server. The service runs at:

code

https://app.tryorcha.com/mcp

Transport is Streamable HTTP. The application source code is private; nothing needs to be installed or built from this repository to use the server.

What the server provides

24 tools spanning:

Ranked search over all indexed workspace content (search_context) with fast, balanced, and fresh routing modes, plus a citation on every result
File and folder reading, creation, update, organization, and deletion, scoped to what the connection is allowed to touch
Curated context bundles with usage guidance (list_bundles, get_bundle)
Structured databases with typed queries (list_databases, query_database, record CRUD)
Direct access to connected read-only sources (query_source, fetch_source_document, list_source_documents)
Filesystem-shaped browsing (browse_context): ls, tree, find, cat, grep, and stat over a virtual tree of the workspace

Every connection is isolated to the organization, workspace, permissions, and optional folder scope it was granted.

Connect with OAuth (recommended)

Add the server URL to any OAuth-capable MCP client. The client discovers Orcha's authorization server automatically and walks you through consent; the grant is scoped to the organization and workspace you approve.

Claude Code:

bash

claude mcp add --transport http orcha "https://app.tryorcha.com/mcp"

claude.ai and Claude Desktop: Settings, Connectors, Add custom connector, then enter https://app.tryorcha.com/mcp.

Cursor and other OAuth-capable clients: add a remote MCP server with the same URL and follow the sign-in prompt.

Connect with a bearer token (headless and CI clients)

Create an Orcha account and workspace at app.tryorcha.com/signup.
Create an API token scoped to that workspace with only the permissions the client needs. Tokens begin with orca_.
Configure the client with an Authorization header:

json

{
  "mcpServers": {
    "orcha": {
      "url": "https://app.tryorcha.com/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer orca_your_token"
      }
    }
  }
}

Example prompts

"Search my workspace for the current authentication requirements and summarize them with the source file names."
"Show me the five files most related to our deployment runbook."
"Check which Orcha context bundles apply to this task and use the best match as the source of truth."
"Create a Markdown file named launch-checklist.md from these release requirements."
"Get the engineering-onboarding context bundle and identify any conflicting guidance."

Registry listing

The server is published in the Official MCP Registry as io.github.westonhancock/orcha. The manifest in server.json mirrors the registry entry. A machine-readable server card is served at https://app.tryorcha.com/.well-known/mcp/server-card.json.

Orcha