myinvois-mcp

myinvois-mcp

Enables issuing and managing validated Malaysian e-invoices via MyInvois (LHDN) directly from MCP clients, with tools for TIN validation, invoice drafting, submission, and document management.

Category
Visit Server

README

<p align="center"> <img src="docs/assets/logo.png" alt="Unofficial MCP & SKILL.md — LHDN Malaysia einvoice. 1. Setup, 2. Generate, 3. Manage" width="440"> </p>

Malaysia e-Invoice (MyInvois) — for humans and their AI

Talk to Claude, get a validated LHDN e-invoice. This repo gives your AI the skill + MCP tools to handle the whole journey — getting API access on the hasil.gov.my portal, keeping your company & client records, submitting, and sending the result to your customer.

Unofficial · not affiliated with LHDN · you are responsible for your own tax submissions. Sandbox by default — nothing touches production unless you opt in.

Where are you in the journey?

flowchart TD
    A{"Do you have MyInvois<br/>API keys?"} -->|no| B["① Get access<br/>one-time only · guided walkthrough"]
    A -->|yes| C["② Configure &amp; setup<br/>one-time only · company &amp; clients"]
    B --> C
    C --> D{"Day-to-day"}
    D --> E["③ Submit an e-invoice<br/>new client → purchase → send"]
    D --> F["④ Check invoices<br/>status · history · cancel"]
    D --> G["⑤ Record a supplier bill<br/>self-billed, foreign vendors"]
    E --> H["📧 Email PDF + QR<br/>to your client"]

    classDef ask fill:#F6C915,stroke:#1B2A4A,stroke-width:2px,color:#1B2A4A
    classDef journey fill:#1B2A4A,stroke:#1B2A4A,color:#FAF9F5
    classDef result fill:#FAF9F5,stroke:#1B2A4A,stroke-width:2px,color:#1B2A4A
    class A,D ask
    class B,C,E,F,G journey
    class H result
    linkStyle default stroke:#1B2A4A,stroke-width:2px
    click B "https://techtemplemy.github.io/e-invoice-malaysia-mcp/guide-access.html" "Get access — guided walkthrough"
    click C "https://techtemplemy.github.io/e-invoice-malaysia-mcp/guide-configure.html" "Configure & setup"
    click E "https://techtemplemy.github.io/e-invoice-malaysia-mcp/guide-submit.html" "Submit an e-invoice"
    click F "https://techtemplemy.github.io/e-invoice-malaysia-mcp/guide-check.html" "Check invoices"
    click G "https://techtemplemy.github.io/e-invoice-malaysia-mcp/guide-selfbill.html" "Record a supplier bill"

Open a journey: ① get access · ② configure & setup · ③ submit · ④ check · ⑤ self-billed (chart nodes are clickable in editors that allow it; GitHub disables in-chart links, so use these)

Each step below has a copy-paste prompt for Claude and a no-AI fallback. Prefer clicking through screens? The visual guide hub has one page per journey ①–⑤, each opening with the same copy-paste Claude prompt.


① Get access — you have no API keys yet (one-time only)

💬 Say to Claude: "Use the myinvois skill. I'm new to Malaysia e-invoicing — get me MyInvois sandbox API access for my company, step by step. Open the portal pages for me as we go."

Claude walks you through the LHDN portal (it can open the hasil.gov.my pages in a browser alongside you), warns you about the two traps everyone hits (registering under your personal profile instead of the company; clock-skew rejections), saves your keys to ~/.myinvois.env, and proves the connection with a live token call.

No AI? Follow the get-access page — mock portal screens plus a .env generator.

② Configure & setup — you have keys (one-time only)

💬 Say to Claude: "Use the myinvois skill. I already have my MyInvois client ID and secret — set up my credentials, my company profile, and my client book."

Claude collects your seller details (TIN, BRN, MSIC, address), validates your TIN against LHDN live, and writes two small local files that every future invoice reuses: ~/.myinvois-profile.json (you) and ~/.myinvois-clients.json (who you bill). Nothing is stored anywhere else.

No AI? The configure page has in-browser generators for both files.

③ Submit an e-invoice

a — new client?

💬 "Save a new client: ACME Sdn Bhd, BRN 201901234567 — look up and validate their TIN first." → MCP: search_tinvalidate_tin → client book.

b — the purchase / invoice itself

💬 "Here's my invoice PDF — submit it to MyInvois. Show me the summary before sending." (or just describe the line items in chat)

Your AI extracts buyer + lines, builds the UBL document from your profile, always shows you a summary and waits for your yes (draft_invoiceconfirm_submission, enforced in code), then returns the LHDN validation link.

c — send it out

💬 "Email the invoice PDF with the validation link and QR to accounts@acme.com." — works if your Claude has an email connector (Gmail / Outlook); otherwise make the QR with npx qrcode "<link>" -o qr.png and attach it yourself. The invoice maker builds a print-ready PDF with the QR embedded — fonts, logo, your colours.

