Skip to main content
Glama
infoset-mcp

infoset-mcp

by sudohakan

infoset-mcp

Model Context Protocol server that gives AI assistants structured access to Infoset CRM tickets, contacts and companies.

CI Release License Node

Features

  • Wraps the Infoset CRM API into 18 MCP tools: tickets, contacts, companies, SLA, email threads and batch operations.

  • API key auth: stateless X-API-Key header, no token refresh, no login flow.

  • Rate limit aware: monitors x-ratelimit-remaining, pauses 60s when remaining drops below 2.

  • Retry with backoff: a 429 response triggers up to 3 retries, 60s apart.

  • Batch tools: fetch multiple tickets, logs, contacts or companies in one call, 5 requests in parallel, with deduplication for contacts and companies.

  • 3 dependencies: @modelcontextprotocol/sdk, axios, zod.

Related MCP server: GHL MCP Server

Installation

git clone https://github.com/sudohakan/infoset-mcp.git
cd infoset-mcp
npm install
cp .env.example .env     # set INFOSET_API_KEY

Register it in your MCP client. The env-wrapper reads credentials from .env, so no secrets live in the client config:

{
  "mcpServers": {
    "infoset": {
      "command": "/absolute/path/to/infoset-mcp/scripts/env-wrapper.sh",
      "args": ["/absolute/path/to/infoset-mcp/src/mcp-server.mjs"],
      "env": {}
    }
  }
}

Configuration

Variable

Required

Default

Description

INFOSET_API_KEY

Yes

none

Infoset API key (sent as X-API-Key header)

INFOSET_BASE_URL

No

https://api.infoset.app

API base URL

INFOSET_USER_ID

No

none

Your Infoset user ID, the default owner for infoset_list_tickets and infoset_get_ticket_stats. API-key auth cannot resolve the caller (/v1/users/me answers 401), so without it those tools return every owner's tickets

Usage

Ticket operations

Tool

Description

infoset_list_tickets

List tickets with status, owner, date, sort filters and pagination

infoset_get_ticket

Get full ticket detail by ID

infoset_search_tickets

Search tickets by keyword with status and priority filters

infoset_create_ticket

Create a ticket with subject, contact, priority, content

infoset_update_ticket

Update status, priority, owners, subject, stage, pipeline

infoset_get_ticket_logs

Get activity logs for a ticket

infoset_add_ticket_note

Add a note to the timeline, private by default, HTML allowed

infoset_delete_ticket_log

Delete a log entry, such as a note added by mistake

infoset_get_ticket_stats

Ticket count breakdown by status

Contacts, companies, email and SLA

Tool

Description

infoset_get_contact

Get contact details by ID

infoset_list_contacts

List or search contacts by name, email, phone

infoset_get_company

Get company details by ID

infoset_get_email

Get email thread content by email ID

infoset_get_sla_breaches

Get SLA breach data for a ticket

Batch operations

Tool

Description

infoset_batch_get_tickets

Get multiple tickets in parallel (concurrency 5)

infoset_batch_get_ticket_logs

Get logs for multiple tickets in parallel

infoset_batch_get_contacts

Get multiple contacts with auto-deduplication

infoset_batch_get_companies

Get multiple companies with auto-deduplication

Reference codes

1

2

3

4

Status

Open

Pending

Resolved

Closed

Priority

Low

Normal

High

Urgent

Development

npm test               # test suite
npm run test:coverage  # with coverage report
npm start              # start the server standalone

See CONTRIBUTING.md for code style and pull request guidelines, and SECURITY.md for credential handling and vulnerability reporting.

Project structure

src/mcp-server.mjs     single-file server: tools, API client, rate limit monitor, retry handler
scripts/env-wrapper.sh  loads .env, then starts the server
tests/                 Jest suite (mcp-server.test.mjs)
MCP client (Claude, Cursor)  <--stdio-->  infoset-mcp (Node.js)  <--HTTPS-->  Infoset API

Transport is stdio (spawned by the MCP client, JSON over stdin/stdout, logs to stderr). Every request carries the X-API-Key header.

License

MIT, see LICENSE.

Available Tools

18 tools
infoset_add_ticket_noteA

