Skip to content

AI Tool Usage Guide

When developing with Cursor, Claude Desktop, VS Code, and other AI tools, add MCP config in your business project so the Agent can learn from the docs.

What we provide / What you do

RoleContent
Open Platform (us)Docs site, llms.txt, MCP config sample, official Skill
You (Cursor example)Confirm config path & layout → add .cursor/mcp.json → confirm mos-developer-docs in MCP panel → add Skill
Your project                         Open Platform
──────────                          ─────────
.cursor/mcp.json          ──MCP──►  https://developer.mosapp.app/llms.txt
.cursor/skills/                       https://developer.mosapp.app/guide/sdk.html
  mos-developer-docs/SKILL.md

Integrate MCP in your project (Cursor example)

1. Config path (Cursor)

Before adding MCP config, confirm where the file lives:

PurposePath
Project MCP (recommended).cursor/mcp.json at project root
Global MCP (all projects)~/.cursor/mcp.json

In Cursor, use Settings → MCP to check status; the config file is .cursor/mcp.json above.

Prepare this structure at the chosen path (next step writes MCP config into .cursor/mcp.json):

text
your-miniapp-project/
├── src/
└── .cursor/
    ├── mcp.json                 # required: MCP config
    └── skills/
        └── mos-developer-docs/
            └── SKILL.md         # see Skill section below

3. Add MCP config

Copy the following into .cursor/mcp.json (recommended to commit to Git):

json
{
  "mcpServers": {
    "mos-developer-docs": {
      "command": "npx",
      "args": ["-y", "mcp-fetch-server"],
      "url": "https://developer.mosapp.app/llms.txt"
    }
  }
}

If you already have other MCP servers, only append the mos-developer-docs entry. Requires Node.js on your machine (npx will fetch mcp-fetch-server on first use).

Windows: if npx fails to start, change command / args to:

json
{
  "mcpServers": {
    "mos-developer-docs": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "mcp-fetch-server"],
      "url": "https://developer.mosapp.app/llms.txt"
    }
  }
}

You can also verify against the hosted file: mos-developer-docs.mcp.json

4. Verify

Open your business project in Cursor, confirm mos-developer-docs is connected in the MCP panel, then ask the Agent:

Please fetch https://developer.mosapp.app/llms.txt and summarize the mini app docs structure.

For doc pages use fetch_txt; URLs must include the .html suffix, e.g. https://developer.mosapp.app/guide/login.html.

Official docs base URL: https://developer.mosapp.app

Recommended reading order:

  1. https://developer.mosapp.app/llms.txt — full index (MCP fetch)
  2. Doc page URLs must include .html — e.g. https://developer.mosapp.app/guide/sdk.html

Skill

Skill provides doc URLs and reading order; MCP fetches page content.

  1. Copy the full text of mos-developer-docs.skill.md and save as .cursor/skills/mos-developer-docs/SKILL.md
  2. Confirm path: .cursor/skills/mos-developer-docs/SKILL.md
  3. Commit to Git for the team

Prompt you can paste into project Rules

text
This project integrates with the MosApp Open Platform. Docs root: https://developer.mosapp.app
1. Use MCP fetch to load https://developer.mosapp.app/llms.txt for the index
2. Then fetch specific pages, e.g. https://developer.mosapp.app/guide/sdk.html
3. Do not invent APIs; confirm with the user if something is not in the docs