docs: add platform connectivity and deployment guidance - #407
Merged
AutomateIP merged 1 commit intoAug 13, 2026
Merged
Conversation
Document itential-mcp's connection model: one platform connection per server process, and the recommended pattern of pointing platform.host directly at a highly-available/load-balanced Itential Platform endpoint rather than building multi-endpoint routing into itential-mcp itself. Covers why this works without client-side sticky sessions, the TTL-based reauthentication itential-mcp already performs transparently, and what to plan for when scaling itential-mcp itself behind its own load balancer (independent of platform-side HA). Add to docs/index.md's Configuration & Security section.
AutomateIP
added a commit
to AutomateIP/itential-mcp
that referenced
this pull request
Aug 13, 2026
Covers all 13 commits since v0.13.3 (itential#395-itential#407), grouped by feature/fix/security/chore/docs. Also corrects the stale '9 Dependabot advisories remain open' note in the 0.13.3 entry -- that hold was lifted in itential#399 and re-triage confirmed 0 open advisories as of 2026-08-07.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds deployment guidance covering itential-mcp's platform connectivity model:
one connection per server process, and the recommended pattern of pointing
platform.hostdirectly at a highly-available/load-balanced ItentialPlatform endpoint rather than building multi-endpoint routing into
itential-mcp itself.
Changes
docs/deployment.md(new): platform connectivity recommendation, why itworks without client-side sticky sessions, the TTL-based reauthentication
itential-mcp already performs transparently (
platform.ttl/ITENTIAL_MCP_PLATFORM_TTL), the connection/state model (one platformconnection per process, immutable config, no per-request state), and
guidance for scaling itential-mcp itself behind its own load balancer.
docs/index.md: link the new doc under "Configuration & Security".Docs-only change; no application code touched.
Testing
Related Issues
N/A