The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the UseMyContext listing page.
MIT license | usemycontext.ai | Docs | usemycontext SDK on npm
UseMyContext is the personal context layer for AI. You keep one profile of who you are and what you are working on, and any AI client reads it over MCP. This plugin brings that into the terminal: sign in once and Claude Code answers with your context already in the room - who you are, what this project is to you, what your documents say. And it does not wait to be asked: when a question touches you personally, Claude Code is guided to check your profile and documents before saying it does not know about you - you should not have to name UseMyContext by hand.
No pasting your background into every session. The context is already there, scoped to the folder you are in.
Then run /mcp, select usemycontext, and complete the browser sign-in.
You will need:
/plugin support).Sign-in is OAuth in the browser; no token is written to any file. This repo is also the plugin's
marketplace, which is why the install is two commands. The second command is plugin@marketplace;
both happen to be named usemycontext. Full reference docs, including the .umc format and the two
connection modes, are in usemycontext/README.md.
No signup needed. At the browser sign-in, use demo@usemycontext.ai with code 424242
(fixed - no email access needed). A shared, read-only demo account with a full profile, files, and a
shared context. Then ask Claude Code "what do you know about me?". Docs:
usemycontext.ai/docs
You are never locked in:
/mcp and disconnect usemycontext.Revoking is enforced on the server: the token dies immediately, everywhere. Nothing needs cleaning up locally.
Ask Claude Code things like "what do you know about me?", "summarize my notes on the Q3 launch", or
"how many rows in expenses.csv are over 500?" - it reads your profile, searches and opens your files,
answers from your documents with cited passages, and runs exact counts and sums over your spreadsheets.
A /umc skill checks or changes which profile a folder reads, and a SessionStart hook points every new
session at the right project automatically.
Under the hood: the UseMyContext MCP server at https://mcp.usemycontext.ai/mcp (Streamable HTTP,
OAuth 2.1) with the tools profile, list_profiles, info, account, list_files, search_files, get_file,
search, fetch (thin aliases of search_files/get_file for ChatGPT deep-research compatibility),
ask_docs, query_table, suggest_update, shared_context - all read-only against your files. One tool,
suggest_update, can write: it files a pending suggestion that you review and approve in the web app.
Nothing the AI does ever edits your profile or your files directly, and every access leaves a record in your
audit trail. When a conversation is wrapping up having surfaced something new and durable about you, Claude
Code is guided to offer that save before the context is lost - so the loop closes at both ends: your context
is read at the start of a session, and what the session taught is offered back at the end.
A work repo reads your @work profile. A side project reads your @personal one. Same terminal, different context, chosen by the folder you are in.
To bind a folder to a project, drop a .umc file in the repo root
(usemycontext/.umc.example is a ready-made template):
A projectId may only be letters, digits, _ and -, up to 32 characters, and a handle only @
followed by letters, digits and -, up to 40. Anything else and the whole marker is ignored, so a
repository you did not write cannot use one to talk to your assistant.
projectId is what scopes the reads. handle is an optional readable label. Find both in the web app
on the project's page, or just ask the /umc skill to create the file for you. With no .umc, the
folder reads your account's active profile.
suggest_update, files a pending suggestion that
you review and approve in the web app./mcp or from the web app's Connect page.What does the AI actually see? The profile you wrote and the files you uploaded to UseMyContext, scoped to the connected or mapped project. Nothing else.
Can it see my other projects? The server only ever serves projects you own. With the default account-wide sign-in, a folder reads its mapped project (or your active profile), and a request for any project that is not yours is refused. If you want hard isolation per repo, use a single-project sign-in: that token is scoped to one project and cannot read the others.
Does it phone home from my repo? No. The plugin reads only the local .umc marker to know which
profile to use. It never uploads your code or files; the only thing that travels is Claude's tool calls
to your UseMyContext account.
What does it cost? The plugin is free and MIT-licensed. UseMyContext has a free tier that covers trying all of this; paid tiers are at usemycontext.ai/pricing.