Opainto MCP MCP server

The Opainto MCP server enables coding agents to generate, verify, and manage real Expo projects for iOS and Android. It allows agents to design native apps visually, export plain React Native source code, and utilize verified skeletons and components to ensure cross-platform compatibility and correct navigation wiring.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Opainto

MCP endpoint (Streamable HTTP)

https://opointo.com/api/mcp

Vendor documentation

What you can do with it

Generate a complete Expo project for iOS and Android from visual designs
Verify app structure and navigation wiring using built-in checks
Export plain React Native source code to a user's repository
Integrate with coding agents like Claude Code or Cursor

Tools advertised by the last live check:

find_component
get_component
check_snippet
get_app_setup
emit_app
add_screen
install_component
update_components
verify_app
propose_app
propose_screen

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http opainto-mcp https://opointo.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add opainto-mcp --url https://opointo.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable opainto-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "opainto-mcp": {
      "url": "https://opointo.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "opainto-mcp": {
      "type": "streamableHttp",
      "url": "https://opointo.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start opainto-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "opainto-mcp": {
      "type": "http",
      "url": "https://opointo.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http opainto-mcp https://opointo.com/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "opainto-mcp": {
      "url": "https://opointo.com/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "opainto-mcp": {
      "serverUrl": "https://opointo.com/api/mcp"
    }
  }
}

See all 957

Do you run Opainto MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing