23-country compliance — native e-invoicing for every major tax authority.
← MCP server registry
Business operationsPublic source
Point of Sale MCP Server
Global Point of Sale engine for ADK-Rust Enterprise agents. Provides 39 MCP tools covering the full retail transaction lifecycle across 23 countries — cart management, 20+ payment methods, fiscal e-invoicing for 22 tax…
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
20+ payment methods — cash, card, mobile money, QR payments, EBT/SNAP, meal vouchers.
Role-based controls — cashiers can't void; managers can. Configurable per-role limits.
Fiscal integrity — SHA-256 hash chain on receipts (TSE/NF525 compliant).
24 receipt languages — bilingual output for any market.
Zero configuration — starts immediately with no API keys or external services.
Architecture
How Point of Sale MCP Server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
01
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
02
MCP client
Discovers schemas, sends calls, and receives typed content.
03
Point of Sale MCP Server
Validates the request and owns 39 documented tool contracts.
04
Domain system
Keeps the API, data, credentials, and business rules behind the server.
This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.
Tool catalog
What can an agent ask Point of Sale MCP Server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
15 named tools shown from 39 documented tools
product_registerRegister product in POS catalog
internal writecart_createStart a new sale
internal writecart_add_itemScan/add item to cart
internal writecart_remove_itemRemove item from cart
internal writecart_apply_discountApply discount to cart
internal writecart_getView cart contents
read onlypayment_processProcess payment
financial actionreceipt_generateGenerate receipt
read onlyrefundProcess refund
financial actionshift_openOpen register shift
internal writeshift_closeClose shift and reconcile
internal writebarcode_lookupLook up product by barcode
read onlyGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
8 internal write5 read only2 financial action
- 23-country compliance — native e-invoicing for every major tax authority.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
ADK MCP SDKrmcpRegistry manifest
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
Install
cargo install mcp-posMCP client configuration
{
"mcpServers": {
"pos": { "command": "mcp-pos" }
}
}Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in business operations.
Ads MCP ServerA digital advertising platform for ADK-Rust Enterprise sales & marketing agents. 19 MCP tools covering campaigns, ad groups, ads/creatives, budgets and bids, audiences, daily performance metrics with derived KPIs…19 toolsAnalytics MCP ServerGoverned analytics platform for AI agents — metrics, dashboards, funnels, cohorts, anomaly detection, forecasting, and policy enforcement. 28 tools with full audit trail.28 toolsBanking MCP ServerUnified banking MCP server with 15 tools across 3 backends — Plaid (US/Canada/EU), Mono (Africa), and Open Banking (UK/EU PSD2). Accounts, transactions, balances, payments, identity, and statements.15 tools
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.7.0
- License
- Apache-2.0
- Tools
- 39
- Revision
- 59b2284c4d22
- Updated
- May 27, 2026
Transportsstdio