Bizplay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIZPLAY_ROLE | No | Role for the registry gateway over stdio. | |
| BIZPLAY_COMPANY | No | Company for the registry gateway over stdio. | |
| BIZPLAY_USER_ID | No | User identity for stdio transport (e.g., emp001, emp002, mgr001). Over stdio (Claude Desktop) the identity falls back to BIZPLAY_USER_ID. | |
| BIZPLAY_API_TOKENS | No | Service token(s) for the Bizplay API. Default is demo-service-token. | |
| BIZPLAY_API_BASE_URL | No | Point the gateway at another API. Set to "embedded" to run the mock existing API inside the MCP server process, or to http://127.0.0.1:18080 to use a separately running API. | |
| FASTMCP_SHOW_SERVER_BANNER | No | Set to "false" to hide the FastMCP server banner. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_card_balanceA | Show the caller's corporate cards with monthly limit, amount spent, and remaining balance. |
| list_card_transactionsB | List the caller's corporate card transactions for a month. |
| find_missing_receiptsA | Find the caller's transactions that are missing receipt images or entertainment attendee lists. |
| validate_tax_complianceA | Check transactions against Korean corporate-card rules (receipts, clean-card merchants, entertainment evidence, late-night/weekend use) and estimate deductible input VAT. |
| draft_expense_reportA | Create a DRAFT expense report and return it with a compliance check. Nothing is submitted. |
| submit_for_approvalA | Submit one of the caller's draft reports to their manager. Refused if compliance blockers remain. Only call this after the user has explicitly confirmed submission. |
| list_pending_approvalsA | Managers only: list expense reports waiting for the caller's approval. |
| decide_approvalA | Managers only: approve or reject a report assigned to the caller. Confirm with the user first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| month_end_closing | Guide an employee through month-end expense closing. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| my_profile | The caller's Bizplay profile: role, department, manager, and cards. |
| korean_compliance_policy | The Korean corporate-card rules this server enforces (simplified demo rules). |
TDQS
Scored across 8 tools
Each tool targets a distinct action-resource pair: balance viewing, transaction listing, receipt gap detection, tax validation, report drafting, submission, and manager-side listing/decision. The only mild overlap (missing-receipt checks vs. tax compliance receipts) is clearly delineated by descriptions emphasizing VAT estimation versus receipt discovery.
All eight tools follow a consistent snake_case verb_noun convention (get_card_balance, list_card_transactions, validate_tax_compliance, draft_expense_report, etc.). No mixing of casing or verb styles.
Eight tools is well-scoped for a corporate card expense workflow, covering both employee and manager roles without redundancy. Each tool earns its place in the lifecycle.
The surface covers balance, transactions, compliance, drafting, submission, and approval decision — a solid full lifecycle. Minor gaps: no tool to fetch or edit an existing draft report's contents, which an agent would likely need after a rejection.