Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ARL-CMS MCP Server Check compliance for export documentation under Bangladesh law"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Exposes the AKIJ Resources Compliance Management System knowledge base to MCP clients (opencode, Claude, etc.) over stdio JSON-RPC 2.0.
data/)Data | Content |
| 584 compliance requirements — 80 domains, 11 categories, 13 fields each (what it is, why, minimum requirements, evidence, pass criteria, non-compliance triggers, owner) |
| 584 quick index rows (name, domain, category, applicability, owner) |
| 2,612 Bangladesh legal risks (SBU, area, scenario, legal basis, penalty, level: Critical 340 / High 1,016 / Medium 881 / Low 375) |
| 55 ERP document types → Tier1 internal policy / Tier2 BD law / Tier3 global standard + owner |
| 42 ERP business documents (schema/table + process + tax flag) |
| 79 Bangladesh acts / rules + official bdlaws.minlaw.gov.bd links |
Related MCP server: Obsidian Regulatory MCP
TIER 1 — Internal ARL policy/SOP/manual library (primary source)
TIER 2 — Bangladesh law (risk register + bdlaws portal) — mandatory floor
TIER 3 — Global standard (584-requirement catalog)
Every "not found" at an earlier tier is reported as a coverage gap before moving on. Bangladesh law is non-negotiable and governs even if an internal document is silent or weaker. Evidence before verdict: no evidence = NOT DEMONSTRATED, not COMPLIANT.
Tool | Purpose |
| Filter the 584-requirement catalog (query/domain/category/owner/applicability) |
| Full 13-field detail of one requirement |
| Orchestrated 3-tier compliance resolver for a topic |
| Tier-1 library search (live Drive embedded view) — reports coverage gap if none found |
| Bangladesh legal risks by SBU/area/topic with legal basis + penalty + level |
| Official bdlaws link + metadata for the 79 registered acts/rules |
| 55 ERP document types → 3-tier compliance mapping + owner |
| 42 ERP business documents inventory |
| Catalog coverage by domain/category + registered asset counts |
| Coverage gap rows + risk-register summary |
| CMS inventory statistics |
node server-arl-cms.jsEnvironment variables:
ARL_CMS_DRIVE_FOLDER — override the Tier-1 policy library Drive folder id
(default 1F_OGk1yzP_nf_TD8NbInJOpS-MYLR3xX)
ARL_CMS_DMS_TREE — path to the ARL-DMS tree.json (Hybrid integration).
When set, cms_search_policy / Tier-1 resolution searches the shared
14,535-entry DMS index and returns real documents (name, path, drive id, url,
source). Default lookup order: env → sibling ../arl-dms/data/tree.json →
bundled data/dms-tree.json → skill library paths.
ARL_CMS_DRIVE_FOLDER — fallback live-Drive root when no shared index found.
Read-only by design. Bundles the catalog data; no external DB required.
Hybrid integration (Option 5): the CMS MCP reads the shared ARL-DMS index
for Tier-1 document search; document text/OCR is fetched via the ARL-DMS MCP
(dms_fetch). The ARL-CMS skill and ARL-DMS skill document this cross-reference.
Shareable as a single npm package (.tgz) via npx -y <github-release-url>.
Return the official Bangladesh law link and metadata for the registered acts/rules from bdlaws.minlaw.gov.bd (Tier 2 mandatory statutory floor).
Inputs: name.
Inventory of ERP business documents (42 types) with schema/table and ERP process mapping; filter by module, process, tax.
Inputs: limit, query, module, process, +1 more.
3-tier compliance resolver: (1) internal policy/SOP library, (2) Bangladesh law (risk register + bdlaws), (3) global standard (584-requirement catalog). Reports coverage gaps explicitly. Tier 2 (Bangladesh law) is the mandatory floor.
Inputs: topic (required).
Library-to-standard coverage scan: maps the 584-requirement catalog domains/categories and reports counts and registered assets.
Inputs: no named parameters.
Compliance mapping for ERP document types (55 types) in 3-tier order - T1 internal policy/SOP/manual, T2 Bangladesh law, T3 global standard, plus indicative owner.
Inputs: tier, limit, owner, document_type.
Coverage gap report: requirements whose domain has no candidate internal document match, plus Bangladesh risk-register summary.
Inputs: limit.
Get full 13-field detail of a single compliance requirement by name (what it is, why, how it should work, minimum requirements, evidence, pass criteria, non-compliance triggers, owner).
Inputs: name (required).
List/filter compliance requirements from the CMS catalog (584 requirements / 80 domains / 11 categories). Filters: query, domain, category, owner, applicability. Returns up to 200 rows.
Inputs: limit, owner, query, domain, +2 more.
Look up Bangladesh legal risks from the risk register (2,612 rows) by SBU, area, or topic, with specific legal basis, possible liability/penalty, and risk level.
Inputs: sbu, area, limit, topic, +1 more.
Search the internal ARL policy/SOP/manual library (Tier 1) for a topic. Hybrid integration: resolves real documents from the shared ARL-DMS index (14,535 entries) first, falls back to live Drive. Returns matched documents with name, path, drive id, url, source. For document text/OCR use ARL-DMS MCP dms_fetch.
Inputs: topic (required), limit.
Return CMS inventory statistics: total requirements, domains, categories, risk register rows, document types, business documents, BD laws.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 11 tools
Most tools target distinct resources, but the set has several adjacent compliance/coverage tools: cms_check_compliance, cms_document_compliance, cms_coverage_scan, and cms_gap_report overlap in scope. Detailed descriptions help, but an agent could still misselect between general compliance checking, document-type compliance mapping, and coverage/gap reporting.
All tools share the cms_ prefix and snake_case, which keeps them readable. However, the convention is mixed: some use verb_noun (cms_get_requirement, cms_list_requirements, cms_check_compliance), while others are noun phrases (cms_risk_lookup, cms_document_compliance, cms_gap_report).
Eleven tools is well within the appropriate range for a compliance knowledge/resolution server. Each tool appears to cover a distinct query, lookup, or reporting need, and none feels redundant enough to remove without losing a capability.
The surface covers requirements lookup, policy search, Bangladesh law references, risk lookup, ERP document mapping, coverage scanning, and gap reporting, which is broad for a read-only compliance assistant. Minor gaps remain, such as no direct document/law text retrieval and no write/update lifecycle for requirements or risk records.
The Compliance Knowledge Marketplace. Accessible to people and AI. Find it on Complyzard.
Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR, Cyber Resilience Act and AI Act.
10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE).
Company-specific regulatory assessments for concrete business questions, as structured data or PDF.