Connect Nexatron to ChatGPT
ChatGPT can connect to remote MCP servers as custom connectors on some plans, when the workspace allows it. Nexatron's hosted MCP server works as one. This page covers what Nexatron needs; ChatGPT's own menus change often, so follow OpenAI's current help pages for the exact labels.
Before connecting
- Check that your ChatGPT plan and workspace allow custom MCP connectors. On business plans, a ChatGPT workspace admin usually controls this. Check the current product UI and OpenAI's help pages.
- Choose the Nexatron account and workspace you intend ChatGPT to access.
- A Nexatron workspace administrator may need to approve the connection first. See workspace approval; the same rules apply to every assistant.
Add the connector
-
In ChatGPT, open the settings for connectors and choose to create a custom connector. Check the current product UI for where this lives on your plan.
-
Enter this server URL:
https://api.nexatron.io/api/v1/mcp -
Choose OAuth as the authentication method. Nexatron supports OAuth 2.1 with PKCE and dynamic client registration, so no client ID or secret is needed from you.
-
Sign in with your Nexatron identity and check the account and workspace before approving the requested access.
-
Enable the connector in a conversation and start with a narrow question, such as revenue for one defined quarter.
What ChatGPT can use
ChatGPT sees the same hosted tools as any other client: seven analytics tools, plus three action tools when the workspace allows them and the connection was granted an action scope. See available tools and the MCP reference.
Every call runs as you, with your Nexatron role, row policies and masking
applied. execute_action changes data in a connected system; review its
target and parameters before you approve it.
Troubleshooting
No option to add a custom connector. Your plan or workspace settings do not allow it. Ask your ChatGPT workspace admin.
Sign-in waits for approval. Ask your Nexatron workspace administrator to review the request under Admin → AI → MCP → Pending approvals, then reconnect.
Action tools missing. The workspace may have actions switched off, or the connection was granted read scopes only.