Connect Claude or ChatGPT

Claude and ChatGPT can reach the MCP server at https://api.salesbud.com.br/mcp by signing you in to Salesbud. There is no client ID or secret to copy: you sign in, pick the workspace and authorize, and the assistant reads what you can see in Salesbud, nothing more.

What a connection is

Authorizing creates a user credential for you, listed on the API credentials screen with the app’s name as its origin. This guide calls it a connection. It is the same as a user credential in these ways:

• Scopes. It gets the scopes you can use in Salesbud, and no others.
• Approval. If you do not approve API credentials yourself, it waits for an administrator.
• Data visibility. It reads only what you can see in Salesbud.
• Limits. It counts toward the limit of 3 active user credentials (a disabled one still counts) and 1 pending, per user in each company. The limit applies when the connection is created; connecting again does not count.

It differs in these ways:

• No fixed validity. It does not expire on a date. It lasts until it is revoked, the owner loses access or the assistant stops renewing it.
• No secret. There is no client secret to copy, so a connection cannot be rotated: asking for it is refused with OAUTH_CLIENT_NOT_ROTATABLE.
• Inactive owner. When you leave the company or lose your login, renewing fails with invalid_grant, not invalid_client.
• Empty scopes. If none of your scopes is available, the token request is refused with invalid_scope.

Before you start

• Your company has API access enabled.
• You can sign in to Salesbud.
• The assistant is one Salesbud accepts: Claude or ChatGPT. Other apps are refused when they try to start the authorization. To use Claude Code, set up the MCP server with a credential, as in the quickstart.

Connect

Claude

Salesbud is listed in Claude’s connector directory, the same catalog in claude.ai, Claude Desktop, Claude mobile and Claude Code.

• Team and Enterprise: an organization Owner adds it once, in Organization settings → Connectors → Browse connectors: search for Salesbud and add it to the team. Each member then opens Customize → Connectors, finds Salesbud and clicks Connect. On Team plans, a member who cannot add connectors sees Request instead, which notifies the Owners.
• Pro and Max: open Customize → Connectors, search the directory for Salesbud and click Connect.

A custom connector added before keeps working. To move to the directory listing, remove it and add Salesbud from the directory.

If the directory listing is not available to you, add Salesbud as a custom connector instead.

On Team and Enterprise plans, an organization Owner adds the connector once, in Organization settings → Connectors → Add → Custom:

• URL: https://api.salesbud.com.br/mcp.
• Authentication: Sign in now, so each member signs in with their own Salesbud account.
• OAuth client: Use Claude’s published identity.
• No request headers: a client ID or secret in the headers would make every member read with the same credential.

Each member then opens Customize → Connectors, finds the connector and clicks Connect. On Pro and Max plans, you add the custom connector yourself in Customize → Connectors, with the same URL and authentication.

Claude does not let you change a connector’s authentication after it is created. If your organization already has a Salesbud connector set up another way, the Owner removes it and adds it again as above.

ChatGPT

1. Open Settings → Plugins and click Explore catalog, in the top right corner.
2. On the catalog page, click Add → Add custom MCP server, in the top right corner.
3. Give it a name, such as Salesbud MCP, enter the URL https://api.salesbud.com.br/mcp and choose OAuth authentication. The other fields are optional. Confirm the risk notice to continue.
4. After you connect, the plugin is listed in the catalog. Open it and choose to test it in a chat, or just ask a new chat about your Salesbud data: ChatGPT calls the plugin on its own.

Developer mode is not needed.

Authorizing

In both, the browser then shows the Salesbud consent page: sign in if needed, choose the workspace when you belong to more than one, review the app and the scopes, and authorize.

Waiting for approval

If you do not approve API credentials yourself, the connection is created awaiting administrator approval, the same queue as a requested user credential. The assistant connects, but every tool answers that the connection is waiting for an administrator, with the API’s message “The API client is waiting for administrator approval.”. The administrators who approve credentials are notified. Once one of them approves it on the API credentials screen, the same connection starts reading, with nothing to redo.

Administrators, and anyone allowed to approve API credentials, connect directly, with no pending step.

Connecting again

Connecting the same app again in the same company reuses the connection instead of creating another one. It updates the scopes to the ones you can use now and ends the earlier renewals, so a refresh token the app held before stops working. An access token already issued stays valid until it expires, which is expires_in seconds after it was issued, currently 1 hour.

If an administrator disabled the connection, enable it again on the API credentials screen before you reconnect; until then the authorization is refused.

Disconnecting

Disconnect on the API credentials screen revokes the connection. The next request the assistant makes is already refused, and it can no longer renew its access. In the MCP server the tools answer with an error asking you to reconnect, not with an HTTP 401. Connecting again after a revoke creates a new connection, and a new approval request if you do not approve credentials yourself.

How the assistant keeps access

The assistant receives an access token, valid for expires_in seconds (currently 1 hour), and a refresh token valid for 90 days. Each refresh token works once: renewing returns a new pair. A refresh token presented twice is treated as stolen. The renewal chain it belongs to is revoked, and the assistant has to connect again. If the assistant goes 90 days without renewing, you connect again.

Support

For help connecting Claude or ChatGPT, or with a connection that stopped working, email eng@salesbud.com.br. Tell us which assistant you use, your company in Salesbud, roughly when it happened and the message you saw. Never send a token, a password or a client secret.

For client developers

The flow is OAuth 2.0 authorization code with PKCE (S256 only) and the resource parameter set to https://api.salesbud.com.br/mcp. Clients are identified by a client metadata document URL, not by registration. A request to /mcp with no credential answers 401 with WWW-Authenticate: Bearer resource_metadata="https://api.salesbud.com.br/.well-known/oauth-protected-resource", which leads to the authorization server metadata. A token not issued for /mcp, such as a client-credentials token, answers 401 invalid_token there. See /oauth/authorize and /oauth/token. A client disconnects by sending its refresh token to /oauth/revoke, which revokes the connection.