invgate-service-desk-mcp: Instructions file for Claude Code

CLAUDE.md

invgate-service-desk-mcp CLAUDE.md is an instructions file for Claude Code from tracegazer/invgate-service-desk-mcp. It costs 536 tokens per session, scanned A, original, MIT.

Project instructions for an MCP server that connects AI agents to InvGate Service Desk, a system for managing IT support requests and related records.

In plain words
What is it for?
Working with incidents, users, groups, custom fields, knowledge-base articles, workflows, assets, announcements, triggers, and time entries.
Why use it?
They give the agent context for working with the service desk's API and its different types of data.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is tracegazer/invgate-service-desk-mcp's own configuration. It tells Claude Code how to work on invgate-service-desk-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything invgate-service-desk-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tracegazer/invgate-service-desk-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tracegazer/invgate-service-desk-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/tracegazer/invgate-service-desk-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for invgate-service-desk-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tracegazer/invgate-service-desk-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/tracegazer/invgate-service-desk-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/tracegazer/invgate-service-desk-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/tracegazer/invgate-service-desk-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for invgate-service-desk-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tracegazer/invgate-service-desk-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/tracegazer/invgate-service-desk-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 536 This file is loaded in full into every session.
When invoked 536 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00536 $0.00536
Opus 5 $0.00268 $0.00268
Sonnet 5 $0.00107 $0.00107
Haiku 4.5 $0.00054 $0.00054

Measured 10d ago against content hash 83e2b883d2d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

invgate-service-desk-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

MCP (Model Context Protocol) server for the InvGate Service Desk API. The goal is to expose InvGate SD operations as MCP tools so that AI agents can interact with InvGate Service Desk programmatically.

Knowledge Base

base_conocimiento/api-spec.json — Complete InvGate Service Desk API specification. This JSON maps endpoint keys (e.g. incident, incidents.by.status, user, kb.articles) to their HTTP methods, parameters, and descriptions. Key API domains:

  • Incidents — CRUD, filtering by status/agent/customer/view/sentiment, attachments, comments, reassignment, approvals, tasks, linking CIs
  • Users & Groups — user management, groups, companies, locations
  • Custom Fields — field definitions, options (list/tree), fields by category
  • Knowledge Base — articles CRUD, categories, keyword search
  • Workflows — initial fields, deployment, process management
  • Assets/CIs — asset lookup, linked assets
  • Breaking News — announcements
  • Triggers — automation rules and executions
  • Time Tracking — time entries by category
  • Data Export — bulk data extraction

Architecture

Python-based MCP server using the Anthropic MCP SDK (mcp package, FastMCP). Modular by domain: each src/invgate_service_desk_mcp/domains/*.py module owns its tools and registers them via register(mcp, client). 96 tools across 11 domains (63 read-only + 33 write opt-in). The API spec in base_conocimiento/ was used to drive tool generation.

Writes are gated by INVGATE_WRITE_PROFILE: none (default, read-only), support (incidents + time tracking; KB stays read-only), or full (incidents + time tracking + Knowledge Base). Legacy INVGATE_ENABLE_WRITES=1 still works and maps to full.

InvGate SD API Notes

  • Instance URL pattern: https://{instance}.sd.cloud.invgate.net
  • Auth: API token via header
  • Dates support epoch or iso8601 format parameter
  • Incidents are called "requests" in some API responses
  • Custom fields are referenced by category and can be list, tree, or free-form types
  • Views are predefined filters identified by numeric ID

Read the full file on GitHub · 38 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 38 lines · 536 tokens per session scan A 83e2b883d2d7

Subscribe to this mod's changes

invgate-service-desk-mcp CLAUDE.md is an instructions file published in the GitHub repository tracegazer/invgate-service-desk-mcp (3 stars, last pushed 1mo ago), licensed MIT. It adds 536 tokens to every session, about $0.0027 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens