FreshBooks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (debug, info, warn, error) | |
| FRESHBOOKS_CLIENT_ID | Yes | OAuth client ID from FreshBooks Developer Portal | |
| FRESHBOOKS_TOKEN_PATH | No | Path for token storage | |
| FRESHBOOKS_REDIRECT_URI | Yes | OAuth redirect URI (e.g., https://freshbooks.goodsamsoftware.com/callback) | |
| FRESHBOOKS_CLIENT_SECRET | Yes | OAuth client secret from FreshBooks Developer Portal |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether FreshBooks is connected and return the active session details. WHEN TO USE:
TAKES NO ARGUMENTS — safe to call anytime. RETURNS (connected session): { connected: true, userId, accountId, businessId, email, expiresAt }
RETURNS (no session or expired token): { connected: false } NEXT STEPS:
|
| auth_get_urlA | Generate an OAuth 2.0 authorization URL and a CSRF state token for the FreshBooks sign-in flow. WHEN TO USE:
TAKES NO ARGUMENTS. RETURNS: { url: "https://auth.freshbooks.com/oauth/authorize?...", state: "" } WORKFLOW:
|
| auth_exchange_codeA | Exchange an OAuth authorization code for access and refresh tokens, completing the FreshBooks connection. WHEN TO USE:
REQUIRED:
RETURNS: { success: true, userId, accountId, businessId, email, expiresAt } Tokens are stored locally; all subsequent tool calls use them automatically. ERRORS:
|
| auth_revokeA | Revoke the current FreshBooks OAuth session and delete all stored tokens. WHEN TO USE:
TAKES NO ARGUMENTS. RETURNS: { success: true, message: "Authentication revoked successfully" } NOTE: After calling this tool, all accounting and time-tracking tools will return auth errors until a new OAuth session is established via auth_get_url → auth_exchange_code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a distinct OAuth lifecycle step: checking status, generating an authorization URL, exchanging the callback code, and revoking the session. There is no meaningful overlap between the tools.
All tools share the auth_ prefix and use snake_case, which creates a clear family. The minor inconsistency is that auth_status is noun-like while auth_get_url, auth_exchange_code, and auth_revoke are action-oriented.
Four tools is well-scoped for the authentication functionality being exposed. Each tool is necessary for completing or managing the FreshBooks OAuth connection, and none are redundant.
The auth lifecycle itself is complete, but the descriptions repeatedly mention accounting and time-tracking tools that do not exist in this server. After connecting, an agent has no actual FreshBooks accounting operations to call, leaving a significant dead end.