Connect ChatGPT to Crane Ledger
Use Crane Ledger as the accounting system behind ChatGPT (custom connector / MCP). ChatGPT becomes the generative UI for your books.
Prerequisites
- A Crane Ledger account at craneledger.ai — GitHub, Google, Apple, or email magic link.
- A ChatGPT plan that supports custom MCP connectors (typically Plus, Pro, Business, Enterprise, or Edu with developer features enabled).
- Optional: credits on Billing (new orgs start with 500 free credits).
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.
Connect via OAuth (recommended)
In ChatGPT, add a custom connector / MCP server with URL:
https://api.craneledger.ai/mcpChatGPT discovers Crane Ledger’s OAuth authorization server and registers a client (DCR).
You’ll be redirected to
https://craneledger.ai/oauth/consent.Sign in if needed (GitHub, Google, Apple, or email magic link).
Pick the organization and approve scopes (
ledger:read,ledger:write, and optionallyledger:admin).Return to ChatGPT — enable the connector in the conversation if your client requires it.
Connect via API key
In the Crane Ledger dashboard, create a live API key (
ha_live_…).Configure the ChatGPT connector with:
Authorization: Bearer ha_live_…
Use this for environments that do not support the OAuth consent UI.
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 |
|---|---|
| 401 / auth failed | Re-run OAuth consent, or confirm the Bearer key is live and not revoked |
| Wrong organization | Re-consent and select the correct org |
| Tools missing | Ensure the connector is enabled for the current chat |
| Insufficient credits | Check Billing; purchase credits or enable auto-recharge |
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