/// access oasis. natural language. infinite possibilities.
The MCP Server brings 250 typed tools directly to Cursor, VS Code, and other MCP-compatible IDEs, covering the full OASIS stack from WEB4 through WEB10. Mint NFTs, manage wallets, orchestrate AI agents with FAHRN, store holonic memory, and discover AI agents — all through conversation.
Traditional development requires switching between documentation, API clients, and your IDE. The MCP Server eliminates this friction by bringing all OASIS capabilities directly into your development workflow. Ask your IDE to mint an NFT, create a wallet, or generate a smart contract, and it happens instantly through the MCP protocol.
Mint, transfer, and manage NFTs across all supported blockchains. Query collections, retrieve metadata, pin GeoNFTs to real-world coordinates, and manage cross-chain NFT operations through natural language.
Create wallets for Solana, Ethereum, and 50+ other blockchains. Send transactions, check balances, link cryptographic keys, and manage multi-chain assets directly from your IDE.
Generate, compile, and deploy smart contracts for Ethereum, Solana, and Radix. Specify requirements in natural language and receive production-ready contract code.
Create and manage avatars, query and award karma, access portrait and profile data, and manage cryptographic keys across Web2 and Web3 — all through natural language.
Drive WEB6's FAHRN multi-agent reasoning engine — Serial, Parallel, Debate, Voting, and Decomposed modes — auto-selected by ML.NET classifier. Benchmarked at 74× PPD improvement on GSM-Hard.
Store and retrieve fractal persistent memory across Session → Agent → User → Group → Earth hierarchy levels with semantic search, TTL, and multi-hop propagation via MCP tools.
Access OpenAI, Anthropic, Google Gemini, Groq, Mistral, Cohere, xAI, Ollama, HuggingFace, DeepSeek, AWS Bedrock, Azure, and more — all through one unified MCP interface.
Trigger WEB6's SkillOpt engine (Microsoft Research, arXiv:2605.23904) to improve agent skills over time — +23.5% accuracy gain, building a proprietary skill corpus as an asset.
Discover and interact with AI agents through the A2A Protocol and OpenSERV infrastructure. Delegate tasks, request services, and orchestrate multi-agent workflows from your IDE.
Build OAPPs, quests, missions, zomes, and libraries on the WEB5 STAR layer. Manage chapters, inventory, celestial bodies, geo hotspots, and AR integrations through natural language.
Start chat sessions, send direct messages, retrieve conversation history, manage notifications, and post to social providers — all WEB4 capabilities accessible from your IDE.
Issue and verify W3C Decentralised Identifiers (did:key, did:web, did:ethr, did:ion) and Verifiable Credentials with HMAC-SHA256 proof via Universal Resolver — all from your IDE.
Query karma stats, leaderboards, system-wide network stats, gift stats, and run full cross-entity OASIS search — 8 stats tools and a unified search tool on WEB4.
Access Symbiosis (bio-signal sessions), Galactic Mesh (distributed node routing), Singularity (unified cross-layer status), and Source (root identity) — 21 live MCP tools.
Two one-line install options — npm (no .NET SDK needed) or NuGet dotnet tool — plus build from source. Configure your IDE, restart, and start using natural language commands.
npm install -g @oasisomniverse/mcp-server
# Then configure your IDE (see Configure tab) using:
# "command": "oasis-mcp"dotnet tool install -g NextGenSoftware.OASIS.MCP.Server
# Then configure your IDE (see Configure tab) using:
# "command": "oasis-mcp"# Clone the OASIS repository
git clone https://github.com/NextGenSoftwareUK/OASIS.git
cd OASIS/WEB6/NextGenSoftware.OASIS.MCP.Server
# Build and run
dotnet build -c Release
dotnet run// After npm or NuGet install — oasis-mcp is on your PATH:
{
"mcpServers": {
"oasis": {
"command": "oasis-mcp",
"env": {
"OASIS_USERNAME": "your-avatar-username-or-email",
"OASIS_PASSWORD": "your-avatar-password"
}
}
}
}
// After build from source — point at the project:
// "command": "dotnet",
// "args": ["run", "--project", "/absolute/path/to/OASIS/WEB6/NextGenSoftware.OASIS.MCP.Server"]
// Prefer a token? Use "OASIS_BEARER_TOKEN": "<your OASIS JWT>" instead of username/password.// Restart your IDE completely, then ask:
"Check the OASIS API health status"
// Or:
"List all available OASIS tools"
// If it works, you're ready to go!
// Troubleshooting:
// - Check Cursor logs: View → Output → MCP
// - Verify path is absolute in mcp.json
// - Check your avatar username/password (or bearer token)
// - Calls that act on another avatar need a Wizard avatar
Two install options:
npm install -g @oasisomniverse/mcp-server (no .NET SDK needed) or
dotnet tool install -g NextGenSoftware.OASIS.MCP.Server (requires .NET 10).
Both put oasis-mcp on your PATH. It is a lightweight proxy: every tool runs in the hosted OASIS service as your avatar and is billed to your OASIS subscription, so no local database, DNA or AI provider keys are needed.
View on GitHub
The IDE server above is a proxy to this hosted endpoint. Call it directly from cloud-hosted agents, claude.ai connectors, and any client that cannot use stdio:
POST https://api.web6.oasisomniverse.one/mcp — MCP JSON-RPC (Streamable HTTP); send Authorization: Bearer <OASIS JWT>
GET https://api.web6.oasisomniverse.one/.well-known/mcp.json — auto-discovery document
GET https://api.web6.oasisomniverse.one/.well-known/agent.json — A2A agent card
Billing & access: each tool call runs as the avatar in your bearer token and counts against your OASIS subscription (AI tools on measured tokens, everything else as one API call; listing tools is free). Send an Idempotency-Key header per tool call and reuse it on retry so a retry is never billed twice. Tools only act on your own avatar unless you are a Wizard.
Note: These endpoints — along with the SSE streaming completion (/v1/complete/stream), telemetry stream, A2A event stream, and WebSocket session — are intentionally not shown in Swagger UI because they use streaming transports the interactive explorer cannot represent. They work as documented; call them directly with curl or point your MCP client at the discovery URL and it configures itself automatically.
Quickly prototype blockchain applications by asking your IDE to mint NFTs, create wallets, or generate smart contracts. Focus on your application logic while MCP handles the infrastructure.
Automate repetitive blockchain operations through natural language. Create scripts that interact with OASIS APIs without writing boilerplate code or managing authentication.
Seamlessly integrate OASIS, OpenSERV, and STAR platforms into your development workflow. Access all capabilities through a single interface without context switching.
Ask your IDE to spin up FAHRN multi-agent reasoning pipelines, register SkillOpt tasks, or query holonic memory — build production AI systems without leaving your editor.
Build OAPPs, quests, missions, and zomes for the STAR metaverse layer through natural language. Design immersive experiences and deploy them to STARNET from inside your IDE.
Query karma leaderboards, NFT collections, system-wide network stats, and unified WEB9 health reports — pull live OASIS data into your IDE without writing a single API call.
Choose the plan that fits your development needs. MCP Server uses the same subscription as the OASIS API: same limits, same features, accessed through your IDE.
The MCP Server uses your OASIS avatar and subscription: no separate license key.
1. Create your OASIS avatar: free, takes a minute.
2. Choose a plan: start on Free, or subscribe for higher limits. Your plan covers direct API calls and MCP tool calls alike.
3. Install and sign in: run npm install -g @oasisomniverse/mcp-server, put your avatar username and password in your IDE's MCP config (above), and restart your IDE.