# Laidian AI tool packs for AI agents / 來電AI 給 AI 用的工具包 > MCP tools for Taiwanese small businesses: ERP, e-invoice, payments. One endpoint, one key for all packs. US$4 per pack per month, includes 1,000 tool calls (trial-period price, final price pending). - [ERP pack](https://enscon.ai/agents/erp.txt): Look up stock and file sales orders, store re-orders and production postings for human approval. Tools: stock_lookup, sales_order_create, store_order_request, production_actual_record, approval_status. - [Taiwan e-invoice pack](https://enscon.ai/agents/einvoice.txt): Request a Taiwan e-invoice (test account) for a sale; a human approves before it is sent. Tools: invoice_issue_test, approval_status. - [Payments pack](https://enscon.ai/agents/payments.txt): Request a Recur payment link (test mode); a human approves before the link is created. Tools: payment_link_create_test, approval_status. ## Connect (one URL + one key) - Endpoint (MCP, Streamable HTTP): https://laidian-erp.enscon.ai/mcp - Header: `Authorization: Bearer ` — key format: ld_ followed by 64 hex characters - Get a key: Subscribe once on Laidian AI (Recur); one key works for every pack. Signup link: TBD (key issuing is being set up). - Test key: After a test subscription, POST the claim code you get at activation to https://laidian-erp.enscon.ai/claim. Not available yet: the Recur sandbox product and webhook are still being set up (TBD). Test tenant quick start (test data — use these values, no need to ask the user): - ERP: SKU `TEA` (black tea), warehouse `MAIN`, customer `SHOP`, unit price `50`. Store re-order: `SHOP` / `TEA`, quantity `3`. `production_actual_record` can omit `orderNo` (demo production order MO2026110001). - E-invoice: order `INV-DEMO-01`, item `紅茶`, amount `50`. Payments: order `PAY-DEMO-01`, amount `99`. Neither needs an approved sales order first. - Write tools return a requestId and wait for a human; you cannot approve them yourself. Read the result later with `approval_status`. Claude Code: ``` claude mcp add --transport http laidian https://laidian-erp.enscon.ai/mcp --header "Authorization: Bearer ld_YOUR_KEY" ``` (Write the key literally; Claude Code does not expand environment variables inside remote headers. Check with /mcp.) Claude.ai / Claude Desktop — Settings → Connectors → Add custom connector: URL = the endpoint, Authentication = No sign in, Request headers: `Authorization` = `Bearer ld_YOUR_KEY`. Cursor (`~/.cursor/mcp.json` or `.cursor/mcp.json`): ```json { "mcpServers": { "laidian": { "url": "https://laidian-erp.enscon.ai/mcp", "headers": { "Authorization": "Bearer ${env:LAIDIAN_KEY}" } } } } ``` OpenAI Responses API (`mcp` tool; the key goes in `authorization`): ```json { "type": "mcp", "server_label": "laidian", "server_url": "https://laidian-erp.enscon.ai/mcp", "authorization": "ld_YOUR_KEY", "require_approval": "always" } ``` (Not yet verified against the live endpoint; this line will be updated after the deploy test.) ChatGPT app (connectors / developer mode): ChatGPT only supports OAuth or no auth and cannot send an API key header (OpenAI Apps SDK docs). An OAuth sign-in (paste your key once, approve) is being built; until then use the API route above.