MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees).
Install Slm Profile
$ npx skills add qualixar/superlocalmemory --skill slm-profile -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qualixar/superlocalmemory slm-profile --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/slm-profile .claude/skills/slm-profile && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "slm-profile" agent skill from https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profile into .claude/skills/slm-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slm-profile", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profileType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add qualixar/superlocalmemory --skill slm-profile -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qualixar/superlocalmemory slm-profile --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugin/skills/slm-profile .agents/skills/slm-profile && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "slm-profile" agent skill from https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profile into .agents/skills/slm-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slm-profile", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add qualixar/superlocalmemory --skill slm-profile -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qualixar/superlocalmemory slm-profile --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugin/skills/slm-profile .cursor/skills/slm-profile && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "slm-profile" agent skill from https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profile into .cursor/skills/slm-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slm-profile", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/qualixar/superlocalmemory.git --path plugin/skills/slm-profile--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add qualixar/superlocalmemory --skill slm-profile -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qualixar/superlocalmemory slm-profile --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugin/skills/slm-profile .gemini/skills/slm-profile && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "slm-profile" agent skill from https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profile into .gemini/skills/slm-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slm-profile", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install qualixar/superlocalmemory slm-profileInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add qualixar/superlocalmemory --skill slm-profile -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugin/skills/slm-profile .github/skills/slm-profile && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "slm-profile" agent skill from https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profile into .github/skills/slm-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slm-profile", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add qualixar/superlocalmemory --skill slm-profile -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install qualixar/superlocalmemory slm-profile --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugin/skills/slm-profile .opencode/skills/slm-profile && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "slm-profile" agent skill from https://github.com/qualixar/superlocalmemory/tree/main/plugin/skills/slm-profile into .opencode/skills/slm-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slm-profile", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
slm-profile- GitHub stars
- 231
- Token cost
- ~1.8k tokens
- SKILL.md length
- 855 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees).
- Tasks that involve MCP servers
- SKILL.md covers Memory profiles, MCP tool sets, If a tool is missing and Related skills
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slm Profile is an agent skill from qualixar/superlocalmemory. Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switchprofile or slm profile switch to change the active memory profile, the profileid argument to read or write another profile for one call, and SLMMCPPROFILE to choose a tool set. Required when working across multiple projects, clients, or tenants.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Open-source governed, local-first memory control plane for AI agents and teams. arXiv:2608.08253. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve MCP servers
Example prompts
- “/slm-profile”
Requirements
- Pre-approved tools (allowed-tools): switch_profile, get_status, Bash
What it can do on your machine
Read from SKILL.md and the folder at commit 26f8c68. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
switch_profileget_statusBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Slm Profile loads about 1.8k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 855 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: switch_profile, get_status, Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from qualixar/superlocalmemory at commit 26f8c68, republished under its AGPL-3.0 licence (© qualixar). 855 words, ~1,830 tokens.
Download SKILL.mdSave it as
.claude/skills/slm-profile/SKILL.md (or your agent's skills folder).- name
- slm-profile
- description
- Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switch_profile or slm profile switch to change the active memory profile, the profile_id argument to read or write another profile for one call, and SLM_MCP_PROFILE to choose a tool set. Required when working across multiple projects, clients, or tenants.
- allowed-tools
- switch_profile, get_status, Bash
- when_to_use
- - "Switch to my work profile" - "What profile am I currently in?" - "Create a profile for this client" - "Read the work profile once without leaving this one"…
slm-profile — Memory Profiles and Tool Sets
Two different things are called "profile" in SuperLocalMemory. Keep them apart.
- A memory profile is a namespace inside one store. It has its own memories,
knowledge graph, learned patterns, retention settings and audit trail. A fresh
install has one, called
default. This is whatswitch_profile,slm profileand theprofile_idargument are about. - An MCP tool set (
SLM_MCP_PROFILE:core,code,full,power,mesh) decides which tools the server shows your host.switch_profiledoes not change it.
A memory profile organises memory. It is not a security boundary: any local
caller that can name a profile can read it, unless the user has turned on company
mode with roles. For memories that must be unreachable from another bot or user,
use a separate data directory (SLM_DATA_DIR) or company mode (slm-governance).
Memory profiles
slm profile list [--json]
slm profile create <name> [--json]
slm profile switch <name> [--json]
slm status --json # data.profile is the active profileCreating a profile is a CLI action; there is no MCP tool for it. Over MCP:
switch_profile(
profile_id: str, # the name of an existing profile
)switch_profile changes the active profile. The change is not private to
your session: it is written as the machine's active profile, so every later call
from every session on this machine, and the dashboard, now work in it until
someone switches again. An unknown name is refused (Profile '<name>' does not exist); nothing is created. In company mode it also needs a role on the target
profile. Only switch when the user asks to move; do not switch to peek at
something.
Reaching another profile for one call
Most tools take an optional profile_id: remember, recall, search,
fetch, list_recent, update_memory, delete_memory, session_init,
close_session, report_outcome, report_feedback, get_status,
get_memory_summary, the correction and memory-kind tools, and others. A
non-empty value serves that one call from that profile (which must already
exist) and never moves the active profile. An empty value means the active
profile. Prefer this to switching and switching back.
recall(query="rollout plan", profile_id="work", session_id="<sid>")
remember(content="...", tags="ops", profile_id="client-acme")forget and the mesh tools take no profile_id; they act on the active profile.
What a profile isolates
recallreturns only the profile's own memories, plus shared or global ones only when you opt in (seeslm-scope).rememberwrites to the profile you name or the active one.- The code graph is not partitioned by profile: it lives in
code_graph.dbin the data directory. - The
slm_cache_*key-value cache andslm_compressrecovery store are keyed by the calling agent, not by profile, so switching profiles does not give you a clean cache (seeslm-cache).
Separate stores
To keep two bots or two clients completely apart, give each its own
SLM_DATA_DIR in its MCP config. You can run several SLM MCP servers at once,
named differently (for example superlocalmemory-personal and
superlocalmemory-work), each pointed at its own directory.
Show full SKILL.md (419 more words)Show less
MCP tool sets
| Profile | Tools | What it is |
|---|---|---|
core | 18 tools — remember, recall, search, fetch, list_recent, update_memory, forget, session, optimize, corrections, summaries, switch_profile | Smallest set; the Grok Bot / Cursor plugin uses it |
code | 38 tools — core + portable Brain evidence, report_outcome/report_feedback, 6 code-graph tools, memory kinds, bounded loops | For coding agents that need the graph; no mesh, no get_status |
full | 56 tools — everyday memory, delete_memory, get_status, observe, saved views, learning tools, skills, optimize, kinds, loops, mesh | Same set as the no-profile default |
power | 68 tools — full + audit_trail, retention, compaction, consistency_check, behavioral and diagnostic tools | Governance and admin work |
mesh | 8 tools — mesh coordination only | Lightweight cross-session signalling |
A host that sets no profile gets the 56-tool full set (this is what the Claude
Code and Codex plugins do; the Antigravity plugin sets power). Two more
environment variables widen or narrow it: SLM_MCP_ALL_TOOLS=1 registers every
tool (103), and SLM_MCP_TOOLS=remember,recall,... registers exactly the names
listed. SLM_MCP_PROFILE=whole is also every tool. The code-graph tools beyond
the six in code (such as update_code_graph, list_graph_stats) and tools
such as core_memory and settle_session_outcomes exist only with
SLM_MCP_ALL_TOOLS=1, whole or an explicit SLM_MCP_TOOLS list. Tools whose
function is to manage the SLM computer are never available to a remote caller.
The tool set is read when the MCP server starts. To change it, set it in the host's MCP config and restart the host; asking the server at runtime does not work:
"env": {
"SLM_MCP_PROFILE": "code",
"SLM_AGENT_ID": "claude_code"
}slm connect <ide> --profile <name> writes that variable into a supported
host's config. Setting SLM_MCP_PROFILE to a name that does not exist stops
slm mcp with a message listing the valid names. Older count-suffixed names
such as code20, full38 and power50 still resolve, with a startup warning.
On an install that already has memories, do not set SLM_DATA_DIR in the MCP
config: it points the host at a different, empty store.
switch_profile is in core, code, full and power, and in the default
set. It is not in mesh.
If a tool is missing
Check the tool set first (slm status does not show it; look at the host's MCP
config for SLM_MCP_PROFILE). Mesh tools need full, power, mesh or the
default. Code-graph tools need code or SLM_MCP_ALL_TOOLS=1. Audit and
retention tools need power. report_outcome and report_feedback need
anything but core or mesh.
Related skills
slm-scope— opt-in fact sharing across profiles (personal/shared/global)slm-graph— code-graph tools and the tool set they needslm-mesh— mesh tools and the tool set they needslm-status— check the active profile nameslm-governance— roles and company mode
SuperLocalMemory v4.1.24 · Qualixar · AGPL-3.0-or-later
© qualixar, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugin/skills/slm-profile of qualixar/superlocalmemory.
Open the folder on GitHubat commit 26f8c68
Compare with similar skills
Slm Profile next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Slm Profile this skillqualixar/superlocalmemory | 231 | — | ~1.8k | Automated safety check: Notes | AGPL-3.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Warp GUI to Agent CLI Migration
warpdotdev/warp
Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.
More from qualixar/superlocalmemory
All 17 skills in this repoSuperlocalmemory
qualixar/superlocalmemory
AI agent memory with mathematical foundations. An agent skill from qualixar/superlocalmemory.
Slm Graph
qualixar/superlocalmemory
Index and query a codebase as a structural graph — build the code graph, trace blast radius of a change, find callers/callees/inheritors, semantic code search by meaning, assemble PR review context…
Slm Loop
qualixar/superlocalmemory
Gate-verified bounded loops with SuperLocalMemory as the durable ledger.
Slm Recall
qualixar/superlocalmemory
Search and retrieve facts, decisions, and past context from SuperLocalMemory.
Slm Remember
qualixar/superlocalmemory
Capture durable facts, decisions, constraints, and gotchas into SuperLocalMemory.
Slm Scope
qualixar/superlocalmemory
Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine).
Related
Works with
Categories
Questions about Slm Profile
What does Slm Profile do?
Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Slm Profile is an agent skill from qualixar/superlocalmemory. Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees).
When should I use Slm Profile?
Slm Profile fits situations like: tasks that involve MCP servers.
How do I install Slm Profile in Claude Code?
Run `npx skills add qualixar/superlocalmemory --skill slm-profile -a claude-code`. Or copy the skill folder (plugin/skills/slm-profile in qualixar/superlocalmemory) into .claude/skills/slm-profile in your project. Claude Code loads it when a task matches its description.
How do I install Slm Profile in Codex?
Run `npx skills add qualixar/superlocalmemory --skill slm-profile -a codex`. Or copy the skill folder (plugin/skills/slm-profile in qualixar/superlocalmemory) into .agents/skills/slm-profile in your project. Codex loads it when a task matches its description.
Can I use Slm Profile in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qualixar/superlocalmemory --skill slm-profile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slm-profile, .gemini/skills/slm-profile, .github/skills/slm-profile and .opencode/skills/slm-profile in your project.
What does Slm Profile need to run?
SKILL.md names no scripts, command-line tools or credentials: Slm Profile is instructions for the agent only. Its frontmatter pre-approves these tools: switch_profile, get_status, Bash.
Does Slm Profile access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Slm Profile safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Slm Profile use?
Slm Profile is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Slm Profile use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Slm Profile?
Skills that share tags, products or a category with Slm Profile: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slm Profile?
qualixar (a GitHub organization) maintains it in qualixar/superlocalmemory, which has 231 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.
Source: qualixar/superlocalmemory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.