Saison Technology International

HULFT Integrate MCP Initiative

Sprint 2 Proposals

February 3-14, 2026

Strategic Alignment: "Global leader in AI-driven data integration solutions"

— Masa Ishikawa, 2026 Vision

Executive Summary

These three POCs position HULFT Integrate at the forefront of the Model Context Protocol (MCP) revolution—an emerging standard adopted by Anthropic, OpenAI, Google, and major enterprise vendors. By adding MCP capabilities, we transform Integrate from a traditional ETL tool into an AI-native data integration platform, enabling customers to leverage LLMs for troubleshooting, data normalization, and intelligent workflow routing.

3 POCs 2-Week Sprint 4+ Customer Use Cases
POC #1

HULFT Integrate MCP Server

Estimated Effort

5 days

Description

Develop an MCP Server that runs in parallel on a HULFT Integrate Server machine (Windows or Linux). The server exposes authenticated capabilities including server logs, exception logs, memory usage, process count, and script triggering—enabling AI-powered troubleshooting via tools like Claude.

User Story

"As a TSAM IT administrator using HULFT Integrate, I want to query server logs and exceptions through Claude so that I can troubleshoot integration errors faster without manually searching log files."

MCP Server Capabilities

  • Server Logs (read/search)
  • Exception Logs (filter by severity)
  • Memory Usage Metrics
  • Process Count & Status
  • Script Trigger Execution
  • Authentication (API Key/OAuth)

Target Customers

TSAM (Toyota South Africa Motors)

Existing HULFT customer with complex integration workflows

Internal Support Team

Faster troubleshooting for customer issues

Market Validation

Major vendors adopting MCP: PostgreSQL, MongoDB, Elasticsearch, Datadog, Sentry, GitHub, Slack, and 100+ others. MCP is positioned as the "USB-C of AI integrations."

POC #2

HULFT Integrate MCP Client Adapter

Estimated Effort

6 days

Description

Create a new HULFT Integrate Adapter that acts as an MCP Client with embedded LLM capability. This extends our adapter portfolio (REST, WSDL) to connect to the growing ecosystem of MCP Servers, with AI-powered data normalization and intelligent routing.

User Story

"As a 21D integration engineer, I want to connect HULFT Integrate to external MCP Servers with LLM normalization so that I can handle changing data formats without rewriting scripts."

Adapter Capabilities

  • MCP Client Connection
  • LLM Integration (Cloud/Local)
  • Source Data → Normalized JSON
  • JSON + Prompt → MCP Server
  • AI-Driven Workflow Routing
  • Data Validation & Column Mapping

Target Customers

21D

Complex data transformation needs

Wallacia

Multi-format data ingestion

PS Team (Internal)

Reduce hours of scripting per customer

Pain Points Addressed

Hours of Scripting

Manual script writing for each data format

Column Name Changes

CSV/structured data schema drift

Format Variations

Same data, different structures per source

POC #3

MCP Future-Proofing Strategy

Estimated Effort

3 days

Description

Prepare for the future where third parties may deprecate REST APIs in favor of MCP Servers. Position HULFT Integrate as the "MCP Mapping Tool with AI Built-In"—a strategic differentiator that aligns with our 2026 vision of becoming a solution-driven, AI-native platform.

User Story

"As a Saison sales engineer, I want to demonstrate HULFT Integrate's MCP capabilities so that customers see us as the future-proof choice for AI-era integrations."

Strategic Deliverables

  • MCP Positioning Document
  • Sales Demo Script
  • Competitive Analysis (vs Workato, Boomi)
  • Customer-Facing One-Pager
  • Technical Architecture Diagram

2026 Vision Alignment

"Shifting toward becoming a solution-driven company"

  • • AI impact is essential to adapt
  • • Default data integration for ERP ecosystems
  • • Growth Mindset + Backcast Mindset

Market Trend: API → MCP Migration

As AI agents become primary consumers of services, companies are shifting from REST APIs to MCP Servers. Early movers: Stripe, Twilio, Salesforce (announced MCP support). HULFT Integrate with native MCP support positions us ahead of competitors.

Sprint 2 Timeline: February 3-14, 2026

Week 1 (Feb 3-7)

  • POC 1 MCP Server scaffolding, authentication, log endpoints
  • POC 2 Adapter framework, MCP client connection
  • POC 3 Research, competitive analysis, draft positioning

Week 2 (Feb 10-14)

  • POC 1 Memory/process metrics, script triggers, testing
  • POC 2 LLM integration, normalization, workflow routing
  • POC 3 Sales materials, demo script, final documentation

Total Estimated Effort: 14 days (parallel execution)

Approval Requested

These POCs require CEO and Business Operations approval to proceed with Sprint 2 starting Monday, February 3, 2026.

Prepared By

Drew Stoneburger

Date

January 30, 2026

Sprint

Sprint 2 (Feb 3-14)