AI assistants such as Claude, ChatGPT, Claude Code and Cursor can work with your BSCpro data for you: look up contacts and recruits, check your calendar and statistics, add notes, update a contact and more. They connect through the BSCpro MCP server (MCP, the Model Context Protocol, is the standard way AI apps connect to other services).
There are two ways to connect:
- Sign in (recommended for AI apps). You add BSCpro to your AI app, sign in to BSCpro and choose what the app may do. Nothing to copy or paste.
- API access token. You create a token in BSCpro and paste it into the app or script. Use this for your own scripts, or for an AI app that can't sign in.
Either way, the app acts as you. It sees only what you can see in BSCpro, and only does what you allowed.
What you need
- A paid, active BSCpro subscription. Free accounts can't connect apps or create tokens.
- An AI app that supports remote MCP servers. Some AI apps only offer this on their paid plans.
The BSCpro MCP server address is:
https://bscpro.com/mcp
Connect by signing in
Step-by-step guides for each app:
- Claude (claude.ai and the Claude app)
- ChatGPT
- Claude Code
- Cursor
- GitHub Copilot in VS Code
- Gemini CLI
For another app, the steps are similar:
- In your AI app, add a new remote MCP server (often called a custom connector or MCP server). Give it the name BSCpro and the address
https://bscpro.com/mcp. Choose OAuth or sign-in if asked, and leave any client ID and secret fields empty. - The app opens a BSCpro page in your browser. Sign in to BSCpro if asked (including your two-factor code if you use one).
- BSCpro shows which app wants to connect, the account you're signed in as, and a list of permissions. Tick only the permissions the app needs.
- Click Allow. You're sent back to your AI app, which is now connected. Click Deny if you didn't start connecting this app yourself.
| Check before you click Allow: Any app can ask to connect, and BSCpro can't confirm who made it. Only allow an app you just started connecting yourself. |
|---|
You stay connected until you disconnect the app or change your password. The app doesn't have to ask you to sign in again each time.
Connect with an API access token
- In BSCpro, click your name or photo at the top right, then click Profile.
- Open the Integrations tab.
- In the API access tokens card, click Create token.
- Fill in the form:
- Name: something that tells you where the token is used, for example "Claude Code on my laptop".
- Scopes: tick only what the app or script needs. Write access doesn't include read access, so tick both if it needs to look things up and change them.
- Expires: 7, 30, 90 or 180 days, 1 year, or no expiry.
- Current password: your BSCpro password.
- Click Create token.
- Click Copy to copy the token. You can see it only this once. If you lose it, revoke it and create a new one.
To use the token with an AI app, add the MCP server address https://bscpro.com/mcp and send the token in an Authorization header with the value Bearer followed by the token. For example, in Claude Code:
claude mcp add --transport http bscpro https://bscpro.com/mcp --header "Authorization: Bearer YOUR_TOKEN"
Your own scripts can use the same token with the BSCpro API at https://bscpro.com/api/v1/.
| Keep your token secret: Anyone who has it can use BSCpro as you, within its scopes. Treat it like a password, and don't paste it into emails, chats or shared documents. |
|---|
What a connected app can and can't do
- It can only use the parts of BSCpro its permissions (scopes) allow. The app shows you only the tools those permissions cover.
- It can add and change contacts, recruits, appointments, notes and more if you allowed write permissions. These changes are real, your team sees them, and some send emails or notifications. Most AI apps ask you before each change; read what they're about to do before you approve it.
- It can't delete anything.
- It can never sign in as you, change your password, email or privacy settings, manage authorized users, uplines or promotion history, remove team members, or create tokens.
AI apps read text that other people typed, such as contact notes and guest names. Text like that could try to trick the app into making changes. Giving the app only the permissions it needs limits what it could do.
Disconnect an app or revoke a token
Both are on the Integrations tab of your Profile:
- Connected AI apps lists the apps you connected by signing in, with the permissions you gave each one. Click Disconnect to remove one. It loses access straight away and has to ask you again to reconnect.
- API access tokens lists your tokens with when each was created and last used. Click Revoke to stop a token working.
Changing or resetting your BSCpro password disconnects every app and revokes every token. If your subscription ends, apps and tokens stop working until you subscribe again.
Troubleshooting
- The app says it can't connect, or asks you to sign in again: disconnect BSCpro in the app, then connect again. If you changed your BSCpro password, you need to reconnect every app.
- "Access tokens need a paid, active BSCpro subscription": connecting apps is part of the paid plans. See What is the difference between a free and paid account?
- The app can't find a tool or says it isn't allowed: the permission it needs wasn't given. Disconnect the app and connect again with that permission ticked, or create a new token with the scope.