In brief: Every AI client connects to the same address, https://mcp.netnet.app/mcp, and signs in with your normal Net Net credentials; only the menu path differs.

Applies to: Anyone on an active trial or a paid plan whose AI tool supports remote MCP connectors.

See also: Connect Your Own AI to Net Net with the MCP Server explains what the connection is for, AI Access and Your Plan: Why MCP Needs a Paid Plan explains declined requests, and What to Ask Your AI About Your Net Net Workspace covers what to do next.

Every assistant connects to the same Net Net MCP server address, https://mcp.netnet.app/mcp, and every assistant authorizes the same way: you sign in with your ordinary Net Net credentials inside your AI tool, and no API key ever changes hands. What differs is where the setting lives and which plan you need on the provider's side, and it differs more than you would expect. Claude allows custom connectors on every tier including free. ChatGPT restricts them the most. Gemini, Perplexity, and Grok all added support during 2026 and are still moving.

The address you paste, every time, in every tool, is https://mcp.netnet.app/mcp.

For the thinking behind connecting the assistant you already use, and what that connection can and cannot reach, see Connect Your Own AI to Net Net with the MCP Server.

Connector settings are the fastest changing corner of the AI industry right now, so each section below links to the provider's own documentation. If a menu has moved since this was written, trust their page over ours.

Watch the walkthrough

If you would rather watch than read, this short video walks through connecting Claude to Net Net from start to finish: finding the custom connector setting, pasting the server address, signing in with your normal Net Net credentials, and enabling the connector inside a conversation. Everything it shows is written out below as well, so you can follow either one.

What is the same in every MCP setup

Whatever tool you use, the shape of the job is identical.

1. Confirm your Net Net workspace is on a trial or a paid plan. MCP is not available on the free tier, and Net Net declines the connection. See AI Access and Your Plan: Why MCP Needs a Paid Plan.
2. Find the custom connector setting in your AI tool. Every provider calls it something slightly different. Connectors, apps, custom apps, integrations.
3. Paste https://mcp.netnet.app/mcp as the server address.
4. Sign in when the Net Net login screen appears. Use your normal email and password. The connection then carries your role and your permissions, which are set out in User Roles Explained: Owner, Admin, Lead, and Member.
5. Turn the connector on in the conversation where you want it. Several tools authorize a connector globally but still require you to enable it per chat, which is the single most common reason a working connection appears to do nothing.

Claude

Plan required: any, including Free. Claude is the most permissive of the group and the easiest place to try this.

For personal accounts, go to Settings → Connectors, choose Add custom connector, paste the address, and confirm. Claude then opens the Net Net sign in. Once authorized, use the + button inside a conversation and enable the connector for that chat.

On Team and Enterprise plans, only an Owner can add a custom connector, and they do it in Admin settings → Connectors. Members then go to their own Settings → Connectors to sign in to it individually. This is worth knowing before you go looking in a settings page that will not show you the button.

Custom connectors work in Claude on the web, in Claude Desktop, and in Cowork.

Official documentation: Get started with custom connectors using remote MCP

ChatGPT

Plan required: Pro for reading only, or Business, Enterprise, or Edu for full use. This is the most restricted of the five and the one to check before you promise a teammate it will work.

ChatGPT Plus does not currently support custom MCP connectors at all. ChatGPT Pro supports them for reading and fetching, which covers questions but not actions, and requires developer mode to be switched on under Settings → Apps → Advanced settings. Full support including the ability to write changes back is in beta on Business, Enterprise, and Edu plans.

On Business, an admin enables it under Workspace settings → Permissions & Roles → Connected Data before anyone can add a connector. On Enterprise and Edu the same admin step applies, and apps are switched off by default there rather than on.

This surface has been renamed and reworked repeatedly through 2026. Check OpenAI's page before you plan around it.

Official documentation: Developer mode and MCP apps in ChatGPT

Gemini

Plan required: Google AI Pro or Google AI Ultra. Custom MCP servers reach Gemini through Gemini Spark, which arrived in 2026 and is not on the free tier.

Connect from the Gemini web app rather than the phone. Open Settings & help at the bottom of the left navigation, then Connected Apps. If you do not see it, look under Personal Intelligence first. Find Custom apps for Spark, choose Add a custom app, and paste the address.

Once the connection is made in the web app, it works from the Gemini mobile app as well.

Two honest caveats. Availability has been rolling out by region rather than everywhere at once, so the option may simply not be present in your account yet. And this is the newest arrival on this list, which means it is the most likely to have moved.

