Build with AI
Give your AI coding assistant access to NERO Embedded Wallets documentation and SDK reference
Build with AI
Speed up NERO Embedded Wallets integrations by giving your AI coding assistant access to the documentation and SDK reference.
You can set up:
- Skill — Guides your AI assistant on how to reason about the SDK (architecture, framework considerations, key derivation rules, common pitfalls). Contains no code.
- MCP server — Provides real-time access to documentation search, code examples, and SDK types.
- Static docs — Full documentation as a single text file for tools that don't support MCP.
Skill
The skill provides a mental model for NERO Embedded Wallets. It includes SDK selection logic, key derivation rules, authentication concepts, protocol specifics (DKLS vs Pedersen), and common mistakes that aren't obvious from the docs alone.
For the best experience, use the MCP server alongside the skill so your assistant can fetch live docs and examples.
Claude Code CLI
Download the skill and append it to your project's CLAUDE.md:
npx degit nerochain/nero-mpc-sdk/skills/nero-embedded-wallets /tmp/nero-skill
cat /tmp/nero-skill/SKILL.md >> CLAUDE.mdCursor
Copy the skill into your project:
npx degit nerochain/nero-mpc-sdk/skills/nero-embedded-wallets .cursor/skills/nero-embedded-walletsCursor picks up any SKILL.md inside .cursor/skills/ automatically.
Claude Desktop
Open Claude Desktop → Settings → Custom Instructions and paste the skill content directly.
Other Tools
For any LLM tool with a system prompt or custom instructions field, paste the skill content directly.
MCP Server
The NERO Embedded Wallets MCP server connects your AI coding assistant directly to the documentation.
| Tool | What it does |
|---|---|
search_docs | Search documentation and example projects |
get_doc | Fetch the full content of any doc page |
get_example | Fetch complete source code of an integration example |
get_sdk_reference | Fetch SDK types and hooks from the source repo |
Claude Code CLI
claude mcp add --transport http nero-embedded-wallets https://mcp.nerochain.ioOr add manually to your project's .claude/settings.json:
{
"mcpServers": {
"nero-embedded-wallets": {
"url": "https://mcp.nerochain.io"
}
}
}Cursor
Open Cursor Settings → Tools & Integrations → MCP and add:
{
"mcpServers": {
"nero-embedded-wallets": {
"url": "https://mcp.nerochain.io"
}
}
}Claude Desktop
Open your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server:
{
"mcpServers": {
"nero-embedded-wallets": {
"url": "https://mcp.nerochain.io"
}
}
}Restart Claude Desktop and ask: "Search NERO Embedded Wallets docs for React quick start" to verify.
Codex CLI / stdio-only agents
Use mcp-remote to bridge the HTTP endpoint:
{
"mcpServers": {
"nero-embedded-wallets": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.nerochain.io"]
}
}
}Static Docs (llms.txt)
If your AI tool doesn't support MCP, use the static documentation file. This gives your assistant the full NERO Embedded Wallets documentation as a single text file.
https://docs.nerochain.io/llms-full.txtFor tools that support the llms.txt spec:
https://docs.nerochain.io/llms.txtThe static file is a snapshot. Use the MCP server when possible for always-current docs.
Start Building
Once the skill and MCP are set up, try these prompts:
- "Add NERO Embedded Wallets to my React app with Google login."
- "Set up social login wallets in my Next.js app."
- "Integrate NERO MPC SDK with account abstraction and gasless transactions."
- "Why are my users getting different wallet addresses after changing the login method?"
Use planning mode (where available) for your initial prompt. Review the plan before generating code — this catches architecture mistakes early and avoids config errors that would change wallet addresses in production.