@veeemlab/itglue-mcp
Related Servers
Alternatives to @veeemlab/itglue-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityNot gradedmaintenanceAn MCP server that enables LLMs to interact with IT Glue documentation, including organizations, configurations, passwords, and flexible assets. It provides tools for listing, creating, and updating managed service provider (MSP) data through the IT Glue API.31-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and update IT Glue documentation, including organizations, configurations, locations, passwords, documents, attachments, flexible assets and user activity metrics, through a stateless HTTP service behind the MSPbots MCP gateway.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAn MCP server for the Hudu IT documentation platform that provides 39 tools and 6 resources for managing companies, assets, articles, and passwords. It enables users to interact with their documentation and assets through any MCP-compatible client using stdio or HTTP transport.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude Code and Copilot Studio to read, and when permitted write or delete, records across every documented resource of the IT Glue API, while password-related data is always refused and stripped. Runs in Docker or over stdio with configurable read/write/delete policies, per-organisation write allow-lists, restricted-record withholding, and Microsoft Entra ID sign-in.MIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for IT Glue that enables natural-language search and retrieval of organizational data, credentials (as secure links), documents, configurations, and other tenant records without ever exposing secrets or writing to IT Glue.-
- AlicenseCqualityDmaintenanceAn MCP server that connects AI assistants to the ThreatLocker Portal API with 44 tools for managing computers, approvals, action logs, tags, maintenance mode, and more across single-org and multi-tenant setups.441MIT
TDQS
Scored across 56 tools
Most tools have clearly distinct purposes (CRUD per resource), but the pairing of search_ and find_ tools for configurations, contacts, and organizations introduces some ambiguity. Descriptions help differentiate, but an agent might struggle to choose between them without careful reading.
Tool names follow a consistent itglue_<action>_<resource> pattern in snake_case. Minor inconsistency: some resources are plural (configurations) while others are singular in tools like itglue_get_configuration, but the pattern is predictable overall.
56 tools is high but justified by the breadth of resources (organizations, contacts, configurations, etc.) and operations (CRUD, bulk, fuzzy match, search). Could be streamlined by merging some search tools, but each tool has a clear role.
The tool set covers most CRUD operations for major resources, but notably missing create/delete for organizations, which is a significant gap for lifecycle management. Also lacks create for groups/users, but those may be read-only. Overall, noticeable gaps for a complete workflow.