# Your first Native conversation Source: https://docs.native.no/mcp/quickstart > **Live connector.** Sign in with your Native account. Available tools depend on account access, workspace features and server write settings. Newsletter MCP tools in this release await public deployment; their guides state the requirements. Blog copy preparation does not include CMS publishing. Connect Native, select a brand and create a social draft your assistant can help you review. ## Before you start Use an existing Native account with access to the workspace and brand you want to work on. Creating a draft requires the relevant Native plan allowance and write access. Publishing also requires a healthy connected social account. ## 1. Connect your assistant Follow the guide for [ChatGPT](https://docs.native.no/mcp/chatgpt), [Claude](https://docs.native.no/mcp/claude), [Grok](https://docs.native.no/mcp/grok) or [another MCP client](https://docs.native.no/mcp/other-clients). Add this URL and choose OAuth authentication: ```text https://mcp.native.no/mcp ``` Finish Native’s sign-in and consent flow, then enable the connection in your conversation. Paste the server URL into the connector settings; an ordinary chat message containing the URL does not establish a connection. ## 2. Choose a brand Try this: ```text Use Native to list my workspaces and brands. Let me choose the brand before making changes. ``` The assistant uses `get_workspaces` and `list_brands`. When more than one workspace or brand matches, choose one explicitly. It should then read `get_profile` and `get_brand_voice` for that brand. ## 3. Ask for a draft Example brief: ```text For Harbour Bakery, draft an Instagram post about our Saturday sourdough class. Use our Native brand voice and an existing product photo. The class is at 10:00 and costs NOK 650. Leave it as a draft for review. ``` The assistant finds a suitable product or picture, creates a Native social draft and reads the result. Generation may continue in the background. A returned job or batch id means work has started; it does not prove the pictures are ready. ## 4. Review the result Check the wording, facts, pictures and destination. A compatible assistant may offer an interactive preview. Use the returned `appUrl` to open the result in Native if a preview is unavailable. Ask for an edit: ```text Make the caption shorter and keep the price and booking details. Show me the updated draft. ``` ## 5. Choose when it goes out When you want the reviewed content to go out, name the post, destination and time with a timezone. The assistant records approval of the version you reviewed where required, then schedules or publishes within your request. A later content edit can require fresh approval. A scheduling request: ```text I approve this version of the sourdough class post. Schedule it to Harbour Bakery’s connected Instagram account on 14 November 2026 at 09:00 Europe/Oslo. ``` The assistant checks `get_post_status` and reports each destination separately. Scheduled means booked for later; a published URL is evidence that a destination is live. ## Keep going Use [Social posts](https://docs.native.no/mcp/social-posts) for a week of content, [Ad creation](https://docs.native.no/mcp/ads) for Meta creatives, or [Blog posts](https://docs.native.no/mcp/blog-posts) for longer copy. The [Newsletter guides](https://docs.native.no/mcp/newsletters) cover sender setup, contacts, saved drafts and sending with the newsletter tools awaiting deployment in this release.