infoset-mcp

Model Context Protocol server for Infoset CRM helpdesk and ticket management

Tickets · Contacts · Companies · SLA · Email Threads · Batch Operations

Why infoset-mcp?

AI assistants need structured access to helpdesk data. REST APIs require authentication boilerplate, pagination handling, and rate limit management on every call. infoset-mcp wraps the Infoset CRM API into 16 MCP tools with built-in retry logic, rate limit protection, and batch operations, so your AI assistant can query tickets, contacts, and companies without dealing with HTTP plumbing.

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

• Rate limit aware: monitors x-ratelimit-remaining headers, auto-pauses before hitting limits

• Retry with backoff: automatic 429 retry (3 attempts, 60s intervals)

• Batch tools: fetch multiple tickets, logs, contacts, or companies in a single call with controlled concurrency

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

Quick Start

git clone https://github.com/sudohakan/infoset-mcp.git
cd infoset-mcp
npm install

MCP Client Configuration (Recommended)

Using env-wrapper (reads credentials from .env, no secrets in config):

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

Then create a .env file:

cp .env.example .env
# Set INFOSET_API_KEY in .env

Environment Variables

Tools

Ticket Operations (7 tools)

Contact and Company (3 tools)

Communication and SLA (2 tools)

Batch Operations (4 tools)

Reference Codes

Architecture

MCP Client (Claude, Cursor)  <--stdio-->  infoset-mcp (Node.js)  <--HTTPS-->  Infoset API
                                               |
                                    API Key Auth (X-API-Key)
                                    Rate Limit Monitor
                                    Retry Handler (429)

• Transport: stdio (spawned by MCP client, JSON over stdin/stdout, logs to stderr)

• Auth: X-API-Key header on every request, no token management needed

• Rate limiting: monitors x-ratelimit-remaining, pauses 60s when remaining < 2

• Retry: 429 responses trigger up to 3 retries with 60s backoff

• Batch concurrency: max 5 parallel API calls per batch operation

Development

npm test              # Run 29 tests
npm run test:coverage # Run with coverage report
npm start             # Start server standalone

Contributing

See CONTRIBUTING.md for development setup, code style, and pull request guidelines.

Security

See SECURITY.md for credential handling and vulnerability reporting.

MIT | Built with Claude Code