# Other MCP clients Source: https://docs.native.no/mcp/other-clients > **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 another assistant or coding client using Native’s remote HTTP endpoint and supported OAuth sign-in. ## What the client needs - Remote MCP over **Streamable HTTP**. - OAuth discovery and a compatible browser sign-in flow. Support for MCP does not by itself establish OAuth compatibility. - Tool discovery through `tools/list`, with the ability to refresh it after permissions or server capabilities change. - A way to present tool results and collect the user’s decisions for changes and publishing. Interactive MCP app views are optional. Server URL: ```text https://mcp.native.no/mcp ``` Add a remote HTTP server in the client’s MCP settings and complete Native’s OAuth flow. Use the client’s documented configuration format rather than copying another assistant’s JSON. Do not choose a local stdio command for this hosted endpoint. ## Clients with extra setup Some coding clients require a registered public OAuth client id or a fixed callback port. Native’s [MCP integration page](https://native.no/integrations/mcp) maintains its client-specific setup cards, including Codex. Follow the card for your client; do not reuse another client’s OAuth identity or redirect settings. ## Check the connection Start with a read: ask for Native workspaces, choose one, then ask for its brands. If a client cannot authenticate, change the connection configuration before attempting content tools. A preview card is optional; a successful data result is enough to proceed. ## Help the assistant use Native well Point the assistant to [the Native assistant guide](https://docs.native.no/mcp/agent-guide) or give it `https://docs.native.no/mcp/agent-guide.md`. The guide explains supported workflows and how to check results. The authenticated server’s tool schemas remain the authority for exact inputs and availability.