MCP 服务器

opointo

com.opointo/opointo
设计与创意 开发者工具 公开且可连接 MCP 2026-07-28

此 MCP 可以做什么

Provides React Native and Expo UI components, runtime guidance, and recipes for emitting, installing, updating, and verifying mobile app screens and projects.

add_screen
Add a screen to an app
Needs a subscription. Adds one screen designed in the App Designer 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. Without it, a self-contained screen file for any Expo app.
只读 幂等
输入模式
{'type': 'object', 'required': ['appId'], 'properties': {'tab': {'type': 'string', 'description': "nest it in this tab's stack; omit to place it where the design does"}, 'appId': {'type': 'string', 'description': 'the share code from "Send app to agent"'}, 'screen': {'type': 'string', 'description': "the new screen's name in that design"}, 'manifest': {'type': 'object', 'description': 'the parsed .opointo/files.json'}, 'componentName': {'type': 'string', 'description': "only to add a second copy of a screen; omit for the export's name"}}}
check_snippet
Check code for blank-render bugs
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 checks a whole emitted project.
只读 幂等
输入模式
{'type': 'object', 'required': ['code'], 'properties': {'code': {'type': 'string', 'description': 'the TSX to check'}}}
emit_app
Build an app from a design
Needs a subscription. Turns an App Designer design 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 line and ordered steps with a check each. Pass `step` for one step in full, which does not count against the daily allowance.
只读 幂等
输入模式
{'type': 'object', 'required': ['appId'], 'properties': {'page': {'type': 'number', 'description': 'for step write or review; each page names the next'}, 'step': {'type': 'string', 'description': 'a step id from the recipe, or "review" for the screen list'}, 'appId': {'type': 'string', 'description': 'the share code from the App Designer\'s "Send app to agent", e.g. "34ca4babb2"'}, 'override': {'type': 'boolean', 'description': 'emit even with screens flagged not ready; ask the customer first'}}}
find_component
Find a 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 renders the real system control.
只读 幂等
输入模式
{'type': 'object', 'properties': {'need': {'type': 'string', 'description': 'e.g. "a progress bar for an upload"'}, 'category': {'enum': ['controls', 'chrome', 'surfaces'], 'type': 'string'}}}
get_app_setup
Get the 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_app already has all three wired.
只读 幂等
输入模式
{'type': 'object', 'required': ['topic'], 'properties': {'topic': {'enum': ['providers', 'theme', 'rules'], 'type': 'string'}, 'platform': {'enum': ['ios', 'android'], 'type': 'string', 'description': 'rules only'}}}
get_component
Get a 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 rendering blank.
只读 幂等
输入模式
{'type': 'object', 'required': ['slug'], 'properties': {'slug': {'type': 'string', 'description': 'e.g. "button"'}, 'platform': {'enum': ['ios', 'android'], 'type': 'string', 'description': 'only the rules that hold there'}}}
install_component
Install a 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 needs and its runtime rules. A backend recipe's id, such as "supabase", adds that integration: its files and the per-app wiring an export writes.
只读 幂等
输入模式
{'type': 'object', 'required': ['slug'], 'properties': {'slug': {'type': 'string', 'description': 'e.g. "button", or a recipe id such as "supabase"'}}}
propose_app
Propose an app design
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 App Designer as a new, unsaved design. The person sees every screen and the navigation, changes what they like, and hands it back for emit_app. Each problem comes back with its path and a fix. dryRun checks without making a link; format: true returns the format and every block.
输入模式
{'type': 'object', 'properties': {'app': {'type': 'object', 'description': 'The design: { name, tabs: [{ screenId, label }], screens: [{ id, name, composition: { screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } } }], onboardingScreenIds: [], pushed: [{ screenId, fromScreenId, presentation }], theme? }. A node is { id, slug, props }: slug is "wireframe:<block>" such as "wireframe:list-row" (a list whose rows open one screen is one row block with repeats: "true" and its sample rows in rows: [{ title, ... }]) or a component from find_component, and a content node opens a screen with navigate: { to, presentation } beside its props. A top bar is header: { id, slug: "header", props: {} }, titled by the screen\'s name; a sheet has none. entryScreenId is only for a splash screen before the tabs. Tab icons, titles and composition metadata are set by the builder.'}, 'dryRun': {'type': 'boolean', 'description': 'check the design and report, without making a link'}, 'format': {'type': 'boolean'}}}
propose_screen
Propose a screen design
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 App Designer as a new, unsaved design the person can change. Each problem comes back with its path and a fix. dryRun checks without making a link; format: true returns the format. For a whole app with navigation, propose_app is the matching tool.
输入模式
{'type': 'object', 'properties': {'dryRun': {'type': 'boolean', 'description': 'check the screen and report, without making a link'}, 'format': {'type': 'boolean'}, 'composition': {'type': 'object', 'description': 'One screen: { name, screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } }. A node is { id, slug, props }: slug is "wireframe:<block>" or a component from find_component.'}}}
update_components
Update supplied 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 change that needs a code edit rather than a copy.
只读 幂等
输入模式
{'type': 'object', 'required': ['manifest'], 'properties': {'page': {'type': 'number', 'description': "only when the answer's page.next asks for it"}, 'current': {'type': 'array', 'items': {'type': 'object', 'required': ['path'], 'properties': {'sha': {'type': 'string'}, 'path': {'type': 'string'}, 'missing': {'type': 'boolean'}}}, 'description': "only when a split-unverified blocker asks: each named file's hash, from its command"}, 'manifest': {'type': 'object', 'description': 'the parsed .opointo/files.json (the object or its files array)'}, 'acceptSplit': {'type': 'array', 'items': {'type': 'string'}, 'description': 'only once the customer agreed: the paths split-customer-edited blockers name'}}}
verify_app
Verify an emitted app
Needs a subscription. Checks an emitted app before it is built: missing files, altered copy-verbatim files, absent packages, the config merge expo-router needs, and whether the installed Xcode can build the project. Takes the files written with byte sizes, package.json dependencies, project config and toolchain versions.
只读 幂等
输入模式
{'type': 'object', 'required': ['files'], 'properties': {'appId': {'type': 'string', 'description': 'the share code given to emit_app; `appId` in .opointo/files.json'}, 'files': {'type': 'array', 'items': {'type': 'object', 'required': ['path'], 'properties': {'sha': {'type': 'string', 'description': 'optional; when sent, the byte check is skipped'}, 'path': {'type': 'string'}, 'bytes': {'type': 'number', 'description': 'size in bytes on disk as `wc -c` reports, not the character count'}}}, 'description': 'each file written, the hidden .opointo/files.json included: { path, bytes }, path from the project root'}, 'config': {'type': 'object', 'properties': {'icon': {'type': 'string', 'description': 'app.json'}, 'main': {'type': 'string', 'description': 'package.json "main"'}, 'scheme': {'type': 'string', 'description': 'app.json'}, 'plugins': {'type': 'array', 'items': {'type': 'string'}, 'description': 'app.json'}, 'moduleSuffixes': {'type': 'array', 'items': {'type': 'string'}, 'description': 'tsconfig compilerOptions'}, 'supportsTablet': {'type': 'boolean', 'description': 'app.json ios'}, 'monochromeImage': {'type': 'string', 'description': 'app.json android.adaptiveIcon'}, 'nativeModulesDir': {'type': 'string', 'description': 'package.json expo.autolinking; omit if unset'}, 'userInterfaceStyle': {'type': 'string', 'description': 'app.json'}}}, 'toolchain': {'type': 'object', 'properties': {'xcode': {'type': 'string', 'description': '`xcodebuild -version`, e.g. "26.2"; omit without Xcode'}, 'expoSdk': {'type': 'string', 'description': 'the INSTALLED expo version, e.g. "56.0.15" (`npm ls expo`)'}, 'enableSceneSupport': {'type': 'boolean', 'description': 'app.json expo-build-properties ios.enableSceneSupport'}, 'expoBuildProperties': {'type': 'string', 'description': 'the INSTALLED expo-build-properties version; omit if absent'}}}, 'dependencies': {'type': 'array', 'items': {'type': 'string'}, 'description': "package.json dependencies' keys"}}}
已更改
propose_screen
2026年10月5日 02:42
已更改
propose_app
2026年10月5日 02:42
已更改
verify_app
2026年10月5日 02:42
已更改
update_components
2026年10月5日 02:42
已更改
install_component
2026年10月5日 02:42
已更改
add_screen
2026年10月5日 02:42
已更改
emit_app
2026年10月5日 02:42
已移除
list_components
2026年10月3日 02:49
已移除
get_theme_tokens
2026年10月3日 02:49
已移除
get_step
2026年10月3日 02:49
已移除
get_rules
2026年10月3日 02:49
已移除
get_provider_tree
2026年10月3日 02:49
已移除
emit_screen
2026年10月3日 02:49
已更改
propose_screen
2026年10月3日 02:49
已更改
propose_app
2026年10月3日 02:49
已更改
verify_app
2026年10月3日 02:49
已更改
update_components
2026年10月3日 02:49
已更改
install_component
2026年10月3日 02:49
已更改
add_screen
2026年10月3日 02:49
已更改
emit_app
2026年10月3日 02:49
已添加
get_app_setup
2026年10月3日 02:49
已更改
check_snippet
2026年10月3日 02:49
已更改
get_component
2026年10月3日 02:49
已更改
find_component
2026年10月3日 02:49
已添加
propose_screen
2026年10月1日 02:42
已添加
propose_app
2026年10月1日 02:42
已更改
get_step
2026年10月1日 02:42
已更改
verify_app
2026年9月29日 02:48
已添加
install_component
2026年9月27日 02:40
已添加
emit_screen
2026年9月27日 02:40