
Agentprofile
io.github.everyai-comPublished by GitHub account everyai-comv0.1.0Updated Oct 27, 2026
One profile — skills, credentials, and memory — synced to every agent tool via one MCP URL.
Overview
Remote MCP server that gives AI coding tools one shared profile of skills and memory, synced through a single URL.
- What you can do
- Retrieve the profile context, skills and stored facts for the connected agent
- List, read and add skills to the shared profile
- Store, recall and delete memories so facts persist across tools
- Sync the same profile across Claude Code, Cursor, Codex and other MCP clients
- Manage memories and skills from a web dashboard with real-time updates
- When to use it
- Useful when you work across several AI coding tools and want preferences, facts and skills to carry over instead of being re-pasted into each one. Also suits people who want a small, self-hostable memory layer rather than a full knowledge base.
- Requirements
- A remote Streamable HTTP endpoint; no local install required. Authentication is required: OAuth discovery or a bearer token in the Authorization header (the CLI can create one). The hosted instance can create an anonymous profile without signup. Self-hosting needs a Cloudflare account with Workers and R2.
Installation
In SourceWeft
- Open Agentprofile in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.everyai-com%2Fagentprofile/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"agentprofile": {
"type": "http",
"url": "https://agentprofile.everyai-com.workers.dev/mcp"
}
}
}README
agentprofile
[license] [MCP] [clients] [status]
Your agent's identity, everywhere. One profile — skills, credentials, and memory — synced to every agent tool through a single MCP URL. Open source, zero-knowledge, and self-hostable on your own Cloudflare account.
Every AI tool you use — Claude Code, Cursor, Codex — starts from zero: its own skills, its own pasted API keys, its own amnesia. agentprofile gives them one shared brain.
Live now: hosted at https://agentprofile.everyai-com.workers.dev · dashboard at
/app
Connect (any MCP client)
The server is a remote MCP server (Streamable HTTP) — no install needed, just one URL:
It supports two ways to authenticate:
- OAuth (recommended) — clients that support MCP OAuth discover it automatically from the URL and show a consent screen.
- Bearer token — run
npx @magicteams_ai/agentprofileto get a token, or hitPOST /profiles.
Claude Code
Or with a bearer token:
Cursor / other mcp.json clients
Codex CLI
Or, for a client that does OAuth discovery:
VS Code / Copilot
Or just run npx @magicteams_ai/agentprofile and it configures every client it finds.
60-second demo
That creates an anonymous profile (no signup) on the hosted instance, auto-detects your installed MCP clients, and writes their config. Restart your tools, then:
- In Claude Code: "Remember that I prefer pnpm over npm."
- In Cursor: "What package manager do I prefer?"
It recalls it. That's your profile, everywhere.
What's in this repo (Phase 1)
This is the Phase 1 implementation from the master plan: a working end-to-end skeleton that syncs skills and memory across tools over MCP. Credentials (zero-knowledge), OAuth, semantic recall, and the skill registry land in later phases — see Roadmap.
Web UI
/— landing page with the one-command install and the pitch./app— live dashboard. Paste your token (or hit "Create new") and watch skills and memory update in real time: when any agent callsremember, the fact appears instantly over a WebSocket. Add or delete memories and skills right from the page./setup-prompt— the "set up with your agent" prompt: paste it into Claude Code or Cursor and your own agent installs and verifies agentprofile for you.
How it works
- One Durable Object per user is the source of truth. It validates the profile's secret on every call and owns that profile's memory and skills.
- Bearer token =
ap_<profileId>.<secret>. TheprofileIdroutes to the DO; the DO verifies a SHA-256 hash of the secret. No central token table. - The MCP surface is 6 tools:
get_context,list_skills,get_skill,remember,recall,forget. Deliberately small — every description byte is paid on every client turn (pinned in tests).
Run it locally
In another terminal:
Run the tests and typecheck:
Deploy your own (self-host)
agentprofile self-hosts on your own Cloudflare account — the free Workers tier covers personal use.
Roadmap
- P1: MCP server + ProfileDO, 6 tools, memory + skills, instant-profile CLI, live dashboard. ✅
- P2: per-client grants + audit log with live enforcement + dashboard access panel ✅; MCP sessions (
Mcp-Session-Id) ✅; semantic recall via Workers AI embeddings (keyword fallback) ✅; pluggable memory providers (builtin default + Mem0 + Supermemory adapters,/memory-config) ✅; OAuth 2.0 + PKCE consent flow with discovery, dynamic registration, and consent screen ✅. - P3: zero-knowledge credentials (client-side E2E), JIT injection, approval flow.
- P4: one-click Deploy-to-Cloudflare, signed skill registry, format translators.
- P5: teams, SSO, hosted cloud.
See the full plan in docs/.
Contributing
Contributions are welcome under the DCO —
sign off commits with git commit -s. See SECURITY.md for
responsible disclosure.
License
Part of the everyai-com agent stack
Open-source infrastructure for local-first, governed AI agents:
- distillory — local-first memory engine that reasons at ingestion
- agent-ready — turn any app into an MCP server + API + CLI, safe by default
- primer — live business context injected into any agent
- plainsync — local-first Markdown workspace for humans + agents
- argus — cloud-native software verification with parallel browser testing
- mintly-alternative — self-hostable documentation layer for humans + AI agents
- talltrack — sales calls in, publishable content out
Built by Phanindra Reddy · magicteams.ai
Source: README.md at commit d1909ab
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts