Alex Tryshchenko
Senior Engineering Manager @ Typeform
tryshchenko.com|otry.eu
- 01
- 02
- 03
- 04
- 05
Learn Many Times - Write Many Times
Fictional conversation. Not based on real messages from real people.
Long Tail
you still own
Auth bridge
user ↔ iPaaS handshake
Entry point abstraction
your API layer over iPaaS
Field mapping UI
logic is in iPaaS, UI is yours
Circuit breaker
before requests reach iPaaS
Integration catalogue
active, inactive, broken
Error notifications
User-facing SLA
your users blame you, not the vendor
iPaaS platform
iPaaS handles
OAuth to destination
Adapter implementation
Field mapping logic + storage
Deprecation management
Retry + backoff
Dead letter queue
shared layer
you both own
Data residency
Compliance
Customer requests
Monitoring and observability
Inbound vs Outbound MCP
Inbound MCP
External agents
orchestrate you
You expose an MCP server. External systems use it to read your data, trigger your actions, and fit you into their workflows.
Claude
ChatGPT
SaaS agents
Your MCP server
Outbound MCP
Your agent accesses
other systems
You run an agent. It uses MCP clients to talk to external tools, read their schemas, and execute actions on your behalf.
Your agent
Salesforce MCP
Notion MCP
Slack MCP
Gap
Gap
Gap
✓
What Did We Learn Today?
- Integrations are hard, with a wide surface of edge cases.
- LLMs have simplified some tasks, but created many others. AI doesn't solve it as a domain. At least not yet.
- Inbound MCP is a must in 2026. Outbound MCP is still a wildcard.
- Having MCP and traditional integration with the same vendor is normal. Sometimes 2×MCP and 2×integration.
- There's no cheap way to abstract integrations. Neither is there a cheap way to outsource them.
- Security and governance need to be considered before making technical decisions.
Questions?
otry.eu / tryshchenko.com