Yellow SDK MCP
Build with Yellow SDK inside your AI coding tool.
Yellow SDK MCP connects tools like Claude Code, Codex, Cursor, Windsurf, and VS Code Copilot to Yellow SDK knowledge. Ask your AI tool to find the right SDK call, explain a flow, create a starter app, or review a migration while you stay in your project.
You do not need to clone the Nitrolite repository. Run it from npm:
npx -y @yellow-org/sdk-mcp@^1
What It Provides
| Builder need | How MCP helps |
|---|---|
| Start a new app | Create TypeScript or Go starter code for transfer, app-session, and AI-agent flows. |
| Find the right call | Search Yellow SDK methods, types, and examples without reading every page first. |
| Understand a flow | Ask for plain-language help with channels, app sessions, signing, settlement, and protocol terms. |
| Check a migration | Review codemod leftovers, old 0.5.3 helper chains, imports, and native v1 replacements. |
| Need wire-level details | Look up v1 RPC methods when you are building a thin proxy, debugger, or non-SDK integration. |
Most builders only need the setup command and natural-language prompts in their AI tool. The exact tool names are listed later for teams that want to be more explicit.
Setup
Claude Code
claude mcp add --transport stdio nitrolite -- npx -y @yellow-org/sdk-mcp@^1
Then run /mcp inside Claude Code and confirm nitrolite is connected.
Codex
codex mcp add nitrolite -- npx -y @yellow-org/sdk-mcp@^1
Claude Desktop
Add this to Claude Desktop's MCP config, then restart Claude Desktop:
{
"mcpServers": {
"nitrolite": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@yellow-org/sdk-mcp@^1"]
}
}
}
Cursor
Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects:
{
"mcpServers": {
"nitrolite": {
"command": "npx",
"args": ["-y", "@yellow-org/sdk-mcp@^1"]
}
}
}
Windsurf
Add this to ~/.codeium/windsurf/mcp_config.json, then refresh MCP servers in Windsurf:
{
"mcpServers": {
"nitrolite": {
"command": "npx",
"args": ["-y", "@yellow-org/sdk-mcp@^1"]
}
}
}
VS Code and GitHub Copilot
Create .vscode/mcp.json in your workspace, or add it from the command palette with MCP: Add Server:
{
"servers": {
"nitrolite": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@yellow-org/sdk-mcp@^1"]
}
}
}
You can also add it from the terminal:
code --add-mcp '{"name":"nitrolite","type":"stdio","command":"npx","args":["-y","@yellow-org/sdk-mcp@^1"]}'
Try It
After setup, ask your AI coding tool questions like:
Use Yellow SDK MCP to build a minimal TypeScript transfer app.
Find the right Yellow SDK calls to create, fund, and close an app session.
Review my 0.5.3 migration TODOs and check whether each import belongs in @yellow-org/sdk or @yellow-org/sdk-compat.
Tool Reference
| Need | MCP surface |
|---|---|
| Find SDK calls and types | search_api, lookup_method, lookup_type |
| Check imports | validate_import |
| Explain protocol concepts | explain_concept, protocol resources |
| Inspect v1 wire methods | lookup_rpc_method, get_rpc_method |
| Create starter code | scaffold_project |
| Start guided workflows | create-channel-app, migrate-from-v053, build-ai-agent-app prompts |
For Contributors
The npm package ships with a release-time content snapshot, so normal users can run it without a repo clone. If you are changing the MCP server itself, use the local source workflow in the Nitrolite monorepo:
cd sdk/mcp
npm install
npm run build
npm run start