Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.moca.network/llms.txt

Use this file to discover all available pages before exploring further.

Connect the Moca Network documentation MCP server to your IDE or AI assistant for real-time access to AIR Kit documentation, API references, and code examples. When you connect the MCP server, AI assistants can search the documentation directly to help you build faster and more accurately.

​
Connect your AI tools

Connect the Moca Network documentation MCP server to your preferred AI tool:
1

Get your MCP server URL

Your MCP server URL is: https://docs.moca.network/mcp
2

Add the Moca Network MCP server to Claude

  1. Navigate to the Connectors page in the Claude settings.
  2. Select Add custom connector.
  3. Add the Moca Network MCP server:
    • Name: MocaNetwork
    • URL: https://docs.moca.network/mcp
  4. Select Add.
3

Access the MCP server in your chat

  1. When using Claude, select the attachments button (the plus icon).
  2. Select the MocaNetwork MCP server.
  3. Ask Claude a question about Moca Network or AIR Kit.
See the Model Context Protocol documentation for more details.
You can also use the contextual menu on any page of the documentation to copy the MCP server URL or install it directly into Cursor or VS Code.

​
Setup with other agents

The Moca skill works with any tool that supports the Agent Skills standard, including Cursor, VS Code Copilot, Gemini CLI, OpenAI Codex, and more. Run: 
npx skills add https://docs.moca.network
The CLI detects your installed agents and places the skill in the correct directory for each one.

​
What the skill provides

FeatureDescription
Quick referencesSDK install (@mocanetwork/airkit), platform matrix, provider and wallet APIs, and REST credential endpoints
Decision guidanceAccount-only vs credential flows, embedded AIR login vs bring-your-own auth, and client vs server signing with Partner JWT
WorkflowsStep-by-step sequences for onboarding, issuance, verification, Issue on Behalf, and advanced flows like paymaster or session keys where relevant
Common gotchasInitialization and iframe setup, JWKS and JWT errors, polling issuance until credentials are on-chain, and schema or verification pitfalls
Verification checklistPartner ID, environment (sandbox vs production), chain allowlists, auth headers, and error handling before you ship

​
Static docs files

If your AI tool does not support MCP yet, you can use one of Moca Network’s static documentation files instead.
Static files are snapshots and may not include the latest updates. Use MCP when possible for always-current docs.

​
Which file should I use?

  • llms.txt — A curated overview of Moca Network. Use it to route an agent to the right docs, understand product structure, and choose the right integration path.
  • llms-full.txt — A full static snapshot of the documentation. Use it when your tool needs more exhaustive reference material in one file.

​
Setup with Cursor

1

Open docs settings

Go to Settings → Features → Docs.
2

Add the overview file

Click Add new doc and paste: https://docs.moca.network/llms.txt
3

Optionally add the full snapshot

If your agent needs deeper static reference coverage, add: https://docs.moca.network/llms-full.txt
4

Reference in chat

Use @docs → Moca in your AI chat to reference the documentation.

​
Setup with Claude Desktop

1

Download the overview file

Download the curated overview from: https://docs.moca.network/llms.txt
2

Optionally download the full snapshot

Download the full documentation snapshot from: https://docs.moca.network/llms-full.txt
3

Add to your project

Save one or both files in your project directory or another known location on your system.
4

Reference in chat

Drag and drop the file into your Claude Desktop chat, or use the attachment button to upload it. Claude will then have access to the uploaded Moca Network documentation context for that conversation.