Connect Claude, ChatGPT or another AI assistant

Before you start

You have the Admin role in Partner Fleet.
MCP is turned on for your marketplace: you can see Advanced → MCP in the admin sidebar. If you can't, request access to the free Beta at [email protected].
Your AI assistant supports custom MCP connectors with sign-in (OAuth). See What it can do for an overview.

You don't need an API key. You connect by signing in, and API keys don't work with the MCP server.

Step 1: Copy your MCP server URL

In the admin sidebar, go to Advanced, then open the MCP tab.
At the top of the page, next to Your MCP server URL, click Copy.

The URL ends in /mcp, for example https://acme.partnerfleet.app/mcp. Always copy it from this page rather than typing it. It uses your admin address, which may be different from your public marketplace domain.

Step 2: Add the connector to your assistant

Assistants that support MCP let you add a custom connector, sometimes called a remote MCP server, usually from their settings under a name like Connectors, Integrations or Apps. Menus and plan requirements change often, so use your assistant's own help for the exact clicks. Wherever you add it, enter:

Name: anything you'll recognize, for example Partner Fleet.
Server URL: your MCP server URL from Step 1.
Sign-in: if you're asked, choose sign-in (OAuth). Don't enter an API key, a token or custom headers.

Then connect (usually a Connect button). Your browser opens Partner Fleet; continue to Step 3.

📘
Notes for common assistants

Claude: add it from Claude's connector settings. On team or business plans, an organization owner may need to add the connector first; each person then connects it with their own sign-in. See the Claude Help Center.

ChatGPT: custom MCP connectors may need a specific plan or a setting (such as developer mode) that a workspace admin turns on, and some plans allow only read actions. See the OpenAI Help Center.

Other MCP clients: any client that supports remote MCP servers with OAuth sign-in can connect. Give it the server URL and nothing else: it finds the sign-in page and registers itself.

Each person signs in with their own Partner Fleet admin account, so their connection carries only the permissions they approve, even when the connector was added for the whole team. Teammates who aren't Partner Fleet admins can't connect.

Step 3: Sign in and choose permissions

Your browser opens your marketplace's admin sign-in. Sign in with your admin account.
You'll see a screen titled [Assistant name] wants to connect to your marketplace. Check:
- Connecting as: the account the connection will act as.
- Authorization codes will be sent to: the address that receives access. It should belong to the assistant you're connecting, for example claude.ai or chatgpt.com. If you don't recognize it, click Deny.
Under What you allow it to do, tick the permissions you want to grant:

Permission	What it allows	Ticked at first
View listings	Read and search your listings: their content, their status, and the templates that shape them.	Yes
Create listings	Add new listings. New listings are always created as drafts, so someone on your team still has to approve one before it goes live.	Yes
Edit listings	Change existing listings: edit their details, add or remove content items such as features and FAQs, and send a listing for review or pull it back. Edits are made on a draft, so a published page doesn't change until someone approves it.	Yes
Read partner applications	See submitted partner and registration applications, including applicants' names, email addresses and links to uploaded files. Read-only.	No
Read form submissions	See responses to your general forms, including submitters' names, email addresses and links to uploaded files. Read-only.	No

Click Allow access. To cancel, click Deny.

You must tick at least one permission. Whatever you tick, the connection can never delete a listing or approve one.

📘
Least access first
Grant only what you need today. For example, tick only View listings to let the assistant search and summarize listings without being able to change anything. You can reconnect later with more permissions.

Step 4: Try it

Back in your assistant, make sure the Partner Fleet connector is turned on for your conversation, then try:

"Which of our listings mention Salesforce in their FAQs?"
"Show me the listings waiting for approval."
"On the Acme listing, rewrite the second feature to be clearer, then send it for approval."
"Which partner applications need review? Summarize each in one line." (needs Read partner applications)

Your assistant may ask you to confirm before it changes anything.

Manage connected assistants

Go to Advanced → MCP. Under Connected AI clients, each connected assistant has a row showing:

Client: the assistant's name and the address that receives access.
Connected by: the admin or admins who approved it.
Permissions: what it is allowed to do, shown by their short names: listings_read (View listings), listings_create (Create listings), listings_update (Edit listings), partner_applications_read and form_submissions_read. If several admins connected through it, this lists every permission any of them granted.
Connected and Last used.

Disconnect an assistant

Click Disconnect on its row and confirm. It loses access immediately. If several admins connected through the same assistant, they are all disconnected. Anyone who wants to keep using it must connect again.

A connection also stops working on its own if the admin who approved it loses the Admin role or their account is locked.

Change an assistant's permissions

Permissions are fixed when you approve them. To change them, click Disconnect, then connect again from your assistant and tick the new permissions.

Next steps

MCP Tools and Troubleshooting: every tool the assistant can use, how its edits flow into your approval queue, and fixes for common problems.