Skip to main content

Connecting an AI App

Connecting an AI app adds Agentic to it as a connector, so the app can answer questions about your agents and, with build access, create and change them. Each AI app adds connectors in its own way. The connect guide in the Admin app has the steps for each one, and this page follows the same order.

Before You Start​

  • You need the Admin or Organisation Admin role in the organisation you plan to connect. Anyone else reaches a "You Need Admin Access" screen at the approval step. See Roles and Permissions.
  • Read the transcript notice on the Connected Apps overview. The app you connect will be able to read session transcripts, which can contain customers' personal information.
  • Some AI apps need their own administrator to turn on custom connectors first. The steps below say where this applies.

Opening the Connect Guide​

  1. Open the connect guide in one of these ways:
    • Select Connect an Agent on the sidebar card in Agentic.
    • Go to Settings > Connected Apps and select How to Connect (Organisation Admins only).
    • Go to Account Settings > Security and select How to Connect in the Connected Apps panel.
  2. The guide opens as Connect Your AI Agent to Agentic. Under Install, choose your AI app: Claude, ChatGPT, Cursor, VS Code, Windsurf or Other MCP Client.
  3. Copy the Server URL shown at the top of the page using its copy button.

The server URL is the address your AI app connects to. It differs between deployments, so always copy it from the guide rather than typing it from memory or from another organisation's setup.

The rest of the guide is under Use It (Prompts to Try and What It Can Do) and Trust (Security and Permissions). The Connected Apps link at the bottom of the guide, which shows a count once you have connections, takes you to your own list in Account Settings > Security.

Third-party menus change

The menu names for each AI app below were accurate at the time of writing. AI apps rename and move their settings often. If a menu doesn't match, check that app's own help for adding a custom or remote connector.

Claude​

  1. In Claude, open Customize, then Connectors.
  2. Select Add custom connector.
  3. Paste the server URL and name the connector NeonNow Agentic.
  4. Select Connect. Claude opens NeonNow Agentic in your browser to finish signing in.
  5. Approve access in the browser.

On Claude Team and Enterprise plans, an owner of the Claude workspace may need to add the connector before members can use it.

ChatGPT​

  1. In ChatGPT, open Settings, then Apps and Advanced Settings.
  2. Turn on developer mode, then create a custom app. Workspace administrators in ChatGPT may need to grant developer mode access first.
  3. Paste the server URL and choose OAuth as the sign-in method.
  4. Approve access in the browser.

Cursor​

  1. Select Add to Cursor in the connect guide. Cursor opens and installs the connector for you.

    To add it by hand instead, copy the snippet labelled ~/.cursor/mcp.json from the guide and add it to that file. The snippet already contains your server URL.

  2. Restart Cursor, then turn the server on under Customize and MCPs.

  3. Approve access in the browser.

VS Code​

  1. Select Add to VS Code in the connect guide. VS Code opens and installs the connector for you.

    To add it to a single workspace instead, copy the snippet labelled .vscode/mcp.json from the guide and add it to that file in your project.

  2. Run the MCP: List Servers command, start the server you added, and allow it to sign in.

  3. Approve access in the browser.

Windsurf​

  1. Copy the snippet labelled mcp_config.json from the guide and add it to ~/.codeium/windsurf/mcp_config.json.
  2. Refresh the MCP servers in the Cascade panel.
  3. Approve access in the browser.

Other AI Apps​

Any AI app that can add a remote server and sign in through the browser will work.

  1. Add the server URL as a remote server in your app. Some apps call this a remote MCP server.
  2. Sign in when your app opens the browser.
  3. Approve access in the browser.

For Other Clients​

The Other MCP Client page of the guide lists the connection details a developer or IT team might need when setting up a less common app. Each one has a copy button:

  • Transport: the connection type the app must support (Streamable HTTP).
  • Auth: how the app signs in, which is a browser sign-in using OAuth 2.1 with PKCE.
  • Client Registration: how the app introduces itself the first time it connects, either by registering itself automatically or by publishing a client metadata document.
  • Scopes: the read and build permissions the app asks for.
  • Metadata: an address the app can read to discover how to sign in.

The page also links to Test the Connection with MCP Inspector, a free tool for checking that a connection works before setting up a full AI app.

What Happens Next​

After you select Allow Access, the browser shows "You're Connected" and returns you to your AI app. The connection appears straight away in your Connected Apps list under Account Settings > Security, and for Organisation Admins on Settings > Connected Apps.

Each install page in the guide ends with a prompt you can copy and paste into the app to check it works, for example "Show me my agents in Production". The guide fills in the name of the environment you were in when you opened it.