IT Glue MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_organizationsB | Search for organizations in IT Glue with optional filtering |
| get_organizationB | Get a specific organization by ID from IT Glue |
| search_configurationsC | Search for configurations (devices/assets) in IT Glue |
| get_configurationB | Get a specific configuration (device/asset) by ID from IT Glue |
| search_locationsA | Search for locations (physical addresses/sites) of an organization in IT Glue. Each result includes the address fields and phone number. Locations are a built-in IT Glue entity (not a flexible asset), so use this rather than search_flexible_assets to look up an organization's address or phone. |
| get_locationA | Get a specific location by ID from IT Glue, including its full address and phone number. |
| create_locationA | Create a new location (physical address/site) for an organization in IT Glue. IT Glue requires a name and typically a country_id for a location. |
| update_locationA | Update an existing location in IT Glue. Only the fields you supply are changed. |
| search_passwordsA | Search for password entries in IT Glue (returns metadata only, not actual passwords) |
| get_passwordA | Get a specific password entry by ID from IT Glue (includes the actual password value) |
| search_documentsA | Search for documents in IT Glue (scoped to an organization). Returns document metadata only (name, folder, URL, timestamps) — not the document body. Use get_document or list_document_sections to read a specific document's content. |
| get_documentB | Get a specific document by ID from IT Glue |
| list_document_foldersA | List document folders for an organization in IT Glue, returning their names and IDs. Works with your API key on tenants where IT Glue exposes the Document Folders resource (rolling out across tenants in 2026). If the API key is rejected, a JWT is used as a fallback (configure via ITGLUE_JWT env var or X-ITGlue-JWT header, or paste one when prompted). |
| create_documentA | Create a new document in IT Glue for an organization. If neither document_folder_id nor skip_folder_prompt is supplied, the user is prompted to pick a folder. Folder enumeration for the name-based picker tries the API key first (works on tenants where IT Glue exposes the Document Folders resource), then a configured JWT; if neither can list folders, the prompt accepts a folder URL, a sibling-document URL, or a numeric folder ID. Pass skip_folder_prompt=true to always create at the organization root without prompting. |
| list_document_sectionsA | List all sections of an IT Glue document in order. Use this to read document content before editing. |
| create_document_sectionA | Add a new section to an IT Glue document. Section types: 'heading' (Document::Heading) or 'text' (Document::Text). Call publish_document after editing. |
| update_document_sectionA | Update the content of an existing IT Glue document section. Use list_document_sections to get section IDs. Call publish_document after editing. |
| delete_document_sectionA | ⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a section from an IT Glue document. This action cannot be undone. Call publish_document after editing. Confirm with the user before invoking. |
| publish_documentA | Publish an IT Glue document to make section changes visible. Always call this after creating, updating, or deleting sections. |
| archive_documentA | ⚠ HIGH-IMPACT. Archives an IT Glue document (soft delete — hides it from normal views but keeps it recoverable). Use unarchive_document to restore. Confirm with the user before invoking. |
| unarchive_documentA | ⚠ HIGH-IMPACT. Restores a previously archived IT Glue document so it appears in normal views again. This makes the document visible to all users. Confirm with the user before invoking. |
| list_flexible_asset_typesA | List all flexible asset types defined in IT Glue. Call this first to discover type IDs before using search_flexible_assets. |
| search_flexible_assetsA | Search for flexible assets in IT Glue (requires flexible_asset_type_id filter) |
| itglue_health_checkA | Check connectivity to IT Glue API by fetching organization types |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| doc-completeness | Audit documentation completeness for an organization in IT Glue |
| runbook-check | Find systems or services without runbooks in IT Glue |
| password-audit | Find passwords that have not been rotated in 90+ days |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| IT Glue Document Card | Interactive MCP Apps card rendering an IT Glue document |
TDQS
Scored across 24 tools
Most tools are clearly distinct by resource type (organizations, configurations, locations, passwords, documents, flexible assets) plus action (search/get/create/update/delete). A few potential confusions exist: get_password vs search_passwords are well-differentiated, but get_document/list_document_sections/list_document_folders could blur for an agent unfamiliar with IT Glue's section/folder vs full-document model. The location vs flexible_assets distinction is explicitly documented to avoid misselection.
Tool names follow an extremely consistent verb_noun pattern throughout: get_*, search_*, create_*, update_*, delete_*, list_*, publish_*, archive_*/unarchive_*, plus one exception itglue_health_check. The prefix conventions are uniform and predictable across all 24 tools, making the intended action and resource immediately clear.
With 24 tools, this borders the upper edge of reasonable for a broad IT Glue domain covering organizations, configurations, locations, passwords, documents, and flexible assets. Each tool maps to a meaningful operation, though the document-centric surface (10+ tools) is somewhat heavy relative to the thin coverage of other entity types. Still defensible given the domain breadth.
The surface covers organizations (search/get), locations (search/get/create/update), passwords (search/get), configurations (search/get), and a rich document lifecycle (search/get/folders/sections/publish/archive/unarchive/create). Notable gaps: no create/update/delete for organizations, configurations, passwords, or flexible assets — only read operations. Since several entity types lack write capabilities, the surface feels read-heavy for those, though document management is fully covered.