Native MCP· Overview

Native MCPGet started

Live

Native MCP

Give your AI assistant Native brand context and tools for social posts, assets and Meta ads, with guides for ChatGPT, Claude and Grok.

Native’s Model Context Protocol (MCP) server gives an assistant a way to read your brand and work in Native from a conversation. Your assistant handles the conversation; Native supplies the brand voice, products, pictures, drafts, publishing state and performance data.

One server, your Native account

#

Remote MCP server URL

https://mcp.native.no/mcp

The connection uses Streamable HTTP and OAuth. Your assistant opens Native’s sign-in flow. You do not need a Native API key, a local server or a dependency install. See Quickstart.

What you can do

#
WorkflowWhat happens in NativeGuide
Social postsGenerate drafts, edit copy and pictures, review, schedule and check publishing results.Social posts
Blog postsRead brand context and source material. The assistant drafts the article in the conversation; publishing needs your CMS.Blog posts
NewslettersNewsletter tools in this release cover Native lists, signup settings, saved drafts and reviewed delivery. Awaiting public deployment; check the authenticated tool list.Newsletters
Meta adsGenerate and review creatives. Publishing and spend controls require the corresponding tools and workspace access.Ad creation
Images and productsFind brand library assets, upload media and use product context in content.Assets and products
PerformanceRead social analytics and, where available, Meta ad results.Analytics

A Native post is a social publishing object. A newsletter is a separate saved email draft and delivery workflow. The new newsletter MCP tools are awaiting deployment and require brand-admin access and sending readiness. Blog publishing still needs your CMS; drafting an article in chat does not publish it.

How the assistant works with Native

#
  1. You connect the assistant through Native’s OAuth sign-in. Native identifies your account and permissions.
  2. The MCP host reads the tools available to your signed-in connection. Each tool describes its purpose, arguments and effect.
  3. You describe the task. The assistant chooses the correct brand, reads relevant Native context and uses the appropriate tool within your request.
  4. Native checks access, validates the input and performs the action. It returns saved data, state, identifiers and app links to the assistant.
  5. The assistant explains that result and follows background work when needed. You can open the same saved object in Native to review or continue.

For example, “write a newsletter” can produce a saved draft when newsletter tools are available. “Send that newsletter” needs a specific revision, reviewed recipients, the prepared sender and explicit approval. The connector provides access to actions; connecting alone does not authorize every action or make missing email setup ready.

Choose your assistant

#

Give an assistant the right context

#

Every guide has a View as Markdown action and a .md address. The assistant guide explains tool selection, brand discovery, background jobs and publishing checks. The site’s llms.txt indexes every guide, and llms-full.txt contains all the pages.

Building a product on Native?

#

These guides are for an assistant acting as a signed-in Native user. The Native API covers a partner backend running Native for its customers. The Norn API covers ranked content ideas. Both API sections describe previews; their client credentials setup is separate from signing in to this connector.

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