Connect AI
Connect your AI app to Bizisy
Claude, ChatGPT, Cursor, VS Code, Gemini CLI and other apps that speak MCP connect to Bizisy by signing in: paste your company's Bizisy address into the app, sign in, check what it may do and press Allow. No keys to copy. The app then works as you, with your permissions.
Your address
Each company has its own address: <company> is the name in the address you sign in at.
| Address | What the app gets |
|---|---|
https://<company>.bizisy.com/mcp/manage | HR Assistant. What your role allows in Manage: people, jobs, teams, invites and settings. For owners, admins, HR and viewers. |
https://<company>.bizisy.com/mcp/me | My workspace. Your own details, the directory and the org chart. For everyone. |
Signed in to Bizisy, press Connect AI at the top of any page (or Integrations → AI apps in Manage): it shows your address ready to copy, and one-click install links for Cursor and VS Code.
Claude
claude.ai, Desktop and Claude Code
claude.ai and Claude Desktop
- In Claude, open Customize → Connectors and choose Add custom connector.
- Paste your address as the server URL (name it Bizisy if asked), then choose Add.
https://<company>.bizisy.com/mcp/manage - Choose Connect next to Bizisy. Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
On Team and Enterprise plans an Owner adds the connector once, under Organization settings → Connectors; then each person connects with their own Bizisy login. On the Free plan you can add one custom connector.
Claude Code
- Run this in your terminal:
claude mcp add --transport http bizisy https://<company>.bizisy.com/mcp/manage - In Claude Code, type /mcp, pick bizisy and choose Authenticate. Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
ChatGPT
Developer mode on the web
- In ChatGPT on the web (Plus, Pro, Business, Enterprise or Edu), open Settings → Security and login and turn on Developer mode.
- Go to Plugins in ChatGPT, select the + button and create an app. Paste your address as the MCP server URL and choose OAuth for authentication.
https://<company>.bizisy.com/mcp/manage - Create it, then connect. Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
- In a chat, turn the app on from the composer's Developer mode tools. ChatGPT asks you to confirm every change before it happens.
Cursor
The AI code editor
- Add it to ~/.cursor/mcp.json (or use the Add to Cursor button in Bizisy → Connect AI):
{ "mcpServers": { "bizisy": { "url": "https://<company>.bizisy.com/mcp/manage" } } } - In Cursor, open Customize → Tools & MCP: bizisy asks you to sign in, so choose Connect. Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
VS Code
GitHub Copilot agent mode
- Run MCP: Add Server… from the Command Palette, pick HTTP and paste your address:
https://<company>.bizisy.com/mcp/manage - When VS Code asks to let Bizisy sign in, allow it. Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
- Open Copilot Chat in Agent mode: the Bizisy tools are in the tools list.
Gemini CLI
Google's command-line agent
- Run this in your terminal:
gemini mcp add --transport http bizisy https://<company>.bizisy.com/mcp/manage - Start gemini and type /mcp auth bizisy. Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
Other MCP apps
Any app that supports remote MCP servers
- Add a remote MCP server (Streamable HTTP) with your address:
https://<company>.bizisy.com/mcp/manage - Apps that support MCP sign-in find it on their own (OAuth 2.1 with PKCE, client registration or client metadata documents). Your browser opens Bizisy: sign in if asked, check what the app may do and press Allow.
- Apps without sign-in can use an API key instead, sent as Authorization: Bearer <key>.
What a connected app can do
A connected app has your permissions, never more, and the same limits as an API key:
- Read and change what your role can in Manage: people, jobs, teams, locations, invites and settings.
- Preview changes for you: Bizisy asks it to show what will change and wait for your OK.
- Every change it makes shows in Activity with its name.
It cannot:
- See other people's private details or pay.
- Change pay or payroll details, close the company or open billing pages: those stay in the app.
- Create API keys or connect other apps.
Disconnect an app at any time: Connect AI in your workspace, or Integrations → AI apps in Manage. Owners and admins see every app connected in the company and can disconnect any of them. An app also disconnects on its own after 30 days without use, and when your login is turned off.
How sign-in works
- Bizisy follows the MCP authorization specification: OAuth 2.1 with PKCE, protected resource metadata (RFC 9728), authorization server metadata (RFC 8414), and both client registration methods apps use (client ID metadata documents and dynamic client registration).
- The sign-in and the Allow page are on your company's own address. A connection works only there, only for the access you approved, and never through the developer API.
- Access tokens last one hour; the app renews them with a refresh token that changes on every use. Bizisy stores only fingerprints (hashes) of tokens.
- Everything an app changes shows in Activity with the app's name.
For developers
Discovery starts from the MCP endpoint's 401, which points to the protected resource metadata. The authorization server metadata of a company is at:
https://<company>.bizisy.com/.well-known/oauth-authorization-serverApps that cannot sign in can use an API key in the Authorization header instead, on the company address or on https://api.bizisy.com/mcp/manage. See the developer docs. Questions: hello@bizisy.com.