iPadian

Install iPadian in your MCP client

iPadian is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

1. Locate your client's MCP config file.
   • Cursor: ~/.cursor/mcp.json
   • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
   • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
   • VS Code: Settings → Extensions → MCP
   • Windsurf: Settings → MCP Servers
2. Add iPadian to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
3. Restart your client so it picks up the new server.
4. Verify — ask the assistant to list available tools; iPadian's tools should appear.

{
  "mcpServers": {
    "ipadian": {
      "command": "npx",
      "args": [
        "-y",
        "@ipadian/mcp-server"
      ],
      "note": "Replace with the actual package name from the server's documentation."
    }
  }
}

Tools exposed by iPadian

Once installed, iPadian exposes the following MCP tools to your AI assistant. Each tool can be called directly by the assistant whenever its capability is relevant to your prompt.

• open_ipadian

  Open the iOS-style iPadian home screen with app icons, a dock, App Store, Create, and My Apps. After opening, briefly explain in chat that users can tap apps, browse App Store for ready-made apps or choose Create for examples, or ask your assistant to build and revise their own web app. Explain that Save locally keeps app code in this browser, not runtime progress. This tool cannot read the local library.

• preview_app

  Render a complete self-contained HTML app in iPadian. Include inline CSS and JavaScript; external requests, libraries, browser storage and navigation permissions are unavailable inside the sandbox. Keep the same id when revising an app. This returns an unsaved draft; only the user’s Save locally button stores it. Never claim the app was saved or published.

Transport

iPadian supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

More build.protocol_tooling.mcp MCP servers

Other Model Context Protocol servers in the same space as iPadian. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

• 4chems Platform — IUCLID, CHESAR & QSAR Toolbox hosting

  Remote MCP server for 4chems hosted IUCLID, CHESAR and QSAR Toolbox: onboarding, inquiries, admin.

• UTMKit

  UTM-tagged short links with naming rules, QR codes and click analytics, from your AI.

• Shipfound

  Growth engineer for your coding agent: site fixes, content PRs, indexing and AI search tracking.

• TANDIU AI infrastructure data

  Read-only LLM API prices, benchmarks, price index, GPU self-hosting sizing and cloud agent data.

• Askli Customer Research

  Run interviews with real customers and retrieve evidence-backed product findings.

• Uviqora

  Find and book people for short on-site tasks in Switzerland. Free public pilot, early stage.

• 1NFER Inference Discovery

  Inspect 1NFER models, crypto funding terms and task cost without keys or paid calls.

• SuperDB

  Backend brasileiro (Postgres, login, storage): a IA cria tabelas, liga RLS e roda SQL no projeto.

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.