CUSTOMER SUCCESS STORY

How Composio Scaled Their MCP Infrastructure with Vercel

When Composio needed to scale their Model Context Protocol (MCP) servers to handle massive growth, they migrated to Vercel Functions. Infrastructure headaches disappeared and deployment times dropped from 10 minutes to 2 minutes.

80%
Faster Deployments
3-4 hrs
Migration Time
250+
Apps Integrated
10K+
Actions Available

About Composio

Composio delivers instant, fully managed access to over 250 Apps via Model Context Protocol (MCP) servers with 10,000+ actions - enabling AI agents to effortlessly interact with popular SaaS and system tools.

As one of the largest MCP providers, Composio uniquely hosts dedicated MCP servers for each integration, managing authentication, rate limiting, and multi-tenant isolation at scale.

Explore MCP Registry

What is MCP?

The Model Context Protocol (MCP) standardizes interactions between AI models and external tools via a straightforward JSON-RPC interface.

Standardized AI-tool interactions
JSON-RPC interface
Multi-tenant isolation

When Growth Outpaces Infrastructure

"We were constantly firefighting infrastructure issues instead of building features."

Previous AWS Stack Challenges

Slow Deployments
10-minute deployment cycles delayed hotfixes and new features
Scalability Constraints
Had to keep expensive standby servers running for traffic spikes
Cost Transparency Issues
Unpredictable costs across multiple AWS services
Developer Experience Costs
Managing SSR + SSE sessions + long builds slowed feature development

Technical Stack

Infrastructure:Custom ECS tasks
Frontend:Vite for SSR
Sessions:Custom SSE + Redis
Deployment:Manual AWS processes
Key Pain Points
  • • No middle ground between over-provisioning and downtime risk
  • • Fragmented monitoring across services
  • • Engineering time spent on infrastructure vs. product

Why Vercel Made Sense

"We have long admired Vercel for their exceptional developer experience, streamlined deployment workflows, and dedication to modern development practices."

The Game Changer: Native MCP Support

Initially, MCP's requirement for long-lived SSE connections seemed incompatible with serverless functions. This changed when Vercel introduced native MCP support with the mcp-adapter and Streamable HTTP.

Official mcp-adapter
Streamable HTTP support
Real-time streaming optimized
SSE backward compatibility
ChallengeVercel SolutionImpact
Slow deploymentsIntegrated CI/CD with instant rollbacks10 minutes → 2 minutes
Limited feedback loopsPreview deployments for every PRFaster iteration & collaboration
Complex MCP scalingNative MCP adapter + Streamable HTTPEliminated custom scaling logic
SSR management overheadManaged SSR with optimized edge cachingZero maintenance overhead
Security concernsBuilt-in DDoS protection and firewallEnhanced security without config

A Surprisingly Smooth Migration

"The migration was remarkably smooth, with no significant initial hurdles. We migrated our entire MCP infrastructure to Vercel in just 3–4 hours, significantly exceeding our expectations."
Official mcp-adapter
Handled complex orchestration automatically
Zero Architecture Changes
Existing MCP servers worked without modification
Same-Day Production
Live workloads running within hours

Migration Timeline

1
Hour 1: Setup & Configuration
Initial Vercel project setup and mcp-adapter integration
2
Hours 2-3: Migration & Testing
MCP servers migrated and tested in preview environments
4
Hour 4: Production Deployment
Live production workloads successfully running

Immediate Improvements

5x Faster Deployments

2 min

Down from 10 minutes

Preview Deployments

Every PR

Live testing environments

Zero Infrastructure

0%

Time spent on infrastructure

What Changed for Composio

✅ Now Possible

  • Focus entirely on product development
  • Lightning-fast feedback loops with preview deployments
  • Automatic scaling without manual intervention
  • Predictable costs that scale with usage

❌ No Longer Needed

  • Infrastructure firefighting
  • Manual server capacity planning
  • Custom SSR and session management
  • Long deployment wait times

Addressing the Cost Reality

Initially, the migration to serverless resulted in higher infrastructure costs due to the nature of SSE connections in a serverless environment. However, this created an opportunity for optimization.

The Solution: Streamable HTTP Migration

Working closely with Vercel, Composio transitioned customers from SSE to Streamable HTTP, resulting in better performance and lower costs.

30-day deprecation notice
Customers had time to plan migration
Backward compatibility maintained
Critical integrations kept working during transition
Comprehensive migration guide
Updated CLI and documentation for smooth transition

Cost Optimization Timeline

AWS
Initial
Fluid
StreamableHTTP
COST REDUCTION

By end of month, Streamable HTTP will be the sole supported protocol, with costs continuing to decrease as adoption increases.

What Other MCP Providers Can Learn

Embrace Managed Services

Custom infrastructure requires significant engineering overhead that doesn't differentiate your product. Let someone else handle the plumbing.

Choose Protocols Thoughtfully

While SSE works, Streamable HTTP provides better serverless economics and performance. The right protocol matters for long-term success.

Prioritize Developer Experience

Fast deployments and preview environments compound productivity gains over time. Small improvements create big advantages.

Plan for Growth

Infrastructure decisions made early can become bottlenecks later. Choose platforms that scale with your success, not against it.

"All of this aligns perfectly with our team's culture: Build fast, ship quality, and lean on great tools instead of reinventing them."

Ready to Scale Your MCP Infrastructure?

Learn more about Vercel's MCP support and see how we can help you focus on building instead of managing infrastructure.