Architecture Overview
The InfoTrack MCP Gateway is a centralized proxy that sits between your AI agents and InfoTrack's services. Rather than connecting to each service individually, your client connects to a single Gateway endpoint. The Gateway handles authentication, routing, session management, and context enrichment before requests reach the backend tools.
How Requests Flow
When your agent sends a request, the Gateway authenticates it, determines which downstream service to route to, injects any required context, and returns the result. Your agent only ever communicates with the Gateway; the complexity of reaching the correct service is handled entirely behind the scenes.
Tool discovery is dynamic. Each time your client connects, the Gateway returns the current set of available tools. As InfoTrack adds or updates services, your agent picks up the changes automatically without any configuration on your side.
Transport and Sessions
The Gateway uses HTTP transport with Server-Sent Events (SSE) for streaming responses. Your client sends standard HTTP requests to the Gateway endpoint and receives streamed results via SSE.
Sessions are maintained across requests, so contextual information gathered during a conversation (such as a client reference or matter details) is automatically carried forward into subsequent tool calls. If your client disconnects and reconnects with the same session, the conversation resumes where it left off.
Elicitation
When an action requires user confirmation, such as approving a cost or selecting from a set of options, the Gateway prompts your client for input using the MCP elicitation protocol. If your client supports elicitation, the user sees a structured prompt within the conversation. If not, the Gateway falls back to chat-based prompting to collect the required approvals.
Rate Limiting
The Gateway enforces rate limiting to protect service availability. Limits are applied per IP range and can be configured for specific traffic sources. For production deployments, provide your IP ranges to the InfoTrack MCP Services team to ensure your traffic is not inadvertently throttled.
Observability
Every tool invocation is traced and logged, capturing the tool name, duration, outcome, and associated metadata. This gives both InfoTrack and your team visibility into what your agents are doing, how services are responding, and where issues may arise.
Scalability
The Gateway is designed for high availability across multiple regions. Load balancing and auto-scaling ensure consistent performance under varying traffic levels, and distributed session storage allows your client to maintain continuity regardless of which instance handles the request.