You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/deploy-mcp/SKILL.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: deploy-mcp
3
-
description: Deploy the everyrow MCP server to staging or production on GKE. Use when the user wants to deploy, redeploy, roll back, scale replicas, or check deployment status. Triggers on deploy, redeploy, staging, production, rollout, scale, replicas.
3
+
description: Deploy the FutureSearch MCP server to staging or production on GKE. Use when the user wants to deploy, redeploy, roll back, scale replicas, or check deployment status. Triggers on deploy, redeploy, staging, production, rollout, scale, replicas.
4
4
---
5
5
6
6
# Deploying the MCP Server
@@ -39,10 +39,10 @@ gh run list --workflow="Deploy MCP Server" --limit 3
39
39
gh run watch <run-id>
40
40
41
41
# Check pod rollout
42
-
kubectl rollout status deploy/everyrow-mcp-staging -n everyrow-mcp-staging --timeout=5m
42
+
kubectl rollout status deploy/futuresearch-mcp-staging -n futuresearch-mcp-staging --timeout=5m
43
43
44
44
# Verify pods are running
45
-
kubectl get pods -n everyrow-mcp-staging -o wide
45
+
kubectl get pods -n futuresearch-mcp-staging -o wide
46
46
```
47
47
48
48
## How It Works
@@ -62,7 +62,7 @@ The deploy uses `--atomic` so it auto-rolls back on failure.
Copy file name to clipboardExpand all lines: .claude/skills/run-mcp-local/SKILL.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,17 @@
1
1
---
2
2
name: run-mcp-local
3
-
description: Run the everyrow HTTP MCP server locally with Docker Compose and optionally expose it via Cloudflare tunnel. Use when starting/stopping the local MCP server, debugging startup issues, connecting Claude.ai or Claude Desktop to a local instance, or checking server logs. Triggers on mcp local, mcp server, run mcp, mcp docker, mcp tunnel, cloudflare tunnel, mcp logs.
3
+
description: Run the FutureSearch HTTP MCP server locally with Docker Compose and optionally expose it via Cloudflare tunnel. Use when starting/stopping the local MCP server, debugging startup issues, connecting Claude.ai or Claude Desktop to a local instance, or checking server logs. Triggers on mcp local, mcp server, run mcp, mcp docker, mcp tunnel, cloudflare tunnel, mcp logs.
4
4
---
5
5
6
-
# Running the everyrow MCP Server Locally
6
+
# Running the FutureSearch MCP Server Locally
7
7
8
-
Two-container stack: **mcp-server** (FastAPI on :8000) and **redis** (on :6379), orchestrated by `everyrow-mcp/deploy/docker-compose.yaml` with local overrides.
8
+
Two-container stack: **mcp-server** (FastAPI on :8000) and **redis** (on :6379), orchestrated by `futuresearch-mcp/deploy/docker-compose.yaml` with local overrides.
9
9
10
10
## Pre-flight Checks
11
11
12
12
**CRITICAL: Always check for stale processes on port 8000 before starting.**
13
13
14
-
A leftover `everyrow-mcp --no-auth` or similar process on the host will shadow the Docker container's port binding. All requests hit the stale process instead of the container — this can look like auth routes are broken, sheets tools are missing, etc.
14
+
A leftover `futuresearch-mcp --no-auth` or similar process on the host will shadow the Docker container's port binding. All requests hit the stale process instead of the container — this can look like auth routes are broken, sheets tools are missing, etc.
@@ -55,7 +55,7 @@ These are templated in `docker-compose.local.yaml` as `${VAR:-default}` — the
55
55
56
56
## Secrets
57
57
58
-
The `.env` file at `everyrow-mcp/deploy/.env` contains production secrets (Supabase, API keys, upload secret). It is already present and should NOT be committed or overwritten.
58
+
The `.env` file at `futuresearch-mcp/deploy/.env` contains production secrets (Supabase, API keys, upload secret). It is already present and should NOT be committed or overwritten.
59
59
60
60
`REDIS_PASSWORD` is intentionally NOT in `.env` — always pass it as an env var (`testpass` for local dev).
61
61
@@ -64,8 +64,8 @@ The `.env` file at `everyrow-mcp/deploy/.env` contains production secrets (Supab
64
64
The `.env` file is gitignored and won't exist in worktrees. Symlink it:
0 commit comments