A private MCP server built entirely in your AWS account. Captures, embeds, classifies, and semantically searches your thoughts. No third-party API routing — your data never leaves your AWS account.
Requires Node.js 22+, AWS CLI v2 with SSO, CDK CLI (npm install -g aws-cdk), and Bedrock model access enabled for Titan Embeddings v2 and Claude 3 Haiku.
git clone https://github.com/rusty428/private-mcp.git
cd private-mcp
npm install
cp .env.example .env # Add your AWS account ID, region, and credentials
npx cdk bootstrap --profile <your-profile> # First time only
npx cdk deploy PrivateMCPStack --profile <your-profile>After deploy, connect your AI tools using the MCP endpoint from the CDK output. See DEVELOPER.md for full setup including AI tool configuration, web UI deployment, and optional Slack integration.
Every AI coding session starts from zero. Context from yesterday's debugging session, last week's architecture decision, that pattern you discovered in another project — all gone. You either re-explain it or the AI rediscovers it the hard way.
Private MCP gives your AI tools persistent memory:
- Decisions survive sessions — "We chose X over Y because Z" is captured once and searchable forever
- Sessions have continuity — Pick up where you left off. Search for what you were working on, not just which files you touched.
- Cross-project awareness — A solution from project A surfaces when you hit the same problem in project B
- Automatic capture — Hook scripts record session summaries and user prompts without manual effort
- Daily digest — A Slack summary of yesterday's activity across all projects
Once deployed, the workflow is mostly invisible. Hooks capture automatically. Your AI tools use capture_thought as they work. When you need context, search_thoughts finds it by meaning — not keywords, not file paths, not commit hashes.
Capture thoughts from any MCP-connected AI tool, the web UI, or Slack — they get embedded, classified, and stored automatically. Any connected tool (Claude Code, Cursor, Claude Desktop) can then search your thoughts by meaning and capture new ones as you work.
Most of the value comes from what happens automatically. Here's a typical day:
Starting a session — You open Claude Code on a project you haven't touched in a week. You ask "what was I working on last time?" Claude calls search_thoughts, finds your last session summary and the decisions you made, and picks up where you left off. No scrolling through git logs.
During work — You're debugging an auth issue. Claude discovers the root cause and captures: "API Gateway returns 403 when the API key header has a trailing space — the key itself is valid." You don't ask it to. It just does. Meanwhile, the prompt-capture hook is recording your side of the conversation too.
Hitting a familiar problem — You run into an S3 Vectors quirk. Claude searches your thoughts and finds a note from three weeks ago in a different project: "S3 Vectors rejects empty arrays in metadata — filter them out before PutVectors." Problem solved in seconds instead of another hour of debugging.
End of session — You close Claude Code. The SessionEnd hook fires, captures a summary of what you did, what decisions were made, and what's left to do.
Next morning — A Slack message is waiting: yesterday's daily summary across all your projects. Two bugs fixed in project A, a new feature started in project B, and a decision captured in project C about which database to use.
A week later — "Why did we use DynamoDB instead of Postgres?" You don't remember which session, which project, or when. Doesn't matter — search_thoughts finds the decision by meaning.
| Source | How it works | What it captures |
|---|---|---|
| Claude Code (MCP) | Claude calls capture_thought on its own when it makes decisions or discovers something worth remembering |
Decisions, patterns, solutions, architecture notes |
| Prompt hooks | Fires on every message you send | Your questions, instructions, context you provided |
| Session hooks | Fires when a session ends | Session summary: what was done, what's next |
| Slack | Post to a channel, bot captures it | Quick thoughts, links, ideas you want to remember |
| Web UI | Manual capture form | Anything you want to explicitly save |
You don't need to change how you work. Deploy it, connect your tools, and it starts building your knowledge base from day one.
-
Capture — Send a thought from any MCP-connected AI tool, the web UI, or Slack. A Lambda generates a vector embedding (Bedrock Titan v2) and extracts metadata (Bedrock Haiku) in parallel, then stores everything in S3 Vectors and DynamoDB.
-
Retrieve — Search your thoughts by meaning, browse recent entries, view stats, or generate narrative reports — from any connected tool or the web dashboard.
AI Tools ──MCP──▶ API Gateway ──▶ mcp-server Lambda
(x-api-key) │
▼
process-thought Lambda
│ │
▼ ▼
Bedrock Bedrock
(Titan Embed) (Haiku classify)
│ │
└─────┬─────┘
▼
S3 Vectors
Slack ──webhook──▶ API Gateway ──▶ ingest-thought Lambda ──▶ process-thought
- CDK v2 (TypeScript) — all infrastructure as code
- S3 Vectors — vector storage with cosine similarity search
- DynamoDB — thought metadata, enrichment settings, query indexes
- Bedrock — Amazon Titan Embeddings v2 + Claude 3 Haiku
- API Gateway — REST API with API key auth
- Lambda — Node.js 22, esbuild bundling
- Web UI — Vite + React + Cloudscape Design System (dashboard, browse, search, capture, reports, settings)
- Slack — optional capture source via webhook
| Tool | Description |
|---|---|
search_thoughts |
Semantic search — find thoughts by meaning, not keywords |
browse_recent |
List recent thoughts, filter by type or topic |
stats |
Overview: total count, type breakdown, top topics, date range |
capture_thought |
Save a thought from any connected AI tool |
daily_summary |
Generate a daily summary of recent activity |
- All data stays in your AWS account — no external services, no telemetry, no phone-home
- The hook scripts capture session summaries and user prompts automatically — review them before installing to understand what's recorded
- Thought content is sent to Amazon Bedrock for embedding and classification — review Bedrock's data privacy policy for how your data is handled
- This is a single-tenant system — no data is shared between users
All services run on pay-per-use pricing. At ~20 thoughts/day, expect < $1/month.
- DEVELOPER.md — Setup, deployment, and configuration
- ARCHITECTURE.md — Detailed architecture and design decisions