Most AppNatively MCP problems have a quick fix. If a result misses, give the assistant a more specific follow-up. If it reports an error, the table below says what it means. If it can’t connect, reconnect it or use a manual token. Nothing the AI does reaches your users until you publish, so there’s always time to fix it.
What if the AI’s result isn’t what I wanted?
- The prompt was vague. “Make it better” leaves a lot open. See Write prompts that get the screen you want.
- The prompt asked for conflicting things. Requests that pull two ways at once tend to produce a compromise instead of either.
- It worked on the wrong app or page. Name both in your prompt.
To recover:
- Describe the correction. If the result is close, a short follow-up – “the button is too small,” “wrong image” – is usually fastest.
- Ask it to reverse the change, then try again with more detail. See Undo an AI change you don’t want.
- Fix fine detail by hand. For exact spacing or one precise tweak, the App Editor is often quicker. See Edit screens and components by hand.
What do the AI’s error messages mean?
Assistants often put errors in their own words, so look for the gist rather than the exact wording.
| What you might see | What it means | What to do |
|---|---|---|
| “This app changed while the tool was running. Read the current state and try again.” | Someone else – you in the App Editor, or another tab – saved a change at the same moment. | Nothing was lost. Ask the assistant to try again; it re-reads the app first. |
| “Too many requests — please slow down and try again shortly.” | The assistant made a very large number of changes in a short time. | Wait a minute, then ask it to continue. |
| “Validation failed” | The change would have left the app in a state the App Editor can’t open, so it was refused and nothing was saved. | Ask the assistant to try a different way. If it keeps happening on one app, contact support. |
| An error about the website or a plugin | It tried to use your products, listings or posts, but your website isn’t connected or the plugin is switched off. | See Fix a failing or dropped connection. |
Why don’t my images show up?
The assistant can use images from your media library or any public link starting with https://. It can’t search stock-photo sites, and it can’t use a link that needs a login. Upload the image to your media library first, then ask the assistant to use it.
Why can’t my AI assistant connect?
- It worked before, then stopped. Its access may have been revoked, your password reset, or – for a manual token – the token expired after 90 days. Connect it again, or generate a new token.
- It can’t find your app. Check you’re signed in to the right AppNatively account under Connected apps, and name the app exactly in your prompt.
- Your client can’t sign in at all. Use a manual token instead – see Use a manual token with the AppNatively MCP server.
- The setup steps don’t match your client. Check the guide for Claude, ChatGPT, or Cursor and VS Code.