④ Check invoices

💬 "Show my e-invoices from the last month" · "What's the status of INV-2026-0012?" · "Cancel INV-2026-0012 — wrong amount."

MCP: list_recent_documents, get_document, cancel_document (cancel window is 72 hours; cancelling asks you to confirm first).

⑤ Record a supplier bill (self-billed)

Foreign vendors (OpenAI, Hostinger, AWS…) never send Malaysian e-invoices — you must issue a self-billed one to claim the expense, by end of the month after payment.

💬 "Here's my OpenAI receipt — create the self-billed e-invoice for it."

The vendor goes in as supplier (generic TIN EI00000000030), your company as buyer, type 11 — same confirm-before-submit flow.


How it's wired

Three frontends, one shared core, everything on your machine — the only thing that ever leaves is the HTTPS call to LHDN:

flowchart LR
    subgraph yours["Your machine — nothing else sees your data"]
        direction LR
        U["You + your AI<br/>Claude Code · Desktop · Cursor"]
        SK["Claude skill<br/>SKILL.md + zero-dep CLI"]
        MCP["MCP server<br/>npx e-invoice-malaysia-mcp"]
        WEB["static pages<br/>guide · invoice maker"]
        LIB["shared core<br/>auth · UBL builder · API client"]
        CFG[("~/.myinvois.env<br/>profile · client book")]
        U --> SK
        U --> MCP
        U --> WEB
        SK --> LIB
        MCP --> LIB
        CFG -.-> LIB
    end
    LIB ==>|HTTPS| LHDN["LHDN MyInvois API<br/>sandbox → prod"]
    LHDN --> OUT["✓ validated e-invoice<br/>share link + QR → email your client"]

    classDef ask fill:#F6C915,stroke:#1B2A4A,stroke-width:2px,color:#1B2A4A
    classDef comp fill:#1B2A4A,stroke:#1B2A4A,color:#FAF9F5
    classDef store fill:#FAF9F5,stroke:#1B2A4A,stroke-width:2px,color:#1B2A4A
    classDef gov fill:#C0321C,stroke:#C0321C,color:#FAF9F5
    class U ask
    class SK,MCP,WEB,LIB comp
    class CFG,OUT store
    class LHDN gov
    style yours fill:#FAF9F5,stroke:#1B2A4A,stroke-width:2px,color:#1B2A4A
    linkStyle default stroke:#1B2A4A,stroke-width:2px

Safety is structural, not polite: submissions are a two-step draft_invoiceconfirm_submission with a one-time token, sandbox is the default environment, and the skill/MCP always show you a summary before anything reaches LHDN.

Install

Claude Code (skill — recommended start):

git clone https://github.com/techtemplemy/e-invoice-malaysia-mcp
cp -r e-invoice-malaysia-mcp/skills/myinvois ~/.claude/skills/myinvois

Claude Desktop / Cursor / any MCP client:

{ "mcpServers": { "myinvois": {
    "command": "npx", "args": ["-y", "e-invoice-malaysia-mcp"],
    "env": { "MYINVOIS_CLIENT_ID": "…", "MYINVOIS_CLIENT_SECRET": "…", "MYINVOIS_ENV": "sandbox" }
} } }

<details> <summary><b>For developers — CLI, API reference, layout</b></summary>

Zero-dependency CLI (Node ≥ 18, no install)

node skills/myinvois/scripts/myinvois.mjs token
node skills/myinvois/scripts/myinvois.mjs validate-tin C1234567890 BRN 202001234567
node skills/myinvois/scripts/myinvois.mjs search-tin BRN 202001234567
node skills/myinvois/scripts/myinvois.mjs submit my-invoice.json --stamp
node skills/myinvois/scripts/myinvois.mjs submission <submissionUid>
node skills/myinvois/scripts/myinvois.mjs document <uuid>

11 commands total — also recent, raw, cancel, reject, doctypes.

MCP server (e-invoice-malaysia-mcp)

11 tools: validate_tin, search_tin, get_supplier_profile, draft_invoice, prepare_ubl_submission, confirm_submission, get_submission, get_document, list_recent_documents, cancel_document, reject_document. Two-step submit (one-time confirmation token, 10-min TTL), sandbox default, local stdio, no telemetry. Local checkout: claude mcp add myinvois -- node <repo>/mcp/server.mjs.

Repo layout

docs/                        # static site: setup guide · invoice maker · landing
skills/myinvois/             # standalone Claude Code skill
  SKILL.md                   #   3-phase workflows
  scripts/myinvois.mjs       #   the CLI
  templates/ references/     #   UBL template · field rules · every endpoint as curl
lib/ + mcp/server.mjs        # the npm package (this repo root)
postman/                     # official LHDN Postman collection + environments

Field-tested

Real sandbox submissions, validations, and rejections — every trap we hit is documented in references/api.md (wrong-role ERP registration, CF321 clock skew, ERR236 consolidated classification…).

</details>

License

WTFPL — do what you want with it.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured