infoset-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFOSET_API_KEY | Yes | Infoset API key (sent as X-API-Key header) | |
| INFOSET_USER_ID | No | Override user ID for owner-based filtering | |
| INFOSET_BASE_URL | No | API base URL | https://api.infoset.app |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infoset_list_ticketsC | List Infoset tickets with optional filters and pagination |
| infoset_get_ticketA | Get single Infoset ticket detail by ID |
| infoset_get_ticket_logsC | Get activity logs for an Infoset ticket |
| infoset_get_emailB | Get email thread content by email ID |
| infoset_get_sla_breachesA | Get SLA breach data for an Infoset ticket |
| infoset_get_contactA | Get contact information by contact ID |
| infoset_search_ticketsB | Search Infoset tickets by keyword and optional filters |
| infoset_create_ticketB | Create a new Infoset ticket |
| infoset_update_ticketC | Update an existing Infoset ticket |
| infoset_list_contactsB | List or search Infoset contacts |
| infoset_get_companyB | Get company information by company ID |
| infoset_get_ticket_statsB | Get ticket statistics dashboard (counts by status) |
| infoset_batch_get_ticketsA | Get multiple Infoset tickets in a single call (parallel fetch) |
| infoset_batch_get_ticket_logsA | Get activity logs for multiple Infoset tickets in a single call |
| infoset_batch_get_contactsA | Get multiple Infoset contacts in a single call (auto-deduplicates) |
| infoset_batch_get_companiesA | Get multiple Infoset companies in a single call (auto-deduplicates) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools are distinct, with clear single vs batch and get vs list/search separations. The only potential confusion is between list_tickets and search_tickets, but their descriptions (filters vs keyword) delineate their purposes.
All tool names follow the consistent pattern infoset_<verb>_<noun>, using snake_case throughout. Verbs like get, list, search, create, update, and batch_get are used predictably, and batch operations are uniformly prefixed with 'batch_get'.
With 16 tools, the server is slightly over the typical 3-15 range, but the domain encompasses tickets, contacts, companies, emails, and SLA data, justifying the count. The batch operations add a few extra tools but serve a clear performance purpose.
Core ticket workflows (create, read, update, list, search, logs, SLA) are covered, along with contact/company read operations. Minor gaps exist such as no delete endpoints and no write operations for contacts or companies, but these do not impede primary use cases.