Nest · Cheshire

Nest & AI_

Compose PoCAT XML in Nest. Internal API updates configuration and deploys. Cheshire reaches the same API through MCP—operators and agents share one control plane.

Cheshire AI

Automate PoCAT dev and ops

Cheshire AI routes intent through MCP into the PoCAT Internal API—the same control plane as Nest—so gateway configuration and routine operations move faster with less manual XML.

Architecture

Nest, Internal API, MCP, Cheshire

Two paths converge on PoCAT Internal API: the Nest UI for hands-on XML compose, and Cheshire calling MCP tools for agent-driven changes.

Legacy Nest · Cheshire
Edit gateway-config, context, and route groups with layout that mirrors shipped tarball structure.
  • Industry-specific gateways you host
  • JDBC resources shared via context.xml
  • Configurable static file routing
  • Pluggable transports and Servit-hosted bridges
Internal API
Read, write, validate, and apply XML through a single internal control plane—shared by Nest and automation.
  • REST API orchestration
  • OAuth 2.0 authentication
  • Rate limiting & throttling
  • Error handling & retry logic
MCP · Cheshire
Cheshire is the LLM assistant name; MCP exposes allowed tools so natural language stays within safe configuration operations.
  • Service discovery
  • Circuit breaker patterns
  • Load balancing strategies
  • Distributed tracing
Control plane

Integration Control plane

Optional: link to USER_GUIDE for authoritative XML layout; Internal API details ship in a separate spec when ready.

HTTP route binding

Bind HTTP patterns to upstream HTTP clients, broker channels, or Servit handlers using filters and XML route descriptors—extensions live in your modules, not in hidden YAML switches.

Ingress handoff
Marshals HTTP exchanges into channel Messages
Filter pipeline
Applies filters and validators you wire in XML
# routes/your-group/route.xml (illustrative)
# HTTP route metadata, filters, upstreams, templates
# are authored in XML—not ad-hoc YAML converters.
<http-route name="example">
<pattern method="GET" uri="/api/v1/items/*"/>
<!-- filters + upstream + responses -->
</http-route>
# Outbound traffic fans out through message channels;
# MQTT, RabbitMQ, and HTTP adapters ship as modules.
Journey

Developer Tools & SDKs

Compose in Nest or with Cheshire, validate, request apply through Internal API, then observe your gateway and channels.

CLI Tools
Command-line interface for managing configurations, testing integrations, and deploying changes.
SDK Libraries
Java-centric Servit APIs; extend Nest and Cheshire with automation from your JVM stack.
JUnit/component tests bundled with gateway modules
Comprehensive testing tools for validating integrations, mocking services, and load testing.
Version-controlled XML repos
Visual configuration editor with validation, version control, and deployment automation.
Structured logs plus your APM toolchain
Real-time monitoring and analytics for integration performance and error tracking.
Template Library
Pre-built integration templates for common enterprise systems and cloud services.