Skip to content

AGENTS.md

Latest commit

 

History

History
73 lines (53 loc) · 3.42 KB

AGENTS.md

File metadata and controls

73 lines (53 loc) · 3.42 KB
Raw

AGENTS.md - UseMyContext plugin for Cursor

Machine-first notes for coding agents. Human docs: README.md.

What this is

UseMyContext (usemycontext.ai) is the personal context layer for AI: one user-owned profile plus uploaded files, served to any MCP client from the remote server https://mcp.usemycontext.ai/mcp (Streamable HTTP, OAuth 2.1). This repo is a Cursor plugin marketplace distributing the usemycontext plugin (plugins/usemycontext/).

When to use

Install this when the user wants persistent personal context across AI tools: Cursor answering with who they are, what a repo is to them, and what their documents say, without re-introducing themselves each session.

Install (Cursor)

Add the plugin from cursor.com/marketplace ("Add to Cursor") or with /add-plugin in the editor. Then open Cursor Settings, go to Tools and MCP Servers, find usemycontext, and let the HUMAN click Connect and complete the browser sign-in. OAuth requires the human; an agent cannot complete it alone. No token is written to any file.

Raw-server alternative (no plugin, no folder mapping) in ~/.cursor/mcp.json:

{ "mcpServers": { "usemycontext": { "url": "https://mcp.usemycontext.ai/mcp" } } }

Account required

A UseMyContext account at usemycontext.ai is required; the free tier is enough. If the user has no account, send them to https://usemycontext.ai first.

Demo account for testing

Try it in 30 seconds - no signup. Sign in as 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. Docs: https://usemycontext.ai/docs

Folder mapping (.umc)

A .umc file in a repo root maps that folder to one UseMyContext project. Every session started in the folder reads the mapped context. Format (see plugins/usemycontext/.umc.example):

projectId=p2
handle=@work

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 (required) scopes the reads; handle (optional) is a readable label. Both are shown in the web app on the project's page. No .umc means the folder reads the account's active profile. The /umc skill checks or changes a folder's mapping.

Boundary

  • The MCP tools are all read-only against the user's files (search and fetch are thin aliases of search_files and get_file, added for ChatGPT deep-research compatibility).
  • One tool, suggest_update, can write: it files a pending suggestion that the user reviews and approves in the web app. Nothing the AI does ever edits the profile or files directly.
  • WHEN to reach for suggest_update: when a conversation has surfaced something new and durable about the user and is wrapping up (the user says thanks, goodbye, or that's all, or the task completes), offer to save it before the context is lost. The server advertises this trigger in its own tool description, so it holds for any client; the plugin's always-on rule restates it.
  • Every access leaves a record in the user's audit trail.
  • Revoke any time: disconnect under Cursor Settings, Tools and MCP Servers, or the Connect page in the web app (server-enforced, immediate).
  • The plugin never uploads repo code or files; only the local .umc marker is read.