Add a note to a ticket timeline (POST /v1/tickets/logs). Private by default (agents only); set isPrivate=false to make it visible to the customer. Notes accept HTML. Returns the created log, whose id can be passed to infoset_delete_ticket_log.

Inputs: notes (required), ticketId (required), isPrivate.

infoset_batch_get_companiesB

Get multiple Infoset companies in a single call (auto-deduplicates)

Inputs: companyIds (required).

infoset_batch_get_contactsB

Get multiple Infoset contacts in a single call (auto-deduplicates)

Inputs: contactIds (required).

infoset_batch_get_ticket_logsB

Get activity logs for multiple Infoset tickets in a single call

Inputs: ticketIds (required), itemsPerPage.

infoset_batch_get_ticketsB

Get multiple Infoset tickets in a single call (parallel fetch)

Inputs: ticketIds (required).

infoset_create_ticketB

Create a new Infoset ticket

Inputs: subject (required), contactId (required), status, content, +1 more.

infoset_delete_ticket_logA

Delete a ticket log entry, such as a note added by mistake (DELETE /v1/tickets/logs/{logId}). Irreversible.

Inputs: logId (required).

infoset_get_companyB

Get company information by company ID

Inputs: companyId (required).

infoset_get_contactA

Get contact information by contact ID

Inputs: contactId (required).

infoset_get_emailB

Get email thread content by email ID

Inputs: emailId (required).

infoset_get_sla_breachesA

Get SLA breach data for an Infoset ticket

Inputs: ticketId (required).

infoset_get_ticketA

Get single Infoset ticket detail by ID

Inputs: ticketId (required).

infoset_get_ticket_logsC

Get activity logs for an Infoset ticket

Inputs: ticketId (required), sortDir, itemsPerPage.

infoset_get_ticket_statsC

Get ticket statistics dashboard (counts by status)

Inputs: toDate, fromDate, ownerIds.

infoset_list_contactsB

List or search Infoset contacts

Inputs: page, query, itemsPerPage.

infoset_list_ticketsC

List Infoset tickets with optional filters and pagination

Inputs: page, status, sortCol, sortDir, +3 more.

infoset_search_ticketsA

Search Infoset tickets by subject text (contains, case-insensitive) and optional filters. The API has no full-text search: Search/q/keyword are ignored and return every ticket. Company lookup is not exposed as a tool: over REST use companies?name= then tickets?companyId=.

Inputs: query (required), page, status, priority, +1 more.

infoset_update_ticketC

Update an existing Infoset ticket

Inputs: ticketId (required), status, stageId, subject, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and the single/batch/log variants are clearly separated by name. The main fuzzy boundary is infoset_list_tickets vs infoset_search_tickets, which the description itself admits is only a subject-contains filter with no real full-text search. Minor asymmetry: notes are created with infoset_add_ticket_note but removed with infoset_delete_ticket_log, which an agent must infer.

    Naming Consistency5/5

    Every tool follows the infoset_<verb>_<noun> pattern, including the uniform batch_get_* group, list_*, get_*, create_*, update_*, add_*, and delete_*. No camelCase/snake_case mixing or stray vague verbs; the convention is predictable enough to guess tool names.

    Tool Count4/5

    18 tools across tickets, logs, contacts, companies, email, stats, and SLA is reasonable for a helpdesk API, but the four batch_get_* tools largely duplicate existing single-get capabilities and push the surface toward the heavy side. Each tool still has a defensible purpose, so this is slightly over-scoped rather than bloated.

    Completeness3/5

    Ticket lifecycle is well covered (create, update, get, list, search, notes, logs, stats), but the contact and company side is read-only — no create/update for contacts or companies, and no company list/lookup tool at all (the description explicitly says company lookup is not exposed). Emails are only reachable by ID via infoset_get_email with no list/discovery path, and there is no ticket deletion, leaving several dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Creatio CRM that enables AI assistants to read, create, update, delete records, execute business processes, and manage settings via OData and REST APIs.
      24
      56 npm
      6
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.
      64
      37 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for amoCRM integration, enabling AI assistants to manage leads, contacts, companies, tasks, and more via natural language.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for integrating AI assistants with Bitrix24, enabling retrieval and management of CRM entities, tasks, scrum, and knowledge bases through natural language.
      1
      MIT