Connect opointo and your agent gets 11 tools, among them add_screen, check_snippet, emit_app. It answers at https://opointo.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 26 September 2026; the last check, on 10 November 2026, succeeded.
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_screen | Needs a subscription. Adds one screen designed in the Architect to a project. With the project's .opointo/files.json it returns the screen file, the route that mounts it and the one line to register it, and never rewrites existing files. Wi Inputs: appId, screen, manifest, tab, componentName |
check_snippet | Scans TSX that uses these components for the mistakes that render nothing with no error: animated opacity on glass, the flex: 1 collapse, a clipped lens, a conditionally mounted surface. A read-only text scan, not a guarantee; verify_app ch Inputs: code |
emit_app | Needs a subscription. Turns a design from the Architect into a working Expo app: navigation, providers, tab bar, screens and the components they use. Returns a recipe for the current project: every file with its target path, one install lin Inputs: appId, override, step, page |
find_component | Finds the component for a UI need described in plain words, ranked, and says when this catalog ships nothing on purpose because the phone's own control is the right choice. Omit `need` to list every component with its purpose and whether it Inputs: need, category |
get_app_setup | How an app is set up so these components work and follow its theme, one topic at a time: the app-root providers in the order that works, the theme hooks and token scales, or the rules that hold across the whole catalog. An app built by emit Inputs: topic, platform |
get_component | Everything needed to write a correct call site for one component: props with types, defaults and allowed values, what draws on iOS and on Android, the providers it needs at the app root, its dependencies, and the runtime rules that stop it Inputs: slug, platform |
install_component | Needs a subscription, except for the free foundation components. Adds one component to an existing project: the files it and its dependencies need in install order with exact target paths, the single expo install line, the providers it need Inputs: slug |
propose_app | Your agent can design an app with you: send an app in opointo's design format (the AppSpec emit_app builds from) and get back a link that opens it in the Architect as a new, unsaved design. The person sees every screen, changes what they li Inputs: app, dryRun, format, into |
propose_screen | Your agent can design a single screen with you: send one screen in opointo's design format (the Composition add_screen builds from) and get back a link that opens it in the Architect as a new, unsaved design the person can change. into: as Inputs: composition, dryRun, format, into |
update_components | Needs a subscription. Reads the project's .opointo/files.json and returns only the opointo-supplied files that changed since export, so it works months later with no share code. Never touches the customer's own screens, and flags the rare c Inputs: manifest, current, acceptSplit, page |
verify_app | Needs a subscription. Checks an emitted app before a build: missing files, altered verbatim files, absent packages, expo-router's config merge, whether installed Xcode can build it, and whether a change needs a native rebuild. Inputs: appId, files, dependencies, config, toolchain |
Every block below points at https://opointo.com/api/mcp. Pick your client and copy.
claude mcp add --transport http opointo https://opointo.com/api/mcp
{
"mcpServers": {
"opointo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://opointo.com/api/mcp"]
}
}
}{
"mcpServers": {
"opointo": {
"url": "https://opointo.com/api/mcp"
}
}
}{
"servers": {
"opointo": {
"type": "http",
"url": "https://opointo.com/api/mcp"
}
}
}{
"context_servers": {
"opointo": {
"url": "https://opointo.com/api/mcp"
}
}
}{
"mcpServers": {
"opointo": {
"serverUrl": "https://opointo.com/api/mcp"
}
}
}{
"mcpServers": {
"opointo": {
"url": "https://opointo.com/api/mcp"
}
}
}name: opointo
version: 0.0.1
schema: v1
mcpServers:
- name: opointo
type: streamable-http
url: https://opointo.com/api/mcp{
"mcpServers": {
"opointo": {
"httpUrl": "https://opointo.com/api/mcp"
}
}
}{
"mcpServers": {
"opointo": {
"type": "http",
"url": "https://opointo.com/api/mcp"
}
}
}{
"mcpServers": {
"opointo": {
"url": "https://opointo.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fopointo.com%2Fapi%2Fmcp&type=streamable_http&id=opointo&name=opointo
It answered our last check on 10 November 2026 in 1535 ms. Over 4 checks since 26 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by opointo.com and served from opointo.com, the vendor's own domain: https://opointo.com/api/mcp.
11, as returned by the server's own tools/list on 16 November 2026: add_screen, check_snippet, emit_app, find_component, get_app_setup, get_component, install_component, propose_app, and 3 more.
It answered our last check on 10 November 2026 in 1535 ms. Over 4 checks since 26 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://opointo.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.opointo. Endpoint host: opointo.com. ARD identifier: urn:air:com.opointo:mcp:opointo.
First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.