Understand the Billabex MCP connector
Understand what the Billabex MCP connector exposes to an AI assistant and how OAuth protects each access.
Updated
In short
The MCP connector links a compatible assistant to Billabex data and actions without giving it your password. The client discovers the remote server capabilities, then OAuth asks you to select the account and granted permissions. Start with read access, test it against a known organization, and add write access only for a defined need.
Expected result
Your AI client connects to the official Billabex server, completes OAuth, and performs a first read-only check.
Before you start
- Use a client that supports OAuth-protected remote MCP servers.
- Get the connector URL from Settings > Integrations in Billabex, never from an unverified message.
Procedure
- In Billabex, open Settings > Integrations and copy the official MCP connector URL.
- In your AI client, add a remote MCP server named Billabex and paste that URL.
- Start OAuth, sign in to Billabex, and check the organization shown.
- Grant
mcp:readfirst; grantmcp:writeonly when the assistant truly needs to change data. - Ask the client to list your organizations or summarize a known account, then compare the result with Billabex.
What Billabex does
The client communicates with the remote MCP server and completes OAuth before accessing Billabex. Available tools, resources, and prompts depend on the granted scopes. The URL configures a client; it is not a page intended to be opened directly in a browser.
If the result is not what you expected
- Do not use opening the URL in a browser as a connector health check.
- If authentication does not complete, disconnect and reconnect the client once.
- Never send a password, OAuth token, or Authorization header to support.