
このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
MCP server for IT Glue — documentation, passwords, configurations, and flexible asset tools for AI assistants
概要
A Model Context Protocol (MCP) server that provides Claude with access to IT Glue documentation and asset management. Unlike the other Wyre MCP servers, this one talks to the IT Glue API directly and has , so the one-click build does not need a GitHub Packages token — the cloud builder's npm ci only pulls public packages. (A read:packages token is only needed to install the published @wyre-ai/itglue-mcp package itself; see Installation.) The DigitalOcean target builds the full Docker image and runs the complete MCP server over HTTP and is the recommended path; this repo does not ship a Workers entrypoint (src/worker.ts), so prefer DigitalOcean or the prebuilt container image (ghcr.io/wyre-ai/itglue-mcp). This package is published to the npm registry, which requires a token even for public packages. Authenticate npm once, then install: The repo's .npmrc already points the @wyre-ai scope at GitHub Packages and reads the token from NODE_AUTH_TOKEN, so no further config is needed.
README
以下は原文 README の抜粋です。原文を見る。
IT Glue MCP Server
A Model Context Protocol (MCP) server that provides Claude with access to IT Glue documentation and asset management.
One-Click Deployment
[!NOTE] Unlike the other Wyre MCP servers, this one talks to the IT Glue API directly and has no private
@wyre-ai/*runtime dependency, so the one-click build does not need a GitHub Packages token — the cloud builder’snpm cionly pulls public packages. (Aread:packagestoken is only needed to install the published@wyre-ai/itglue-mcppackage itself; see Installation.) The DigitalOcean target builds the full Docker image and runs the complete MCP server over HTTP and is the recommended path; this repo does not ship a Workers entrypoint (src/worker.ts), so prefer DigitalOcean or the prebuilt container image (ghcr.io/wyre-ai/itglue-mcp).
Installation
This package is published to the GitHub Packages npm registry, which requires a token even for public packages. Authenticate npm once, then install:
# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token) # or a PAT with read:packages
npm install @wyre-ai/itglue-mcp
The repo’s .npmrc already points the @wyre-ai scope at GitHub Packages and
reads the token from NODE_AUTH_TOKEN, so no further config is needed. The same applies
to npx @wyre-ai/itglue-mcp.
Or use the Docker image:
docker pull ghcr.io/wyre-ai/itglue-mcp:latest
Configuration
Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file; never commit a real value.
| Variable | Description | Required |
|---|---|---|
ITGLUE_API_KEY |
Your IT Glue API key (format: ITG.xxx). Used by stdio and by HTTP when AUTH_MODE=env. |
Yes (stdio and env mode) |
ITGLUE_JWT |
A user-session JWT used as an optional fallback for document-folder operations on tenants whose API key cannot access the Document Folders resource yet. See JWT fallback for document-folder operations. | No |
ITGLUE_REGION |
API region: us, eu, or au (default: us) |
No |
ITGLUE_BASE_URL |
Override the IT Glue API base URL (advanced) | No |
MCP_TRANSPORT |
Transport: stdio (local) or http (remote). Defaults to stdio when run via npx/node, and to http in the Docker image. |
No |
MCP_HTTP_PORT |
Port for HTTP transport (default: 8080) |
No |
インストール
npx @wyre-ai/itglue-mcp設定
{
"mcpServers": {
"itglue": {
"command": "npx",
"args": ["@wyre-ai/itglue-mcp"],
"env": {
"ITGLUE_API_KEY": "${ITGLUE_API_KEY}",
"ITGLUE_REGION": "us"
}
}
}
}