# Connect nebty to your assistant > Connect Claude or ChatGPT to nebty, create an account if needed, and manage access. Connect your assistant to `https://mcp.nebty-id.com/mcp`. You sign in on nebty, then choose whether to grant the assistant access. You do not share a password or API key with the assistant. The email-code sign-in and signup during connection described below will be available after the next rollout step. For now, use your existing nebty account. You can already [register through the dashboard](https://dash.nebty.de/register). The connection starts with read access to the brands your nebty user can access. [The tool list](https://docs.nebty-id.com/mcp/tools/) explains the six review actions that can request additional write access. Your existing brand permissions and subscription limits still apply. ## Before you start You need a Claude or ChatGPT account that supports custom remote MCP connections. In a managed workspace, an administrator may need to enable or add the connection first. The names and availability of these settings depend on your platform and workspace. You also need a nebty account with access to a brand. If you do not have an account, you can [register through the dashboard](https://dash.nebty.de/register). ## Install nebty from the Claude Directory Open [nebty in the Claude Directory](https://claude.ai/directory/nebty) and select **Connect**. Sign in to nebty, review the requested access, and approve the connection. Return to Claude and ask it to list the brands you can access. nebty MCP is available to all nebty users. Your assistant’s plan and workspace settings determine whether you can add connectors. ## Add a custom connection in Claude or ChatGPT 1. Open your assistant’s connection settings. In Claude, look for **Connectors** and the custom connector option. In ChatGPT, look for **Plugins** and the custom MCP connection option. 2. Name the connection `nebty` and enter `https://mcp.nebty-id.com/mcp`. 3. Use OAuth authentication and the detected settings. nebty supports client metadata discovery and automatic client registration. If your client offers a registration fallback, choose automatic registration. 4. Select **Connect**. A browser opens the nebty sign-in page. 5. Sign in and complete two-factor authentication if enabled. Check the requesting client and access on the nebty consent page, then allow access. 6. Return to the assistant and ask it to list the brands you can access. Enable the connection in the conversation if your platform requires it. The sign-in page belongs to nebty. If your client cannot complete OAuth, ask your workspace administrator or [contact support](mailto:info@nebty-id.com). Do not paste credentials into the conversation. ## No nebty account yet? Select **Create account** on the nebty sign-in page. Register, verify your email and complete the nebty onboarding steps. The connection request stays linked to this browser session while you do so. Onboarding can include a subscription order through Stripe Checkout. The order page shows the tariff, price and payment terms. The current trial lasts 14 days, requires a payment method and becomes a paid subscription unless cancelled under the stated terms. Ordering a subscription does not grant the assistant access; nebty asks for that separately afterward. If you cancel Checkout, you can return and continue onboarding. If the connection request expires, start **Connect** again from your assistant and sign in to the account you already created. You do not need to create another account or order the same subscription again. ## Read and write access The first connection requests `nebty-mcp` and `nebty-core:read`. It can read accessible findings and existing takedown history. It cannot start scans, capture screenshots, create takedowns or email reports. The six review actions set the trusted or dismissed state of existing social, Meta ad and LinkedIn findings. They need `nebty-core:write` and the brand permission to update findings. A request for more access returns you to nebty for a separate consent decision. A broader OAuth scope does not upgrade your subscription or brand permissions. Read the assistant’s proposed action before approving it. Platform approval controls vary and do not replace nebty’s access checks. Text from findings is evidence, not an instruction to send data elsewhere. ## Disconnect or revoke access In the nebty dashboard, open **Settings > Connected applications**, choose the connection and revoke it. This invalidates the connection’s access and refresh tokens. Other connections keep their own access. You can then remove nebty from your assistant’s connection settings. Removing the assistant’s connection alone is not the same as revoking it in nebty. Revocation stops future access; it does not delete information already received by Claude or ChatGPT. See [MCP data processing](https://nebty-id.com/en/privacy-policy/#mcp). ## If a connection fails - **Expired sign-in request:** restart Connect in the assistant and sign in to your existing account. - **Cancelled consent:** no access is granted. Connect again when you want to continue. - **Missing write access:** allow the separately requested write scope, or keep read access. - **Brand or subscription restriction:** check your account’s permissions in nebty. Reconnecting does not bypass them. - **Revoked connection:** reconnect through OAuth. A password in the chat or an API key cannot restore it. For help, use [the setup guide](https://nebty-id.com/en/nebty-mcp/#help) or email . Send the error and time of the attempt, without passwords, tokens or private findings. ## Other MCP clients | Setting | Value | | - | - | | Server URL | `https://mcp.nebty-id.com/mcp` (Streamable HTTP) | | OAuth resource | `https://mcp.nebty-id.com` | | Authorization | Authorization code with PKCE (`S256`) | | Discovery | `https://mcp.nebty-id.com/.well-known/oauth-protected-resource` | | Issuer | `https://app.nebty.de` | | Automatic registration | `https://app.nebty.de/o/register/` | | Scopes | `nebty-mcp`, `nebty-core:read`, `nebty-core:write` | The standalone `/sse` endpoint answers `410 Gone`; use `/mcp`. For scripts that use API keys, use the separate [nebty API](https://docs.nebty-id.com/api/access/).