Official documentation: Connect apps to Gemini Spark

Perplexity

Plan required: not published. Perplexity documents the feature without naming which subscription tier unlocks it, so the honest answer is to open your settings and look.

Go to Account settings → Connectors, choose + Custom connector, and select Remote rather than local. Paste the address and sign in. HTTPS is required, which the Net Net address already satisfies.

In an organization, an admin controls this under Enterprise settings → Permissions → Connectors permissions, including a toggle governing whether ordinary members are allowed to add their own custom connectors at all.

Be aware that Perplexity's help center currently carries an older page saying remote MCP is coming soon. That page is out of date. Remote connectors have shipped.

Official documentation: Adding custom remote connectors

Grok

Plan required: documented as available to all Grok users, though the free versus paid breakdown is not spelled out. Grok has the shortest path of the five.

Go to grok.com/connectors, choose New Connector, select Custom, paste the address, and complete the sign in.

On Grok Business and Enterprise, an admin has to add the connector first at console.x.ai, under the team, in Grok Business → Connectors. Team members cannot add it themselves until that is done.

Connectors work on Grok web, iOS, and Android.

Official documentation: Grok connectors

If your assistant is not on this list

MCP is an open standard, not a Net Net invention and not a private arrangement with five companies. Any assistant that supports remote MCP servers can connect to Net Net, whether or not it appears above.

What you need from it is the ability to add a remote server by URL, with OAuth sign in. That last part matters. Some tools only support MCP servers you run yourself on your own machine, which is a different capability and will not reach Net Net.

If your tool supports remote servers, give it https://mcp.netnet.app/mcp and it should behave the same way as everything described here.

When the connection does not work

Nothing happens when you ask a question. The most likely cause by a distance is that the connector is authorized but not enabled in that particular conversation. Look for a connectors or tools control inside the chat itself rather than in settings.

You are asked to sign in again and again. One sign in per connection is expected. Repeated sign ins during normal use are not, and are worth reporting rather than working around.

Requests are declined. Check your workspace plan first. Net Net refuses MCP requests from a workspace that has returned to the free tier, even though the connector still looks correctly configured in your AI tool.

Your AI answers about the wrong workspace. If your login belongs to more than one Net Net workspace, name the workspace explicitly in your question rather than assuming your assistant picked the one you meant.

The connection fails from a browser based tool. A small number of tools run MCP connections entirely inside the browser rather than from their own servers. If your tool works that way and the connection will not establish, that is a known limitation rather than something you have configured wrongly.

Frequently Asked Questions

Do I need an API key or a token from Net Net?

No. There is nothing to generate, copy, or store. You sign in with the same email and password you use for Net Net, inside your AI tool, and the two systems handle the authorization between them. If a set of setup instructions anywhere asks you to paste a Net Net secret key, those instructions are wrong.

Which assistant should I pick if I have no strong preference?

Claude is the lowest friction starting point, because custom connectors are available on every tier including free. That makes it the cheapest way to see whether connecting your workspace to an assistant is genuinely useful to you before you buy anything. The walkthrough video linked above shows that path from start to finish.

Can my whole team connect, or just me?

Anyone with a Net Net login can connect their own assistant, and each connection carries that person's own permissions. On the AI side, some providers require an admin to approve custom connectors for the organization first, so check the relevant section above.

Why do I have to sign in inside my AI tool instead of Net Net?

Because the authorization has to belong to the AI tool, not to a browser tab. Signing in from inside the tool is what tells Net Net which assistant is asking and on whose behalf, and it is what lets you remove that specific connection later without touching anything else.

How do I disconnect?

Remove the connector in your AI tool. It is the same settings screen you used to add it. The connection ends there, and nothing in your Net Net workspace changes as a result.

These menu paths do not match what I am seeing. Now what?

Follow the provider's own documentation, which is linked in each section above. Every one of these companies shipped or reworked custom connector support during 2026 and several are still in beta, so their pages will be current when ours is not. The address you paste, https://mcp.netnet.app/mcp, does not change.

Related articles

If you are still deciding whether the setup is worth it, Connect Your Own AI to Net Net with the MCP Server explains what the connection is for and where its limits are. Once a connector is working, What to Ask Your AI About Your Net Net Workspace is the fastest way to find out whether it earns its place. If requests are being declined and the settings look right, AI Access and Your Plan: Why MCP Needs a Paid Plan is usually the explanation. And because every person connects with their own login and their own permissions, Managing Team Members, Invites, and Join Requests covers getting the rest of your shop set up first.

Updated on: 08/05/2026