Connect Gemini to Crane Ledger
Use Google Gemini (CLI or Gemini Enterprise) with Crane Ledger’s hosted MCP endpoint.
Prerequisites
- A Crane Ledger account and API key (or OAuth credentials for Enterprise).
- Gemini CLI, and/or Gemini Enterprise with permission to add a custom MCP data store.
MCP endpoint
| Setting | Value |
|---|---|
| URL | https://api.craneledger.ai/mcp |
| Transport | Streamable HTTP |
| Auth (OAuth) | Sign in at consent UI — no key in the client |
| Auth (API key) | Authorization: Bearer ha_live_… |
| Consent | https://craneledger.ai/oauth/consent |
Organization scope comes from your OAuth token or API key — you do not pass organization_id separately.
Scopes: ledger:read, ledger:write, and optionally ledger:admin.
See Authentication and MCP tools.
Gemini CLI
Add Crane Ledger to ~/.gemini/settings.json (field names may vary slightly by CLI version — prefer remote HTTP / URI pointing at the MCP URL):
{
"mcpServers": {
"crane-ledger": {
"httpUrl": "https://api.craneledger.ai/mcp",
"headers": {
"Authorization": "Bearer ha_live_your_key_here"
}
}
}
}
If your CLI build expects url / uri instead of httpUrl, use that key with the same URL and Authorization header. Restart the CLI after saving.
Gemini Enterprise (custom MCP datastore)
Admins can add a Custom MCP Server data store:
- Open Gemini Enterprise → Data stores → Custom MCP Server.
- MCP Server URL:
https://api.craneledger.ai/mcp(Streamable HTTP only). - Configure OAuth 2.0 against Crane Ledger’s authorization server (
https://auth.craneledger.ai) — authorization URL, token URL, client id/secret as required by Google’s connector form. - Create the connector, enable actions/tools, then authorize from the Gemini Enterprise chat UI and toggle the connector on.
Example prompts
Once connected, try:
- "Set up a basic chart of accounts for a small service business"
- "Create an invoice for $2,500 to Acme Corp for consulting"
- "What's our cash position right now?"
- "Show me profit and loss for last quarter"
- "How many credits do I have left?"
Troubleshooting
| Issue | What to try |
|---|---|
| Connection failed | Confirm HTTPS URL ends with /mcp and transport is Streamable HTTP |
| OAuth errors (Enterprise) | Verify authorize/token URLs and redirect URIs match Google’s docs |
| 401 (CLI) | Check Bearer API key |
Related
Need help?
Create a free account (GitHub, Google, Apple, or email) to access our support portal. Once signed in, use the Support tab in your dashboard to submit a support ticket — no GitHub account required. Our team typically responds within 24 hours.
- ✨ For LLMs/AI assistants: Read our structured API reference
- Legal: Terms of Service · Privacy Policy