Integrations & MCP
At a glance
- The agent platform integrates with 10+ external systems via APIs, webhooks, and MCP
- Communication providers: 10+ (ElevenLabs, Twilio, Meta WhatsApp, ReachAll, LiveKit, AWS SNS, Novomind)
- MCP server at
/mcpexposes platform tools to external AI systems - Integration architecture: Abstract Factory pattern → provider-specific implementations
Why this matters
Every agent deployment involves connecting to the customer’s existing systems — their TMS, ERP, CRM, telephony, messaging. Knowing what’s already integrated (and what’s not) helps you scope a deployment accurately. “We already have a Twilio connector” is a different conversation than “we’ll need to build a custom integration.”
Current integration inventory
Platform integrations
| System | What it connects | Used for |
|---|---|---|
| ProjectX | Shipsy’s main logistics platform | Auth, consignment data, trip management, geocoding, object actions |
| LIA / Query Builder | Ticket management system | Incident tickets, comments, status updates, custom fields |
| Project Atlas | Address intelligence service | Address registration, scoring, resolution |
Communication providers
| Channel | Providers | Notes |
|---|---|---|
| Voice | ElevenLabs, LiveKit, ReachAll, Twilio | ElevenLabs = primary for AI voice; ReachAll = Indian market; LiveKit = WebRTC |
| Meta (Cloud API), Novomind, Twilio | Meta Cloud API = primary; Novomind = European market | |
| SMS | AWS SNS, Twilio | AWS SNS for bulk; Twilio for conversational |
| Provider implementation exists | Used for RFQ responses, notifications, alerts | |
| Chat | Provider implementation exists | Web chat widget integration |
Observability & monitoring
| System | What it does |
|---|---|
| New Relic | Application performance monitoring (APM), error tracking |
| Langfuse | AI observability — LLM call tracing, cost tracking, eval visualization |
| Elasticsearch | Request logging, execution logs (1-2 month retention) |
Integration architecture
Pattern: Abstract Factory (ChannelFactory → ProviderFactory) + Strategy (sync/async). Single entry: CommunicationService.send_message(). Adding a new provider means implementing the provider interface — no changes to the agent or orchestration layer.
MCP (Model Context Protocol)
The platform runs a FastMCP server at /mcp, exposing selected tools over streamable HTTP transport. This allows external AI systems to call platform tools directly.
See Tools & MCP for the full MCP technical details.
ERP & CRM integrations
For customer-specific systems not covered by the standard integrations:
| System type | Integration approach | Examples |
|---|---|---|
| ERP (SAP, Oracle) | Custom tool implementation in app/functions/ + API connector | SAP S/4HANA, Oracle Fusion |
| CRM | Custom tool via ProjectX object_action or direct API | Salesforce, HubSpot |
| OMS | Custom tool or ProjectX integration | Customer-specific OMS |
| TOS (Terminal Operating System) | Custom tool for port deployments | Mainsail, eModal, CiTAS |
Custom integrations follow the same pattern: define the tool in tools.json, implement the function, assign to agents. See Tools & MCP for the step-by-step.
Webhook handling
External systems send events to the platform via webhooks:
| Provider | Webhook endpoint | Auth |
|---|---|---|
| ElevenLabs | /api/webhook/elevenlabs | HMAC signature (ELEVENLABS_WEBHOOK_SECRET) |
| Twilio | /api/webhook/twilio | Twilio request signature |
| Meta WhatsApp | /api/webhook/meta | Meta signature verification |
Each webhook is validated using the provider’s HMAC/signature mechanism before processing.
Sources
- agent-platform repo:
app/communication/ - agent-platform repo:
app/integrations/ - Voice Agent Cost Structure & Deployment
- See Tools & MCP for the tool registry and MCP server
- See The agent-platform repo for the full code structure
Changelog
- 26 May 2026: Full content from GitHub repo analysis. Integration inventory, communication providers, webhook handling.