# Connect Native to Claude Source: https://docs.native.no/mcp/claude > **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 as a remote Claude connector, sign in with OAuth and enable it in a conversation. ## Claude connector for social post drafts In Claude, open **Customize > Connectors**, choose **Add custom connector**, enter **Native** and the address below, then sign in to Native. Select a workspace and brand you can access. On Team and Enterprise, an administrator adds the connector before members sign in. Claude directory connector URL: ```text https://mcp.native.no/mcp/claude ``` Ask Claude to save a text-only draft or lay out a two-slide post with an existing brand photo, logo and typography. Open the returned post link to review the draft in Native. Reading, changing and undoing individual layers requires a brand with design editing enabled. Starting a design from a brief costs 50 Native tokens and requires your approval. ```text Use an existing photo from my brand library to lay out a two-slide draft. Put “Meet the team” on slide one and “Behind the scenes” on slide two. Save it in Native and give me the draft link. ``` ## General Native MCP connection Existing general Native MCP connections use the address below. 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. Use Native as a remote connector in Claude. The connection is hosted by Native, so you do not need a local MCP process or a Claude Desktop configuration file. ## Add the general connector 1. Open **Customize > Connectors** in Claude. 2. Choose **Add custom connector** from the add menu. Name it **Native** and enter the URL below. 3. Continue through the detected authentication settings. Use OAuth sign-in to your own Native account. If automatic client registration is offered, it can register the connection; you do not need to paste a Native API key or partner client secret. 4. Complete Native’s sign-in and consent flow. 5. In a conversation, open the **+** menu, then **Connectors**, and enable Native. Remote MCP server URL: ```text https://mcp.native.no/mcp ``` ## Using a team account On Claude Team and Enterprise, an owner or other authorized administrator first adds the remote connector in **Organization settings > Connectors**. Members then connect their own Native accounts. Follow [Claude’s current custom connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for the available settings in your plan. ## Check the connection ```text Use Native to list my brands. After I choose one, read its brand voice and connected social channels. Make no changes. ``` Once you have selected a brand, ask Claude for a [social draft](https://docs.native.no/mcp/social-posts), [Meta ad creative](https://docs.native.no/mcp/ads) or [blog outline](https://docs.native.no/mcp/blog-posts). Native’s tool availability follows your account, workspace and connection permissions. ## Previews and links Claude may render Native’s calendar, asset picker and post previews as interactive components. When a component is unavailable, the assistant can report the returned data and link to Native. Do not treat a missing component as evidence that a write did not happen. ## Disconnect or reconnect Manage the connection under **Customize > Connectors**. Reconnect when sign-in expires or the wrong Native account was selected. Removing the connector does not cancel Native’s existing scheduled posts or live ads. See [Troubleshooting](https://docs.native.no/mcp/troubleshooting) for tool and permission issues.