Native MCP· Troubleshooting

Native MCPFor AI assistants

Live

Troubleshoot the Native connection

Resolve sign-in, missing tools, generation and publishing failures using the result Native actually returned.

The assistant cannot connect

#
  • Check the exact server URL: https://mcp.native.no/mcp. Use the remote HTTP connector flow and OAuth.
  • Complete the browser sign-in using the Native account with the right workspace access. If the connection uses the wrong account or sign-in has expired, reconnect.
  • If your assistant or team blocks custom connectors, ask the workspace administrator to enable the connection. Native access and the assistant’s connector settings are separate controls.
  • For a coding client with a registered client id or callback port, follow its current Native integration card. A transport that can reach the URL may still lack a compatible OAuth setup.

A workspace, brand or tool is missing

#
SymptomNext step
Expected brand absentVerify the signed-in Native account, workspace membership and any discovery filters.
Tools changed or unavailableRefresh the connection’s tool list. Call only tools it currently advertises.
Ads tools absentCheck workspace ads access and server availability. A tool shown to another account may not be enabled for yours.
forbidden or insufficient_scopeThe account or token lacks access. Repeatedly approving a conversational request does not grant it.
writes_disabledThe server’s write mode blocks the change. Use the Native app or contact Native about the connection’s allowed capabilities.

Generation has not finished

#

Follow the returned identifier with get_post_batch_status, get_generation_job, get_ad_status or get_ad_pack_status. Ad renders can take minutes. Inspect stage, pending counts and per-item errors. Do not issue another create call simply because the first result is not ready.

If generation reports a plan allowance or configuration error, address that prerequisite. When a batch partly fails, keep the successful posts and explain the failed slots rather than recreating the whole batch.

A post will not publish

#
  1. Read get_profile for channel health and the tool error for the actual blocker.
  2. Check the selected destination, content requirements and current approval. A content edit after review may require fresh approval.
  3. For a disconnected social account, use create_connect_link and have the user complete the browser flow. Read the profile again afterwards.
  4. Read get_post_status and handle each platformResults item. Retry only failures covered by the user’s request; retain the links for destinations already published.

A write timed out

#

A timeout can occur after Native saved the change. Read current state before retrying, using the returned post, batch, creative or job id when available. Separate write calls are independent attempts and can duplicate drafts or work.

The preview is missing

#

Interactive views depend on the assistant client. Ask for a short summary and the returned Native appUrl. A view failure alone does not establish that generation, scheduling or publishing failed; use the corresponding status tool.

The request needs another service

#

Publishing a blog article requires a CMS. Native newsletter tools are implemented in this release but await public deployment; when absent, copy preparation does not save or send a newsletter. When present, they still require brand-admin access and configured delivery. See Blog posts and Newsletters.

A newsletter cannot send or its list changed

#

Read get_newsletter_setup and the saved draft. “Sending from your own domain is not available yet” is a service limitation; entering a reply-to does not verify a sender. A false live-delivery or readiness value requires the reported prerequisite to be resolved. For newsletter_changed, reread the current draft and recipient review before selecting or approving again. After a timeout or an UNKNOWN state, inspect the existing delivery instead of creating a replacement send. See Setup and Sending.

What to include when asking for help

#

Share the assistant client, Native workspace and brand, tool name, approximate time, error code and any returned post/batch/job/creative id. Include the Native app link when available. Keep access tokens, passwords and OAuth secrets out of support messages. Contact Native if reconnecting and checking the reported blocker do not resolve it.

Start with your Native account

Connect an assistant, choose your brand and ask for a first draft. Available tools follow your Native access.

Choose an assistant