Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (create-context-hub) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
create-context-hub
Set up a Claude Context Hub in one command. No cloning, no manual config, no guesswork.
npx create-context-hubThe Problem
Claude.ai, Claude Code, and the Claude App each maintain separate context. Memories saved in one don't exist in another. You re-explain yourself every time you switch devices. There's no official API to bridge them.
What This Creates
A shared MCP server on Cloudflare Workers that all your Claude interfaces connect to simultaneously. It stores:
- Memories — preferences, facts, learnings
- Decisions — what you chose and why
- Projects — descriptions and custom instructions per project
- Instructions — global behavior rules ("always use TypeScript")
- Identity — name, role, expertise, location
- Context Log — breadcrumbs across sessions ("discussed auth on phone at 3pm")
24 MCP tools. Full-text search (FTS5). 3-layer deduplication. Runs on Cloudflare's free tier — $0/month.
How It Works
npx create-context-hub
│
├── 1. Prompts for project name
├── 2. Scaffolds project files (MCP server, migration SQL, configs)
├── 3. Runs npm install
├── 4. Authenticates with Cloudflare (opens browser)
├── 5. Creates a D1 database on your Cloudflare account
├── 6. Patches wrangler.json with the database ID
├── 7. Runs database migration (creates 5 tables + FTS indexes)
├── 8. Deploys to Cloudflare Workers → gives you a live URL
├── 9. (Optional) Generates an API key + sets it as a Wrangler secret
├── 10. (Optional) Runs `claude mcp add` to connect Claude Code
└── 11. Prints Claude.ai/App connector instructions + summaryIf any step fails, the CLI prints the exact command to run manually. The scaffolded project is always valid — worst case, you finish 2-3 steps yourself.
What Gets Deployed
Claude App (Phone) ──────┐
│ Custom Connector (HTTPS)
Claude.ai (Browser) ──────┤
▼
┌──────────────────┐
│ Your MCP Server │ Cloudflare Workers
│ (24 tools) │ Free tier ($0/month)
│ │ Always on, global edge
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Cloudflare D1 │ SQLite database
│ (5GB free) │ 5M reads/day
└──────────────────┘
▲
│ HTTP transport
┌────────┴─────────┐
│ Claude Code │
│ (your laptop) │
└──────────────────┘Requirements
- Node.js 18+
- A free Cloudflare account
- Claude Code (optional, for auto-configuration)
Usage
# Interactive — prompts for project name
npx create-context-hub
# Pass project name directly
npx create-context-hub my-hub
# Scaffold only (skip Cloudflare setup)
# Answer "No" when prompted for Cloudflare setup
npx create-context-hub my-hubWhat Gets Scaffolded
my-hub/
├── src/
│ └── index.ts # MCP server (24 tools, ~1700 lines)
├── migrations/
│ └── 0001_init.sql # Database schema (5 tables + FTS5 indexes)
├── wrangler.json # Cloudflare Workers config (auto-patched with DB ID)
├── package.json # Dependencies: @modelcontextprotocol/sdk, agents
├── tsconfig.json
└── .gitignoreAfter Setup
Once deployed, verify it works:
In Claude.ai or Claude App:
"Who am I? Check your Context Hub."
In Claude Code:
"What do you know about me? Check context hub."
Cross-interface sync:
- On your phone: "Save this thought: consider migrating to tRPC for the dashboard"
- On your laptop: "What was I thinking about on my phone?"
Updating
Your Context Hub is a live MCP server. To update after the main project releases changes:
cd my-hub
git pull origin main # if tracking upstream
npx wrangler deployAll connected Claude sessions pick up changes on their next conversation.
Related
- claude-context-hub — the full project with documentation, tool reference, and comparison with alternatives
License
MIT