NextGenSoftware.OASIS.MCP.Server 2.0.5

OASIS MCP Server

The OASIS Model Context Protocol Server — 516 typed tools covering the full OASIS stack (WEB4 through WEB10) delivered directly into Cursor, VS Code, Claude Desktop, and any other MCP-compatible IDE.

Built on the official ModelContextProtocol C# SDK, communicating over stdio. Part of the OASIS Omniverse ecosystem.

Every tool is specific, named, and typed — the agent sees exactly what's available and can reason about what to call. Generic HTTP passthrough is deliberately omitted because it gives agents no discoverability.

Install

Option A — npm (recommended, no .NET SDK required)

npm install -g @oasisomniverse/mcp-server

Downloads the correct pre-built native binary for your platform (Windows / macOS / Linux, x64 & arm64) automatically.

Option B — NuGet dotnet tool (requires .NET 8+ SDK)

dotnet tool install -g NextGenSoftware.OASIS.MCP.Server

Option C — Build from source (requires .NET 10 SDK)

git clone https://github.com/NextGenSoftwareUK/OASIS.git
cd OASIS/WEB6/NextGenSoftware.OASIS.MCP.Server
dotnet build -c Release
dotnet run

Configure your IDE

After installing, the oasis-mcp command is on your PATH. Add it to your IDE's MCP config:

Cursor (~/.cursor/mcp.json) / VS Code (.vscode/mcp.json) / Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "oasis": {
      "command": "oasis-mcp",
      "env": {
        "OASIS_API_URL": "https://api.web4.oasisomniverse.one",
        "OASIS_MCP_LICENSE_KEY": "your-license-key",
        "OPENAI_API_KEY": "sk-...",
        "ANTHROPIC_API_KEY": "sk-ant-..."
      }
    }
  }
}

For a local build, point at the project instead:

{
  "mcpServers": {
    "oasis": {
      "command": "dotnet",
      "args": ["run", "--project", "/absolute/path/to/OASIS/WEB6/NextGenSoftware.OASIS.MCP.Server"]
    }
  }
}

HTTP MCP Transport (cloud / remote access)

The MCP server also runs as an HTTP endpoint built into the WEB6 REST API — useful for cloud-hosted agents, claude.ai connectors, and any client that can't use stdio:

GET  https://api.web6.oasisomniverse.one/mcp       — establishes SSE stream
POST https://api.web6.oasisomniverse.one/mcp       — send MCP JSON-RPC tool calls
GET  https://api.web6.oasisomniverse.one/.well-known/mcp.json   — auto-discovery document

Note: These endpoints are intentionally not shown in the Swagger UI (/swagger) because they use SSE / streaming transports that the interactive explorer cannot represent. They work normally — call them directly or point your MCP client at the discovery URL and it will configure itself automatically.

Tool Reference

For the exhaustive command-by-command reference, including parameter signatures and descriptions, see complete 516-command catalog.

WEB4 — Identity, Karma, NFTs, Wallets, Chat, Search, Stats & more (365 tools)

Avatar

Karma

Holons, NFTs & Wallets

WEB5 — Holons, OAPPs, Quests, Missions, Zomes, Libraries, Games & more (95 tools)

Quests & Missions

OAPPs (OASIS Applications)

Holons & Celestial Bodies

WEB6 — AI, FAHRN, BRAID, Memory, Orchestration (39 tools)

AI Completion & Embeddings

FAHRN Multi-Agent

Holonic BRAID

Holonic Memory

External Memory Providers

Orchestrators

ML.NET & Context

WEB7 — Symbiosis & Collective Consciousness (7 tools)

WEB8 — Galactic Mesh & Protocol Bridge (8 tools)

WEB9 — Singularity (1 tool)

WEB10 — The Source (1 tool)

Environment variables

Required

AI Provider Keys (at least one required for WEB6 tools)

External Memory Providers (optional)

API Base URL Overrides (for local dev)

Links

• oasisomniverse.one
• oasisweb4.com/products/mcp — product page & pricing
• WEB6 README — full REST API reference
• WEB6 API Reference
• WEB6 MCP Tool Reference
• WEB6 User Guide
• OASIS GitHub