agentsclimarketplace

Mcp tools

Skill komluk/scaffolding/skills/mcp-tools

MCP tool decision tree and MCP-first fallback strategy. TRIGGER when: choosing whether to use an MCP tool versus a built-in, or an MCP tool is available for a task. SKIP: semantic-memory MCP usage specifically (use semantic-memory-mcp).From its SKILL.md

Install
npx -y skills add komluk/scaffolding --skill mcp-tools

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.6 KB, as published. Nobody here has run it

MCP Tools Decision Tree

Priority Order

  1. Does an MCP tool exist for this operation? Use it first.
  2. Did the MCP tool fail (auth missing, plugin unavailable)? Fall back to built-in.
  3. No MCP tool matches? Use built-in tools (Bash, Grep, WebSearch, etc.).

MCP Plugin Quick Reference

PluginTransportKey ToolsAgents
context7stdiomcp__context7__resolve-library-id, mcp__context7__get-library-docsresearcher, developer
playwrightstdiomcp__playwright__browser_navigate, mcp__playwright__browser_screenshotdeveloper, debugger
eslintstdiomcp__eslint__*developer, reviewer
sonarqubedockermcp__sonarqube__*developer, reviewer
sequential-thinkingstdiomcp__sequential-thinking__*architect, debugger
postgres-mcpstdiomcp__postgres-mcp__*developer, optimizer
redis-mcpstdiomcp__redis-mcp__*developer, devops, debugger
dockerstdiomcp__docker__*devops
cronstdiomcp__cron__*devops
ssh-mcpstdiomcp__ssh-mcp__*devops
githubhttpmcp__github__*gitops, architect
google-sheetsstdiomcp__google-sheets__*researcher, tech-writer
slackssemcp__slack__*tech-writer
asanassemcp__asana__*architect
supabasehttpmcp__supabase__*optimizer
firebasestdiomcp__firebase__*devops, optimizer
memorystdio13 tools across search/store/notes/ingest/session tiers (see below)tiered — see Access Control

Semantic Memory MCP

  • Transport: stdio (Python, venv/bin/python -m mcp_servers.semantic_memory)
  • Source: MCP servers in your backend directory (internal, built on fastmcp)
  • Auth: DATABASE_URL (PostgreSQL connection string), SEMANTIC_MEMORY_ENABLED=true
  • Config: .mcp.json at project root

Tools (13 total)

ToolPurposeParameters
search_contextSearch ingested context chunks (Qdrant hybrid retrieval)query (required), corpus, top_k
semantic_searchSearch memories by similarityquery (required), project_id, agent_name, top_k, threshold
semantic_recallRecall relevant memories as markdowncontext (required), agent_name, project_id, top_k
semantic_storeStore a new memory with embeddingcontent (required), agent_name (required), project_id, conversation_id, task_id, tags, content_type
store_notePersist a note documentcorpus, relative_path, content (see notes-tier agents)
read_noteRead a note documentcorpus, relative_path
list_notesList note documentscorpus
trigger_ingestQueue ONE document (corpus + relative_path) for immediate re-indexing so a note just written via store_note becomes searchable in seconds instead of up to 15 minutes. Path-scoped only — cannot trigger a full backfill. Returns once queued; does not wait for indexing to finish (~3s to become searchable). Only useful to agents that also have store_note — otherwise you'd be re-indexing someone else's file.corpus (required), relative_path (required)
list_sessionsList memory sessions (catalog)—
get_sessionGet a session's detailssession_id
semantic_listList stored memories (catalog)project_id
semantic_deleteDelete a memorymemory_id (granted to no agent)
archive_sessionArchive a sessionsession_id (granted to no agent)

Access Control

TierToolsAgents
Write (search/recall/store)search_context, semantic_search, semantic_recall, semantic_storedeveloper, architect, debugger, analyst, researcher, reviewer, optimizer
Read-onlysearch_context, semantic_search, semantic_recalltech-writer, devops, gitops, mcp-builder, prompt-engineer
Notesstore_note, read_note, list_notesarchitect, researcher
Ingest triggertrigger_ingestarchitect, researcher — narrow grant, restricted to the two agents that also hold store_note; broader access would invite wasted LLM context-gen calls re-indexing files the caller didn't write
Session cataloglist_sessions, get_session, semantic_listcoordinator
Delete/archivesemantic_delete, archive_sessionnobody

corpus (top-level NFS share directory: homelab, platform, projects) and project_id (scaffold:<hash>, one per repo) are different axes — corpus scopes the notes/ingest tools above, project_id scopes the semantic_* (mem0) tools. Don't pass one where the other is expected.

For detailed usage guidance (when to search, when to store, quality gates), see the semantic-memory-mcp skill.

Fallback Strategy

OperationMCP Tool (Priority)Fallback
Library docs lookupcontext7WebSearch
UI verificationplaywrightManual browser check
Code qualitysonarqubepython3 devops/sonarqube.py via Bash
Lintingeslintnpx eslint via Bash
Database querypostgres-mcppsql via Bash
Cache inspectionredis-mcpredis-cli via Bash
Container opsdockerdocker via Bash
Git operationsgithubgh CLI via Bash
Memory searchmemoryFile-based agent-memory
Remote serverssh-mcpssh via Bash

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.