Use Happy Tactic from your AI assistant

Happy Tactic runs a remote tool server using the open Model Context Protocol (MCP) — the standard way assistants call tools. Your assistant connects to it with an API key.

Settings → API Keys → AI assistants → Create key for my assistant. Choose what it may do:

The key acts as you, inside your company only — the same data, role and plan limits you have in the app. Revoke it on the same page to switch the assistant off immediately. Keys expire (1 year by default).

Replace YOUR_API_KEY with your key.

https://api.happytactic.com/api/mcp/k/YOUR_API_KEY

{
  "mcpServers": {
    "happytactic-tools": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.14.3", "https://api.happytactic.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_API_KEY" }
    }
  }
}

https://api.happytactic.com/api/mcp/k/YOUR_API_KEY

{
  "mcpServers": {
    "happytactic-tools": {
      "url": "https://api.happytactic.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

claude mcp add --transport http happytactic-tools https://api.happytactic.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

The load, customer, carrier and verification tools are the matching API endpoints — same validation, scope, rate limit and answers. The account set-up tools run the same code as the screens in the app, as you: if the app would refuse you, so does the assistant.

Tools your key can’t use are not listed (a read-only key sees only the read tools). create_load and create_verification take an optional idempotencyKey: repeating a call with the same key returns the first result instead of creating a second one.

Can: read loads (stops, charges, references, history), check calls, customers, carriers with their latest verdict, and verifications; show today’s pickups and deliveries; create a Draft load; move a load to its next status; add a check call; set up the account (company details, defaults, customers with their own payment terms, contacts and addresses, teammates); look up a carrier by MC or DOT number; start a verification.

Cannot, on purpose: delete anything; change billing, your plan, payments, where invoices are paid to, or security settings; make someone an admin; change the legal company name (that needs approval in the app). Cannot yet: work with drivers, equipment, invoices, bills or settlements, read or upload documents, send offers or tenders, or cancel a verification.

• The assistant can only do what the key allows. Use a read-only key unless you want it to change things, and tell it to confirm before it does.
• Starting a verification and inviting a teammate cost money or send an email, so the assistant must pass confirm: true, which it should only do after you said yes. Every change it makes is written to your audit log with the key’s name.
• A link with the key in it is a password. Revoke the key if it leaks.
• Limits: the connection allows 120 requests a minute, and each tool keeps its endpoint’s own limit (reads 120/min, writes 60/min, verifications 10/min).
• Errors come back as plain sentences the assistant can read.