SHADDAI Agents MCP
Used by the ORACLE research agent as a research source for finding and synthesizing intelligence from arXiv.
Used by the NEXUS technical architect agent as part of its agentic toolset for GitHub-related code and repository work.
Exposes the curated NVIDIA/skills library through the nvidia_skills tool, allowing users to list all skills, read a skill's full SKILL.md, or filter by keyword or category across areas such as TAO, climate, physical AI, Omniverse, RAG, vision, and Cosmos.
Used by the ORACLE research agent as a research source for gathering and synthesizing information from Reddit.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
SHADDAI Agents MCP
Use your 7 SHADDAI agents — with their real tools and agentic loop — inside Claude Code, Cursor, or any MCP client. Zero dependencies. It proxies to your running SHADDAI backend.
The agents
Agent | Specialty |
SHADDAI | Supreme Orchestrator — strategy, coordination |
NEXUS | Technical Architect — runs code (JS/Python), GitHub, security scans |
ZEROX | Wealth & Revenue — live prices, DeFi, trade math |
ORACLE | Research & Intelligence — web/wiki/arxiv/reddit + synthesis |
TURTLE | UI/UX & Creative — images, palettes, diagrams |
QUILL | Writing & Communication — copy, docs, translation, publishing |
PIKADON | Security & Compliance — code audits, security checks |
Related MCP server: nvidia-nim-mcp
Tools it exposes
shaddai_list_agents— list the 7 agents + what they doshaddai_ask— quick single reply from a chosen agentshaddai_task— a real agentic job: the agent uses its tools over multiple steps and returns the finished worknvidia_skills— the curated NVIDIA/skills library (48 entries): the whole catalog, or one skill's fullSKILL.mdbody
The NVIDIA skills library
A curated 48-skill slice of NVIDIA/skills, installed locally and exposed as a tool.
Category | Count | What it covers |
| 22 | TAO data services, AutoML, DEFT loops, dataset formats |
| 7 | Earth2Studio deterministic forecasts and diagnostics |
| 5 | Defect generation, video augmentation, infrastructure |
| 4 | USD/SimReady/CAD-to-SimReady workflows |
| 3 | Skill discovery and environment setup |
| 3 | NVIDIA RAG Blueprint deploy/configure/troubleshoot |
| 2 | FoundationPose perception pipeline |
| 1 | Cosmos AnomalyGen synthetic defect generation |
| 1 | TAO dataset conversion and validation |
25 of the 48 require an NVIDIA GPU to complete their stated execution path; the other 23 run CPU-only. Every GPU-flagged entry carries a gpuReason naming the exact step that needs the GPU.
The catalog lives at ~/.agents/skills by default. Point it elsewhere with SHADDAI_NVIDIA_SKILLS_ROOT.
Call it three ways:
List all —
nvidia_skillswith no arguments returns every skill with its id, category, GPU flag and S.A.P. relevance.Read one —
nvidia_skillswithskill=<id>returns that skill's fullSKILL.mdbody.Filter —
nvidia_skillswithquery=<text>keyword-matches over id, name, description and S.A.P. relevance;category=<name>filters by category.
Only skill ids listed in nvidia-skills.json can be read, ids are charset-restricted, and the resolved path must sit directly inside the catalog root — path traversal is rejected before any filesystem access.
Rebuilding the manifest
nvidia-skills.json is generated, not hand-edited:
npm run build:manifest # rebuild from the local skill catalog
npm run sync:manifest # copy it to the shaddai-mcp repo
npm test # 16-check stdio JSON-RPC harnessSetup
Your SHADDAI backend must be running (double-click START-SHADDAI.bat → serves http://localhost:3000).
Claude Code:
claude mcp add shaddai -- node "C:/Users/Brittany/mcp-servers/shaddai-agents/mcp.js"Claude Desktop / Cursor (claude_desktop_config.json / .cursor/mcp.json):
{ "mcpServers": { "shaddai": { "command": "node", "args": ["C:/Users/Brittany/mcp-servers/shaddai-agents/mcp.js"], "env": { "SHADDAI_URL": "http://localhost:3000" } } } }SHADDAI_URL defaults to http://localhost:3000; set it if you host SHADDAI elsewhere.
Security
stdout carries only JSON-RPC (logs go to stderr). Inputs are length-capped. It only talks to the backend URL you configure. MIT licensed.
Related MCP Connectors
Governed AI agent skills — one library, distributed to devs and exposed to remote agents over MCP.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Search & install 13,000+ AI agent skills from skills-hub.ai inside any MCP tool.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides 634+ curated production-ready AI skills for any MCP-compatible client, covering areas like security, frontend, backend, infrastructure, AI/ML, and architecture. Enables AI agents to access best practices, patterns, and solutions across multiple domains.612 npm1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to consume 50+ NVIDIA NIM models including LLMs, image generation, and vision through 10 MCP tools with rich metadata and advanced filtering.11291 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, retrieve, and invoke 80+ SkillHub practical skills as standardized MCP tools over stdio, covering coding, office, content creation, data analysis, and security operations.MIT No Attribution
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, retrieve, score, compose, and verify reusable agent skills from the SkillForge registry via MCP.18 npmMIT