# Connect Native to ChatGPT Source: https://docs.native.no/mcp/chatgpt > **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. Add Native to ChatGPT with OAuth, enable it in a conversation and use your brand’s content tools. The same Native connection serves all supported workflows; newsletters do not need a second assistant connector. The newsletter tools in this release await public deployment. Once they appear on your signed-in connection, use [Newsletter setup](https://docs.native.no/mcp/newsletter-setup), [Contacts](https://docs.native.no/mcp/newsletter-contacts) and [Sending](https://docs.native.no/mcp/newsletter-sending). A provider mailbox or business sending domain is configured separately in Native. Connect Native from ChatGPT on the web, then use it in a conversation. Custom MCP connections follow your ChatGPT workspace’s permissions. The name of the connection area can vary as ChatGPT updates its interface. ## Add the connection 1. Open ChatGPT’s **Plugins** area and choose the plus button, then **Add custom MCP server**. If your account offers Native in its app directory, you can use that listing’s connect flow instead. 2. Name the connection **Native** and enter the server URL below. 3. Choose **OAuth** authentication. Finish the sign-in flow with the Native account that has access to your brand. Native does not require an API key for this connection. 4. Complete ChatGPT’s connection review and create the plugin. Install it in the personal or workspace area where you will use it. 5. Start a conversation, type **@** and select Native. If tools do not appear, open the connection’s details to refresh its tool list. Server URL: ```text https://mcp.native.no/mcp ``` Use the account’s current connection UI if its labels differ. OpenAI maintains the [custom MCP setup guide](https://developers.openai.com/api/docs/guides/custom-mcp-server). Your workspace administrator controls whether adding and using a custom connection is allowed. ## Check the connection ```text Use Native to show which workspaces and brands I can access. Do not create or schedule anything. ``` A successful result lists the Native workspaces your signed-in account can reach. Next, choose the brand and follow [Your first Native conversation](https://docs.native.no/mcp/quickstart). ## Make useful requests - “For the brand I selected, draft three LinkedIn posts about our new service. Leave them as drafts.” - “Use our Native voice and product information to prepare a newsletter draft in this chat.” - “Read our Native publishing calendar and tell me which days next week have no posts.” ChatGPT decides whether to render Native’s interactive calendar or preview. The tool result also provides text and, where available, an `appUrl`. A missing card alone does not mean the tool failed. ## Manage access Use the connection’s settings in ChatGPT to refresh tools, control available tools or disconnect Native. Disconnecting the assistant does not withdraw posts already scheduled in Native or pause live ads. Use the appropriate Native workflow to change those. For an expired sign-in, missing brand or refused write, see [Troubleshooting](https://docs.native.no/mcp/troubleshooting). This guide covers ChatGPT’s user connection; it does not configure an OpenAI API integration.