point-topic-mcp 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- point_topic_mcp-0.1.0/.dev/aws_lambda_mcp_analysis.md +210 -0
- point_topic_mcp-0.1.0/.dev/cloudflare_mcp_capabilities.md +131 -0
- point_topic_mcp-0.1.0/.dev/cloudflare_quick_summary.md +43 -0
- point_topic_mcp-0.1.0/.dev/cloudflare_workers_pricing.md +67 -0
- point_topic_mcp-0.1.0/.dev/external_docs/mcp_inspector_docs.md +461 -0
- point_topic_mcp-0.1.0/.dev/external_docs/mcp_transport_auth_requirements.md +90 -0
- point_topic_mcp-0.1.0/.dev/external_docs/official_mcp_sdk_readme.md +2161 -0
- point_topic_mcp-0.1.0/.dev/github_oauth_setup.md +59 -0
- point_topic_mcp-0.1.0/.dev/oauth_testing_guide.md +120 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/agent_handoff_mcp_deployment.md +114 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/api_key_auth_fix.md +107 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/api_key_authentication_handoff.md +177 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/api_key_authentication_success.md +125 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/clean_implementation_plan.md +131 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/cloudflare_hosting_investigation_report.md +242 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/cloudflare_hosting_prompt.md +51 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/dataset_mcp_implementation.md +69 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/ec2_deployment_guide.md +129 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/final_summary.md +76 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/http_migration_plan.md +88 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/mcp_authentication_implementation.md +307 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/mcp_authentication_revelation.md +119 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/mcp_chat_client_handoff.md +210 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/official_mcp_sdk_implementation_guide.md +377 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/phase_2_handoff_authentication.md +332 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/pypi_distribution_final.md +53 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/pypi_distribution_setup.md +64 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/session_recap_and_architecture_review.md +172 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/troubleshooting_report.md +144 -0
- point_topic_mcp-0.1.0/.dev/progress_reports/user_permissions_guide.md +255 -0
- point_topic_mcp-0.1.0/.env.example +7 -0
- point_topic_mcp-0.1.0/.gitignore +20 -0
- point_topic_mcp-0.1.0/.python-version +1 -0
- point_topic_mcp-0.1.0/PKG-INFO +266 -0
- point_topic_mcp-0.1.0/README.md +244 -0
- point_topic_mcp-0.1.0/deploy_local.sh +3 -0
- point_topic_mcp-0.1.0/publish.sh +35 -0
- point_topic_mcp-0.1.0/pyproject.toml +39 -0
- point_topic_mcp-0.1.0/src/__init__.py +0 -0
- point_topic_mcp-0.1.0/src/connectors/__init__.py +0 -0
- point_topic_mcp-0.1.0/src/connectors/snowflake.py +157 -0
- point_topic_mcp-0.1.0/src/context/__init__.py +1 -0
- point_topic_mcp-0.1.0/src/context/datasets/__init__.py +1 -0
- point_topic_mcp-0.1.0/src/context/datasets/upc.py +417 -0
- point_topic_mcp-0.1.0/src/context/datasets/upc_forecast.py +307 -0
- point_topic_mcp-0.1.0/src/context/datasets/upc_take_up.py +247 -0
- point_topic_mcp-0.1.0/src/context/general_db_instructions.py +31 -0
- point_topic_mcp-0.1.0/src/core/context_assembly.py +55 -0
- point_topic_mcp-0.1.0/src/core/utils.py +38 -0
- point_topic_mcp-0.1.0/src/server_local.py +27 -0
- point_topic_mcp-0.1.0/src/tools/__init__.py +5 -0
- point_topic_mcp-0.1.0/src/tools/mcp_tools.py +59 -0
- point_topic_mcp-0.1.0/uv.lock +1034 -0
|
@@ -0,0 +1,210 @@
|
|
|
1
|
+
# AWS Lambda for MCP Server Hosting Analysis
|
|
2
|
+
|
|
3
|
+
## ✅ What AWS Lambda Offers
|
|
4
|
+
|
|
5
|
+
### 🐍 Python Support
|
|
6
|
+
|
|
7
|
+
- ✅ **Full Python package ecosystem**
|
|
8
|
+
- ✅ **FastAPI + FastMCP works perfectly**
|
|
9
|
+
- ✅ **Container image deployment**
|
|
10
|
+
- ✅ **All external dependencies supported**
|
|
11
|
+
- ✅ **Production-ready**
|
|
12
|
+
|
|
13
|
+
### 🚀 Deployment Options
|
|
14
|
+
|
|
15
|
+
#### 1. Container Images (Recommended for MCP)
|
|
16
|
+
|
|
17
|
+
```dockerfile
|
|
18
|
+
FROM public.ecr.aws/lambda/python:3.12
|
|
19
|
+
COPY requirements.txt .
|
|
20
|
+
RUN pip install -r requirements.txt
|
|
21
|
+
COPY . .
|
|
22
|
+
CMD ["main.handler"]
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
#### 2. Lambda Web Adapter
|
|
26
|
+
|
|
27
|
+
- **HTTP API** support via adapter layer
|
|
28
|
+
- **FastAPI/FastMCP** compatibility
|
|
29
|
+
- **URL routing** works normally
|
|
30
|
+
|
|
31
|
+
### 🔧 MCP Integration Approaches
|
|
32
|
+
|
|
33
|
+
#### Option 1: AWS Lambda MCP Library
|
|
34
|
+
|
|
35
|
+
```python
|
|
36
|
+
# Using awslabs/run-model-context-protocol-servers-with-aws-lambda
|
|
37
|
+
from mcp_lambda import McpLambdaServer
|
|
38
|
+
|
|
39
|
+
server = McpLambdaServer()
|
|
40
|
+
# Wraps existing stdio MCP servers
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
#### Option 2: FastMCP + Web Adapter
|
|
44
|
+
|
|
45
|
+
```python
|
|
46
|
+
from fastmcp import FastMCP
|
|
47
|
+
from mcp.server.fastmcp import FastMCPServer
|
|
48
|
+
|
|
49
|
+
app = FastMCP("my-mcp-server")
|
|
50
|
+
|
|
51
|
+
@app.tool()
|
|
52
|
+
def my_tool(input: str) -> str:
|
|
53
|
+
return f"Processed: {input}"
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
## 📊 Pricing Comparison
|
|
57
|
+
|
|
58
|
+
### AWS Lambda Pricing
|
|
59
|
+
|
|
60
|
+
- **Free tier**: 1M requests/month + 400,000 GB-seconds
|
|
61
|
+
- **Requests**: $0.20 per 1M requests
|
|
62
|
+
- **Duration**: $0.0000166667 per GB-second
|
|
63
|
+
- **Additional**: Data transfer, API Gateway costs
|
|
64
|
+
|
|
65
|
+
### Cost Examples
|
|
66
|
+
|
|
67
|
+
#### Example 1: Moderate Traffic
|
|
68
|
+
|
|
69
|
+
- 15M requests/month, 1GB RAM, 200ms duration
|
|
70
|
+
- **AWS Lambda Cost**: ~$18-25/month
|
|
71
|
+
- Requests: $2.80 (14M excess × $0.20)
|
|
72
|
+
- Duration: $4.17 (3M GB-seconds × $0.0000166667)
|
|
73
|
+
- API Gateway: ~$10-15
|
|
74
|
+
- **vs Cloudflare**: $8.00/month (56% savings)
|
|
75
|
+
|
|
76
|
+
#### Example 2: High Traffic
|
|
77
|
+
|
|
78
|
+
- 100M requests/month, 1GB RAM, 200ms duration
|
|
79
|
+
- **AWS Lambda Cost**: ~$85-120/month
|
|
80
|
+
- Requests: $19.80
|
|
81
|
+
- Duration: $33.33
|
|
82
|
+
- API Gateway: $35-70
|
|
83
|
+
- **vs Cloudflare**: $45.40/month (50-60% savings)
|
|
84
|
+
|
|
85
|
+
## ⚡ Performance Characteristics
|
|
86
|
+
|
|
87
|
+
### Cold Starts
|
|
88
|
+
|
|
89
|
+
- **Duration**: 100-1000ms (vs 0ms Cloudflare)
|
|
90
|
+
- **Language impact**: Python slower than Node.js
|
|
91
|
+
- **Container images**: Slower cold starts
|
|
92
|
+
- **Provisioned concurrency**: Available but costly
|
|
93
|
+
|
|
94
|
+
### Regional Deployment
|
|
95
|
+
|
|
96
|
+
- **Single region** by default
|
|
97
|
+
- **Multi-region** requires separate deployments
|
|
98
|
+
- **Global latency** higher than edge deployment
|
|
99
|
+
|
|
100
|
+
## 🚨 Challenges for MCP Hosting
|
|
101
|
+
|
|
102
|
+
### 1. Cold Start Impact
|
|
103
|
+
|
|
104
|
+
- **MCP connections** expect low latency
|
|
105
|
+
- **AI agents** sensitive to response times
|
|
106
|
+
- **User experience** degraded by cold starts
|
|
107
|
+
|
|
108
|
+
### 2. Authentication Complexity
|
|
109
|
+
|
|
110
|
+
- **OAuth implementation** required from scratch
|
|
111
|
+
- **No built-in MCP OAuth** support
|
|
112
|
+
- **Additional services** needed (Cognito, Auth0)
|
|
113
|
+
|
|
114
|
+
### 3. Cost Structure
|
|
115
|
+
|
|
116
|
+
- **API Gateway charges** add significant cost
|
|
117
|
+
- **Data transfer** fees for global access
|
|
118
|
+
- **Provisioned concurrency** expensive for always-on
|
|
119
|
+
|
|
120
|
+
### 4. Operational Overhead
|
|
121
|
+
|
|
122
|
+
- **VPC networking** complexity for database access
|
|
123
|
+
- **IAM role management**
|
|
124
|
+
- **CloudWatch logging** and monitoring setup
|
|
125
|
+
- **Deployment pipeline** configuration
|
|
126
|
+
|
|
127
|
+
## ✅ AWS Advantages
|
|
128
|
+
|
|
129
|
+
### 1. Ecosystem Integration
|
|
130
|
+
|
|
131
|
+
- **RDS/DynamoDB** native integration
|
|
132
|
+
- **Secrets Manager** for secure config
|
|
133
|
+
- **CloudWatch** comprehensive monitoring
|
|
134
|
+
- **X-Ray** distributed tracing
|
|
135
|
+
|
|
136
|
+
### 2. Enterprise Features
|
|
137
|
+
|
|
138
|
+
- **VPC networking**
|
|
139
|
+
- **Advanced security** controls
|
|
140
|
+
- **Compliance** certifications
|
|
141
|
+
- **Support tiers**
|
|
142
|
+
|
|
143
|
+
### 3. Mature Platform
|
|
144
|
+
|
|
145
|
+
- **Battle-tested** reliability
|
|
146
|
+
- **Extensive documentation**
|
|
147
|
+
- **Large community**
|
|
148
|
+
- **Rich tooling ecosystem**
|
|
149
|
+
|
|
150
|
+
## 🎯 Best Fit Scenarios
|
|
151
|
+
|
|
152
|
+
### AWS Lambda Good For:
|
|
153
|
+
|
|
154
|
+
1. **Complex Python dependencies** required
|
|
155
|
+
2. **Existing AWS infrastructure**
|
|
156
|
+
3. **Enterprise compliance** needs
|
|
157
|
+
4. **Database integration** critical
|
|
158
|
+
5. **Advanced monitoring** required
|
|
159
|
+
|
|
160
|
+
### AWS Lambda NOT Ideal For:
|
|
161
|
+
|
|
162
|
+
1. **Global low-latency** requirements
|
|
163
|
+
2. **Cost-sensitive** projects
|
|
164
|
+
3. **Simple MCP servers**
|
|
165
|
+
4. **Rapid prototyping**
|
|
166
|
+
5. **OAuth complexity** aversion
|
|
167
|
+
|
|
168
|
+
## 🚀 Alternative AWS Options
|
|
169
|
+
|
|
170
|
+
### 1. AWS App Runner
|
|
171
|
+
|
|
172
|
+
- **Container-based** deployment
|
|
173
|
+
- **Auto-scaling**
|
|
174
|
+
- **Always-warm** (no cold starts)
|
|
175
|
+
- **Higher cost** but better performance
|
|
176
|
+
|
|
177
|
+
### 2. ECS Fargate
|
|
178
|
+
|
|
179
|
+
- **Container orchestration**
|
|
180
|
+
- **Global deployment** via multiple regions
|
|
181
|
+
- **Always-running** instances
|
|
182
|
+
- **More expensive** than Lambda
|
|
183
|
+
|
|
184
|
+
### 3. AWS Lambda@Edge
|
|
185
|
+
|
|
186
|
+
- **CloudFront edge** deployment
|
|
187
|
+
- **Global distribution**
|
|
188
|
+
- **Limited runtime** and package size
|
|
189
|
+
- **Not suitable** for complex MCP servers
|
|
190
|
+
|
|
191
|
+
## 📋 Migration Considerations
|
|
192
|
+
|
|
193
|
+
### From Current Setup to AWS
|
|
194
|
+
|
|
195
|
+
1. **Containerize** existing FastMCP server
|
|
196
|
+
2. **Add Lambda Web Adapter** layer
|
|
197
|
+
3. **Implement OAuth** authentication
|
|
198
|
+
4. **Set up API Gateway** routing
|
|
199
|
+
5. **Configure monitoring** and logging
|
|
200
|
+
|
|
201
|
+
### Estimated Migration Effort
|
|
202
|
+
|
|
203
|
+
- **Development**: 2-3 weeks
|
|
204
|
+
- **Testing**: 1 week
|
|
205
|
+
- **Deployment setup**: 1 week
|
|
206
|
+
- **Total**: 4-5 weeks vs 1-2 days Cloudflare
|
|
207
|
+
|
|
208
|
+
## 🎯 Bottom Line
|
|
209
|
+
|
|
210
|
+
AWS Lambda works for MCP servers but requires **significant additional complexity** and **higher costs** compared to Cloudflare's native MCP support. Best for scenarios requiring **complex Python dependencies** or **deep AWS integration**.
|
|
@@ -0,0 +1,131 @@
|
|
|
1
|
+
# Cloudflare MCP Server Capabilities
|
|
2
|
+
|
|
3
|
+
## ✅ What Cloudflare Offers for MCP
|
|
4
|
+
|
|
5
|
+
### 🎯 Native MCP Support
|
|
6
|
+
|
|
7
|
+
- **McpAgent class** in Agents SDK - built-in MCP server capabilities
|
|
8
|
+
- **Streamable HTTP transport** - latest MCP standard supported
|
|
9
|
+
- **SSE transport** - backward compatibility with existing clients
|
|
10
|
+
- **OAuth 2.1 provider** - built-in authentication/authorization
|
|
11
|
+
- **Durable Objects** - stateful MCP servers with SQL storage
|
|
12
|
+
|
|
13
|
+
### 🚀 Deployment Options
|
|
14
|
+
|
|
15
|
+
#### 1. TypeScript/JavaScript MCP Servers
|
|
16
|
+
|
|
17
|
+
- ✅ **Full production support**
|
|
18
|
+
- ✅ **One-click deployment** templates
|
|
19
|
+
- ✅ **Complete package ecosystem**
|
|
20
|
+
- ✅ **OAuth provider included**
|
|
21
|
+
- ✅ **Auto-scaling and hibernation**
|
|
22
|
+
|
|
23
|
+
#### 2. Python MCP Servers
|
|
24
|
+
|
|
25
|
+
- ⚠️ **BETA - Limited production support**
|
|
26
|
+
- ✅ **FastAPI supported** (local dev only)
|
|
27
|
+
- ❌ **No external packages in production**
|
|
28
|
+
- ❌ **Standard library only**
|
|
29
|
+
- ⚠️ **Development experience rough**
|
|
30
|
+
|
|
31
|
+
## 🔧 Built-in Features
|
|
32
|
+
|
|
33
|
+
### Authentication & Authorization
|
|
34
|
+
|
|
35
|
+
```typescript
|
|
36
|
+
// Automatic OAuth handling
|
|
37
|
+
class MyMcpServer extends McpAgent {
|
|
38
|
+
// User details automatically provided
|
|
39
|
+
async myTool(input, user) {
|
|
40
|
+
// user.id, user.email available
|
|
41
|
+
}
|
|
42
|
+
}
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
### State Management
|
|
46
|
+
|
|
47
|
+
- **Durable Objects** with SQLite storage
|
|
48
|
+
- **Automatic hibernation** during idle periods
|
|
49
|
+
- **Global state persistence**
|
|
50
|
+
|
|
51
|
+
### Transport Support
|
|
52
|
+
|
|
53
|
+
- **Streamable HTTP** (latest MCP spec)
|
|
54
|
+
- **Server-Sent Events** (SSE) for compatibility
|
|
55
|
+
- **WebSocket** with hibernation support
|
|
56
|
+
|
|
57
|
+
## 🛠️ Development Experience
|
|
58
|
+
|
|
59
|
+
### Local Development
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
npm create cloudflare@latest my-mcp-server \
|
|
63
|
+
--template=cloudflare/ai/demos/remote-mcp-authless
|
|
64
|
+
npm start # http://localhost:8788/sse
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### Testing
|
|
68
|
+
|
|
69
|
+
- **MCP Inspector** integration
|
|
70
|
+
- **AI Playground** as remote MCP client
|
|
71
|
+
- **Claude Desktop** via mcp-remote proxy
|
|
72
|
+
|
|
73
|
+
### Deployment
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
npx wrangler@latest deploy
|
|
77
|
+
# Instant global deployment
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
## 🌍 Global Infrastructure
|
|
81
|
+
|
|
82
|
+
- **285+ edge locations**
|
|
83
|
+
- **Automatic global distribution**
|
|
84
|
+
- **Zero cold starts**
|
|
85
|
+
- **Built-in DDoS protection**
|
|
86
|
+
|
|
87
|
+
## 📋 Supported MCP Features
|
|
88
|
+
|
|
89
|
+
✅ **Tools** - Function calls from AI agents
|
|
90
|
+
✅ **Resources** - Data/content exposure
|
|
91
|
+
✅ **Prompts** - Template management
|
|
92
|
+
✅ **OAuth** - Authentication flows
|
|
93
|
+
✅ **Scoped permissions** - Fine-grained access control
|
|
94
|
+
✅ **Multi-client support** - Multiple simultaneous connections
|
|
95
|
+
|
|
96
|
+
## 🔄 Client Compatibility
|
|
97
|
+
|
|
98
|
+
### Direct Remote Support
|
|
99
|
+
|
|
100
|
+
- **Claude** (via AI Playground)
|
|
101
|
+
- **Windsurf**
|
|
102
|
+
- **Any MCP SDK** with remote transport
|
|
103
|
+
|
|
104
|
+
### Via Proxy (mcp-remote)
|
|
105
|
+
|
|
106
|
+
- **Claude Desktop**
|
|
107
|
+
- **Cursor**
|
|
108
|
+
- **Cline**
|
|
109
|
+
- **Other stdio-based clients**
|
|
110
|
+
|
|
111
|
+
## 💰 Pricing for MCP Servers
|
|
112
|
+
|
|
113
|
+
- **Free tier**: 100K requests/day, 10ms CPU time
|
|
114
|
+
- **Paid**: $5/month + usage (very cost-effective)
|
|
115
|
+
- **No bandwidth charges**
|
|
116
|
+
- **Global deployment included**
|
|
117
|
+
|
|
118
|
+
## 🚨 Current Gaps
|
|
119
|
+
|
|
120
|
+
- **Python production limitations** (packages not supported)
|
|
121
|
+
- **Learning curve** for McpAgent class
|
|
122
|
+
- **Beta status** for some features
|
|
123
|
+
- **Documentation still evolving**
|
|
124
|
+
|
|
125
|
+
## 🎯 Best Use Cases
|
|
126
|
+
|
|
127
|
+
1. **TypeScript/JavaScript MCP servers** - Excellent choice
|
|
128
|
+
2. **Global distribution needs** - Perfect fit
|
|
129
|
+
3. **OAuth authentication required** - Built-in support
|
|
130
|
+
4. **Cost-sensitive projects** - Very competitive pricing
|
|
131
|
+
5. **Rapid prototyping** - One-click deployment
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
# Cloudflare Hosting Quick Summary
|
|
2
|
+
|
|
3
|
+
## 🚨 TL;DR: Python Workers Not Production Ready
|
|
4
|
+
|
|
5
|
+
**Bottom line**: Cloudflare Workers are AMAZING for MCP servers... but **Python packages don't work in production** (beta limitation).
|
|
6
|
+
|
|
7
|
+
## ✅ What's Great About Cloudflare
|
|
8
|
+
|
|
9
|
+
- **Native MCP support** with McpAgent class
|
|
10
|
+
- **50-80% cost savings** vs AWS Lambda
|
|
11
|
+
- **0ms cold starts** globally (vs 100-1000ms AWS)
|
|
12
|
+
- **Built-in OAuth** authentication
|
|
13
|
+
- **Global edge deployment** at 285+ locations
|
|
14
|
+
- **$5/month minimum** + usage-based pricing
|
|
15
|
+
|
|
16
|
+
## ❌ The Python Problem
|
|
17
|
+
|
|
18
|
+
- Python Workers in **beta only**
|
|
19
|
+
- **No packages in production** (FastAPI, FastMCP, etc.)
|
|
20
|
+
- Only **standard library** supported
|
|
21
|
+
- Our existing server **won't work**
|
|
22
|
+
|
|
23
|
+
## 🎯 Recommendation
|
|
24
|
+
|
|
25
|
+
**Migrate to TypeScript + McpAgent** (~2-3 weeks effort)
|
|
26
|
+
|
|
27
|
+
- Use Snowflake HTTP API instead of Python connector
|
|
28
|
+
- Keep existing Python server as backup
|
|
29
|
+
- Unlock all Cloudflare benefits
|
|
30
|
+
|
|
31
|
+
## 📁 Files Created
|
|
32
|
+
|
|
33
|
+
- `cloudflare_workers_pricing.md` - Detailed cost analysis
|
|
34
|
+
- `cloudflare_mcp_capabilities.md` - Platform features
|
|
35
|
+
- `aws_lambda_mcp_analysis.md` - AWS comparison
|
|
36
|
+
- `cloudflare_hosting_investigation_report.md` - Full report with migration plan
|
|
37
|
+
|
|
38
|
+
## 🚀 Alternative: AWS Lambda
|
|
39
|
+
|
|
40
|
+
- **Keeps Python** but costs 2x more
|
|
41
|
+
- **Slower performance** (cold starts)
|
|
42
|
+
- **More complexity** (OAuth setup)
|
|
43
|
+
- **Regional deployment** only
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
# Cloudflare Workers Pricing Analysis
|
|
2
|
+
|
|
3
|
+
## 🆓 Free Tier
|
|
4
|
+
|
|
5
|
+
- **100,000 requests per day**
|
|
6
|
+
- **10ms CPU time per invocation**
|
|
7
|
+
- No duration charges
|
|
8
|
+
- **No bandwidth/egress charges**
|
|
9
|
+
|
|
10
|
+
## 💰 Paid Plan ($5/month minimum)
|
|
11
|
+
|
|
12
|
+
- **10 million requests included** + $0.30 per additional million
|
|
13
|
+
- **30 million CPU milliseconds included** + $0.02 per additional million CPU-ms
|
|
14
|
+
- Max 5 minutes CPU time per invocation (default: 30 seconds)
|
|
15
|
+
- **No duration or bandwidth charges**
|
|
16
|
+
|
|
17
|
+
## 📊 Cost Examples
|
|
18
|
+
|
|
19
|
+
### Example 1: Moderate Traffic MCP Server
|
|
20
|
+
|
|
21
|
+
- 15M requests/month, 7ms CPU time per request
|
|
22
|
+
- **Monthly Cost: $8.00**
|
|
23
|
+
- Subscription: $5.00
|
|
24
|
+
- Requests: $1.50 (5M excess × $0.30)
|
|
25
|
+
- CPU time: $1.50 (75M excess CPU-ms × $0.02)
|
|
26
|
+
|
|
27
|
+
### Example 2: High Traffic MCP Server
|
|
28
|
+
|
|
29
|
+
- 100M requests/month, 7ms CPU time per request
|
|
30
|
+
- **Monthly Cost: $45.40**
|
|
31
|
+
- Subscription: $5.00
|
|
32
|
+
- Requests: $27.00 (90M excess × $0.30)
|
|
33
|
+
- CPU time: $13.40 (670M excess CPU-ms × $0.02)
|
|
34
|
+
|
|
35
|
+
### Example 3: Cron-Based Data Processing
|
|
36
|
+
|
|
37
|
+
- 720 requests/month, 3 minutes CPU time per request
|
|
38
|
+
- **Monthly Cost: $6.99**
|
|
39
|
+
- Subscription: $5.00
|
|
40
|
+
- CPU time: $1.99 (99.6M excess CPU-ms × $0.02)
|
|
41
|
+
|
|
42
|
+
## 🔑 Key Advantages
|
|
43
|
+
|
|
44
|
+
- **CPU-time based billing** - no charges for I/O wait time
|
|
45
|
+
- **Zero cold start latency** globally (V8 isolates)
|
|
46
|
+
- **Global edge deployment** at 285+ locations
|
|
47
|
+
- **Free static asset serving**
|
|
48
|
+
- **No egress/bandwidth charges**
|
|
49
|
+
- **Built-in DDoS protection**
|
|
50
|
+
|
|
51
|
+
## ⚡ Performance Benefits
|
|
52
|
+
|
|
53
|
+
- ~0ms cold starts (vs AWS Lambda 100-1000ms)
|
|
54
|
+
- Global edge execution
|
|
55
|
+
- Built-in auto-scaling
|
|
56
|
+
- No infrastructure management
|
|
57
|
+
|
|
58
|
+
## 🚨 Current Limitations for Python
|
|
59
|
+
|
|
60
|
+
- **Python Workers in BETA**
|
|
61
|
+
- **Packages DO NOT run in production** (only standard library)
|
|
62
|
+
- FastAPI works but limited to built-in packages only
|
|
63
|
+
- Must use `python_workers` compatibility flag
|
|
64
|
+
|
|
65
|
+
## 💡 Bottom Line
|
|
66
|
+
|
|
67
|
+
**Cloudflare Workers pricing is VERY competitive** - typically 40-80% cheaper than AWS Lambda for similar workloads, with better performance and global distribution.
|