io.github.usemycontext/usemycontext MCP Server

The io.github.usemycontext/usemycontext MCP server provides a personal context layer for AI by exposing a user profile and files to any MCP client over OAuth. The server is positioned as “your profile and files” that can be read by MCP clients, enabling context sharing across AI tools.

🛠️ Key Features

Personal context layer
Exposes a profile and files
Readable by any MCP client
Uses OAuth for access
Matches topics: AI, Claude Code, context-layer, MCP, personal-context, plugin

🚀 Use Cases

Supplying personal profile data to MCP-based AI workflows
Providing file-based context to MCP clients via OAuth

⚡ Developer Benefits

Standard MCP client access to user context
OAuth-based authorization for context reading
Clear scope: profile and files for AI consumption

⚠️ Limitations

Context described is limited to profile and files; no other data types are stated.

UseMyContext for Claude Code

MIT license | usemycontext.ai | 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.

What it looks like

code

cd ~/code/acme-api
claude

> Who am I, and what is this project to me?

  This folder is mapped to your @work context. You're a backend engineer
  at Acme, this repo is the payments API you own, and your notes say the
  current focus is the v2 billing migration. Want me to pull the migration
  checklist from your files?

No pasting your background into every session. The context is already there, scoped to the folder you are in.

Install

code

/plugin marketplace add usemycontext/claude-code-plugin
/plugin install usemycontext@usemycontext

Then run /mcp, select usemycontext, and complete the browser sign-in.

You will need:

A UseMyContext account. The free tier is enough to try this. No account yet? Create a free one at usemycontext.ai first.
A current Claude Code (any version with /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.

Disconnecting and revoking

You are never locked in:

In Claude Code, run /mcp and disconnect usemycontext.
Or revoke from the UseMyContext web app: the Connect page lists every AI connected right now, each with its own Disconnect button, plus a "Disconnect all".

Revoking is enforced on the server: the token dies immediately, everywhere. Nothing needs cleaning up locally.

What you get

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 eight tools - profile, list_files, search_files, get_file, 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 read is logged to your audit trail.

One folder, one context

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):

code

projectId=p2
handle=@work

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.

What it can and cannot do

Reads: your profile and the files you uploaded to UseMyContext, scoped to the connected or mapped project.
Writes: nothing to your files. The one write tool, suggest_update, files a pending suggestion that you review and approve in the web app.
Every read is logged to your audit trail.
You can revoke access at any time, from /mcp or from the web app's Connect page.
It does not change your Anthropic account, your Claude Code login, your billing, or which model runs.

Questions you probably have

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.

Repo layout (for contributors)

code

.
|-- .claude-plugin/
|   `-- marketplace.json      # the marketplace catalog (one plugin: usemycontext)
`-- usemycontext/             # the plugin
    |-- .claude-plugin/
    |   `-- plugin.json        # plugin manifest
    |-- .mcp.json              # registers the remote UseMyContext MCP server (OAuth)
    |-- skills/umc/SKILL.md    # the /umc skill (status + folder mapping)
    |-- hooks/hooks.json       # SessionStart hook
    |-- scripts/umc-session.sh # reads a folder's .umc marker
    |-- .umc.example           # example folder mapping
    `-- README.md              # reference docs for the plugin

query	string	required	What to find in the user's documents (a question or topic).
k	integer	optional	How many passages to return (default 12, max 50).

fileId	string	required	The id of the file to query (from list_files / search_files - the same id get_file takes).
projectId	string	optional	Optional: which of the user's projects holds the file. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.
query	object	required	The constrained query object (grammar in the tool description): select?, where?, groupBy?, aggregates?, limit?.

saved	string	optional	SAVED-BY-NAME read: the exact short name the user gave a saved context. The service resolves the name to its real source and re-validates access live; if the access is gone it returns a calm "no longer available" note. Use this when the user refers to a context by a name they chose.
from	string	optional	The grantId of a share to READ (take it from the list this tool returns with no arguments). Omit to LIST the available shares.
handle	string	optional	NETWORK read: a UseMyContext project's public @handle (with or without the leading @) whose context you want to pull. Each @handle addresses ONE specific project, so the handle alone identifies what to read - there is no separate project argument. The owner must have opened that project to the network. You must already know the handle - there is no directory.
org	string	optional	ORGANISATION read: the id of an organisation you and the target are BOTH members of (on an active team plan). Use together with `member`. The service re-checks your shared membership and the team plan before serving anything.
member	string	optional	ORGANISATION read: the member id of the teammate whose live composite you want to read. Only used alongside `org`. You can read only a fellow member of an organisation you also belong to.
orgProject	string	optional	ORGANISATION read: which of that teammate's projects to read (defaults to their primary project). Only used alongside `org` + `member`.

UseMyContext

io.github.usemycontext/usemycontext MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

profile

list_files

search_files

get_file

ask_docs

query_table

suggest_update

shared_context

UseMyContext for Claude Code

What it looks like

Install

Disconnecting and revoking

What you get

One folder, one context

What it can and cannot do

Questions you probably have

Repo layout (for contributors)

Install

Remote endpoint