Use Noli from Claude or ChatGPT
Connect your Noli account to the assistant you already use, and ask it about your customers, pipeline, projects and notes without leaving that chat.
If your working day already happens inside Claude or ChatGPT, you do not have to move it. Connect your Noli account and those assistants can look things up in your business and get work done in it, right there in the conversation you are already having.
Once connected you can ask things like:
- "Who did I not follow up with this week?"
- "What is in my pipeline over five thousand dollars?"
- "Pull up what I wrote about pricing last month and turn it into a post."
- "Add a task to chase the Henderson quote tomorrow."
One connection covers everything your plan includes. You do not connect each product separately.
Where to find it
Sign in at app.noliai.com, open the account menu in the top right, and choose Claude & ChatGPT. Everything below is on that page, including your connection address and a button to create a key.
Claude
- In Claude, open Settings, then Connectors.
- Choose Add custom connector.
- Paste the address from your Noli connect page:
https://app.noliai.com/api/agent/mcp - Claude will send you to Noli to sign in. Approve it once.
That is the whole setup. Claude will now show your Noli tools when they are relevant.
Custom connectors are available on Claude's Free, Pro, Max, Team and Enterprise plans. On Free you can have one at a time.
ChatGPT
ChatGPT keeps custom connectors behind a setting you turn on yourself.
- In ChatGPT, open Settings, then Connectors.
- Turn on Developer mode (under Security and login, depending on your version).
- Choose Add, and paste the same address:
https://app.noliai.com/api/agent/mcp - Sign in to Noli when prompted.
Claude Code, Codex, Cursor and other command line tools
Tools that run in a terminal cannot open a sign-in window, so they use a key instead.
- On your Noli connect page, choose Generate a key.
- Copy it straight away. We show a key once and cannot show it again, because we never store it in a readable form.
- Run the command for your tool. For Claude Code:
claude mcp add noli --transport http "https://app.noliai.com/api/agent/mcp" --header "Authorization: Bearer YOUR_KEY"
For Codex, Cursor and most other clients, use the JSON block shown on the same page.
If you lose a key or want to cut off access, generate a new one. That switches the old key off immediately, so update anywhere you had pasted it.
Keeping an assistant to one area
Sometimes you only want an assistant touching one part of the business. Add ?products= to the address and list what it may see:
https://app.noliai.com/api/agent/mcp?products=crm
https://app.noliai.com/api/agent/mcp?products=crm,kb
Anything left out simply does not appear to that assistant. This is a real boundary, not an instruction it can talk itself past.
The names are crm for your CRM, kb for your knowledge base, pm for your project manager, ams for your marketing system, and cos for your Chief of Staff's own tools.
What it can reach
Whatever your plan includes, and nothing else. If a product is not on your plan its tools never appear, and if you cancel one they stop working the same day. If you are not sure what an assistant can currently see, ask it to check its Noli capabilities and it will tell you.
What needs your approval first
Anything that goes out to the world or cannot be undone waits for you. Publishing a post, sending to your audience, deleting a project: your assistant files it in your Noli approval feed and tells you it is waiting, and it runs once you approve it there. Everyday work like adding a note, creating a task or updating a draft happens straight away.
This is the same rule your Chief of Staff already follows, so an outside assistant does not get a shortcut around it.
Connecting to one product directly
You can still point an agent at a single product with that product's own API key, which is useful for scripts and custom code rather than chat assistants. Each product issues its own key from its settings: the project manager and knowledge base use a Bearer token, and the CRM uses an x-api-key header. The connection above is the better choice for Claude and ChatGPT, because it is one sign-in instead of several and it keeps working as we add tools.