UseMyContext.ai
Server Details
Personal context for AI, written by you and never scraped: your profile and files, any MCP client.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- usemycontext/usemycontext
- GitHub Stars
- 0
- Server Listing
- UseMyContext
- ChatGPT
- –
- Claude
- UseMyContext.ai
TDQS
Scored across 13 tools
The tools are mostly well-differentiated, with clear guidance on when to use ask_docs vs query_table and list_profiles vs profile. However, fetch/get_file and search/search_files are explicit aliases, so the same purpose is served by two tools each; while the descriptions explain the client-contract difference, this still creates ambiguity about which to call. Overall some overlap exists but descriptions help.
The naming is a mix of verb_noun forms (get_file, list_files, query_table, suggest_update) and bare nouns/verbs (account, info, profile, fetch, search). This mixed convention is still readable, but not consistently predictable.
At 13 tools, the set is well-scoped for a read-only personal-context and document access service. Even with the alias pairs, the count is appropriate and each tool covers a distinct functional area (account, search, retrieval, profiles, shared context, updates).
For a read-only service, the tool surface covers the main user needs: account/plan info, service information, file listing/search/retrieval, semantic and tabular search, profile reading, shared context, and suggesting context updates. There are no obvious missing operations within the stated read-only scope.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Stop copy-pasting client context into your AI. 48 connectable providers via MCP.
Person-owned AI memory: portable context for any MCP client.
Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.
shared AI-context layer for teams — persistent memory your agents search and update over MCP
Related MCP Servers
- AlicenseAqualityFmaintenanceProvides persistent personal context (identity, projects, decisions, knowledge) to MCP-compatible AI tools, eliminating the need to re-explain yourself across sessions.251 npm1MIT
- AlicenseAqualityCmaintenanceStores personal context as markdown files and exposes them via MCP for AI assistants to retrieve user preferences, skills, and background.61MIT
- AlicenseNot gradedqualityCmaintenanceAggregates your digital footprint (GitHub, blogs, resume) into a single AI-readable profile and exposes it via MCP tools so AI agents can query your context live.1MIT
- FlicenseNot gradedqualityAmaintenanceProvides a local-first, user-owned AI work identity layer that stores preferences, quality bars, lessons, decisions, and project context in inspectable JSON/Markdown files on your machine, so multiple MCP-compatible coding tools start from the same approved context. It enables reviewing, editing, overriding, and previewing exactly what any AI caller receives before anything is sent.-
Glama MCP Gateway
Add one secure layer between your agents and this server.