ITGlue

You can run an unofficial MCP server to interact with ITGlue data via automated assistants. This server lets you manage ITGlue documents, their sections, and organizations through HTTP or local stdio transports, with CRUD operations, publishing, and regional support. It’s designed to be integrated by tools and assistants that rely on structured MCP endpoints to perform ITGlue tasks.

How to use

You connect an MCP client to the server either over HTTP or through a local stdio process. Use the HTTP method for a remote or testable setup by starting the server in HTTP mode and pointing your client to the local endpoint. Use the stdio method if you want to run the server directly in your environment using the command-line interface. Both options support document management, document sections, and organization lookups. You can list, retrieve, create, update, publish, and delete documents; manage document sections; and search for organizations to obtain IDs needed for operations.

How to install

Prerequisites: you need Node.js installed on your machine. You may also use Docker if you prefer containerized deployment.

Install dependencies and prepare the server for running.

Run the server in stdio mode using the following command (you must provide your ITGlue API key via an environment variable):

Additional configuration and usage notes

Environment variables you will commonly use include ITGLUE_API_KEY for authenticating with ITGlue, ITGLUE_BASE_URL for a custom ITGlue API base URL, and TRANSPORT to select stdio or http transport. You can also specify the port for the HTTP server.

You can enable regional API endpoints by adding a region flag to the server startup command, such as --region eu or --region au, if you are targeting EU or Australia regions.

Tools available and what they do

The MCP server exposes tools to manage organizations, documents, and document sections. These tools enable you to list, retrieve, create, update, publish, and delete ITGlue data within the constraints of ITGlue API permissions.

Security and access considerations

Keep your ITGlue API key secure. Keys are revocable by ITGlue after 90+ days of inactivity. Use restricted keys and rotate them as part of your security hygiene.

Troubleshooting tips

If you encounter rate limiting from the ITGlue API, you will receive clear error messages. If the HTTP server is not reachable, verify the port binding and that the ITGLUE_API_KEY is correctly set. For local development, ensure your environment variables are exported in the shell before starting the server.

Examples you can model your setup on

Start the server in HTTP mode on port 3000 with your API key, then point your MCP client to the local endpoint.

Notes on deployment

Docker provides containerized deployment options. You can build a local image and run it, exposing port 3000 by default. The image expects the ITGLUE_API_KEY to be supplied at runtime.

Available tools

itglue_list_organizations

Search and list organizations with filtering and pagination

itglue_get_organization

Get detailed information about a specific organization

itglue_list_documents

List documents globally or within an organization

itglue_get_document

Get a document with all embedded sections

itglue_create_document

Create a new draft document

itglue_update_document

Update document metadata (name)

itglue_publish_document

Publish a draft document

itglue_delete_documents

Permanently delete one or more documents

itglue_list_document_sections

List all sections in a document

itglue_get_document_section

Get a specific section with full content

itglue_create_document_section

Add a section (Text, Heading, Gallery, Step)

itglue_update_document_section

Update section content, type, or position

itglue_delete_document_section

Permanently delete a section