POS Support MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POS_SUPPORT_DB_PATH | No | Path to the SQLite database file used by the server. Override to use an isolated database. | data/pos_support.db |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_branchesA | List fictitious branches, optionally filtered by status. |
| get_branchA | Get one branch by its stable business code. |
| list_terminalsB | List terminals, optionally filtered by branch and status. |
| get_terminalB | Get one terminal by branch code and branch-local terminal code. |
| list_incidentsB | List incidents using optional branch, terminal, status, and priority filters. |
| get_incidentB | Get an incident with its branch, optional terminal, and ordered history. |
| search_similar_incidentsB | Find incidents using deterministic local Jaccard text similarity. |
| create_incidentB | Create an open branch-wide or terminal-specific support incident. |
| update_incidentB | Edit an active incident or move it from open to in_progress. |
| resolve_incidentC | Resolve an active incident with a required applied solution. |
| get_critical_incidentsA | List unresolved critical incidents, optionally for one branch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nery2004/pos-support-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server