[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYPVH5AFXBACE21BTCT55G":3,"skill-same:01M7AYPVH5AFXBACE21BTCT55G":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7AYPVH5AFXBACE21BTCT55G","mcp-server-patterns",null,"Add or troubleshoot MCP servers in Hermes Agent.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmcp-server-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mcp-server-patterns\ndescription: \"Add or troubleshoot MCP servers in Hermes Agent.\"\nversion: 1.0.0\nauthor: OraMesLita\nlicense: MIT\nmetadata:\n  hermes:\n    triggers:\n      - \"add mcp server\"\n      - \"mcp configuration\"\n      - \"filesystem mcp\"\n      - \"mcp not working\"\n      - \"mcp tools missing\"\n      - \"add searxng\"\n      - \"add brave search\"\n      - \"mcp server setup\"\n    related_skills: [hermes-agent]\n---\n\n# MCP Server Configuration Patterns\n\nPractical patterns for configuring MCP servers in Hermes Agent. Covers common setups, pitfalls, and optimization techniques.\n\n## Quick Reference\n\n### Filesystem MCP — Parent Directory Access\n\n**Key insight:** Specifying a parent directory grants access to ALL subdirectories automatically. No wildcards needed.\n\n```yaml\n# ❌ Verbose — listing every subdirectory\nfilesystem:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-filesystem'\n    - F:\\projects\\app1\n    - F:\\projects\\app2\n    - F:\\projects\\app3\n\n# ✅ Clean — parent directory covers all subdirs\nfilesystem:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-filesystem'\n    - F:\\projects          # ALL subdirs automatically accessible\n    - F:\\obsidian_note     # ALL Obsidian vaults\n```\n\n**Why this works:** The server treats specified directories as allowed roots. Any path under them is automatically accessible, including future subdirectories.\n\n### MCP SDK Installation\n\n**Prerequisite:** The `mcp` Python package must be installed for MCP support.\n\n```bash\n# Install MCP SDK\npip install mcp\n\n# Verify installation\npython -c \"import mcp; print('MCP SDK installed')\"\n```\n\n**Pitfall:** If you see \"MCP SDK not available -- skipping MCP tool discovery\", the package is missing. MCP support is silently disabled without it.\n\n### MCP Roots Protocol\n\nFor dynamic directory updates without server restart, use MCP Roots:\n\n```yaml\nfilesystem:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-filesystem'\n    # No directories specified — client provides via Roots protocol\n```\n\n**When to use:** When you need runtime directory updates via `roots\u002Flist_changed` notifications. Most users should stick with explicit directory args.\n\n## Common MCP Server Configurations\n\n### SearXNG — Privacy-respecting Web Search\n\n```yaml\nsearxng:\n  command: npx\n  args:\n    - -y\n    - mcp-searxng\n  env:\n    SEARXNG_URL: \"http:\u002F\u002Fyour-searxng-instance:8080\"\n  timeout: 30\n```\n\n**Why:** Replaces `ddgs` (often broken), private, no API key needed.\n\n### Brave Search — High-quality Web Search\n\n```yaml\nbrave-search:\n  command: npx\n  args:\n    - -y\n    - \"@brave\u002Fbrave-search-mcp-server\"\n  env:\n    BRAVE_API_KEY: \"your-brave-api-key\"  # Free at brave.com\u002Fsearch\u002Fapi\n  timeout: 30\n```\n\n### everyfile — Instant Local File Search via Everything\n\n`everyfile` does NOT ship a built-in MCP server module. You must write a bridge\nscript that wraps the `everyfile` Python API using the MCP SDK (`MCPServer` in\nMCP 2.x, `FastMCP` in 1.x).\n\n**Prerequisites:** Windows, Python ≥ 3.11, VoidTools Everything installed and\nrunning. Install: `pip install everyfile[mcp]` (or `pipx install everyfile[mcp]`).\n\n**Bridge script** (save as `everyfile_mcp_server.py`):\n\n```python\nfrom everyfile import Everything, EverythingError\nfrom mcp.server.mcpserver import MCPServer\n\nmcp = MCPServer(\"everyfile\")\n\n@mcp.tool()\ndef search_files(query: str, max_results: int = 50, sort: str = \"name\",\n                 descending: bool = False, match_case: bool = False,\n                 match_path: bool = False, regex: bool = False) -> str:\n    ev = Everything()\n    cursor = ev.search(query, sort=sort, descending=descending,\n                       limit=max_results, match_case=match_case,\n                       match_path=match_path, regex=regex)\n    results = [row.to_dict() for row in cursor]\n    return json.dumps({\"results\": results, \"count\": len(results),\n                       \"total\": cursor.total}, default=str, ensure_ascii=False)\n\nif __name__ == \"__main__\":\n    mcp.run()\n```\n\n**Config (Hermes + Claude Code):**\n\n```yaml\n# Hermes config.yaml\neveryfile:\n  command: \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fpipx\u002Fpipx\u002Fvenvs\u002Feveryfile\u002FScripts\u002Fpython.exe\"\n  args:\n    - \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fhermes\u002Feveryfile_mcp_server.py\"\n```\n\n```bash\n# Claude Code\nclaude mcp add -s user everyfile -- \\\n  \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fpipx\u002Fpipx\u002Fvenvs\u002Feveryfile\u002FScripts\u002Fpython.exe\" \\\n  \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fhermes\u002Feveryfile_mcp_server.py\"\n```\n\n**Why:** Sub-millisecond filename\u002Fpath\u002Fmetadata search across all NTFS drives\n(reads the MFT directly). Complements ripgrep — Everything for filenames, rg\nfor content. Also works as a standalone CLI (`ev` command) and Python API.\n\n**Pitfall — MCP 2.x API rename:** `FastMCP` was renamed to `MCPServer` in MCP\n2.x. If you see `ModuleNotFoundError: No module named 'mcp.server.fastmcp'`,\nyou're on MCP 2.x — import from `mcp.server.mcpserver` instead. The migration\nguide is at https:\u002F\u002Fpy.sdk.modelcontextprotocol.io\u002Fv2\u002Fmigration\u002F.\n\n**Pitfall — async functions in MCP 2.x:** Any `@mcp.tool()` that uses `await`\n(e.g. `await ctx.info(...)`) MUST be declared `async def`. A plain `def` with\n`await` inside produces `SyntaxError: 'await' outside async function`. If the\ntool doesn't need `await`, a plain `def` is fine.\n\n### Obsidian MCP — Direct Vault Manipulation\n\n```yaml\nobsidian:\n  command: npx\n  args:\n    - -y\n    - \"@fazer-ai\u002Fmcp-obsidian\"\n  env:\n    OBSIDIAN_API_KEY: \"your-obsidian-api-key\"  # Enable in Obsidian settings\n    OBSIDIAN_HOST: \"localhost\"\n    OBSIDIAN_PORT: \"27123\"\n  timeout: 30\n```\n\n### PostgreSQL — Database Access\n\n```yaml\npostgres:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-postgres'\n    - postgresql:\u002F\u002Fuser:pass@localhost:5432\u002Fdbname\n```\n\n### GitHub — Repository Management\n\n```yaml\ngithub:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-github'\n  env:\n    GITHUB_PERSONAL_ACCESS_TOKEN: \"ghp_xxxxxxxxxxxx\"\n```\n\n## Transport Types\n\n### Stdio Transport (command-based)\n\n```yaml\nserver_name:\n  command: \"npx\"             # Executable to run\n  args: [\"-y\", \"pkg-name\"]   # Command arguments\n  env:                       # Environment variables for subprocess\n    SOME_API_KEY: \"value\"\n  timeout: 120               # Per-tool-call timeout (seconds)\n  connect_timeout: 60        # Initial connection timeout (seconds)\n```\n\n### HTTP Transport (url-based)\n\n```yaml\nserver_name:\n  url: \"https:\u002F\u002Fmcp.example.com\u002Fmcp\"\n  headers:\n    Authorization: \"Bearer sk-...\"\n  timeout: 180\n  connect_timeout: 60\n```\n\n**Note:** A server config must have either `command` (stdio) or `url` (HTTP), not both.\n\n## Security Considerations\n\n### Environment Variable Filtering\n\nFor stdio servers, Hermes only passes safe baseline variables:\n- `PATH`, `HOME`, `USER`, `LANG`, `LC_ALL`, `TERM`, `SHELL`, `TMPDIR`\n- Any `XDG_*` variables\n\nAll other environment variables are excluded unless explicitly added via `env`. This prevents accidental credential leakage.\n\n```yaml\ngithub:\n  command: \"npx\"\n  args: [\"-y\", \"@modelcontextprotocol\u002Fserver-github\"]\n  env:\n    # Only this token is passed to the subprocess\n    GITHUB_PERSONAL_ACCESS_TOKEN: \"ghp_...\"\n```\n\n### Credential Stripping in Error Messages\n\nFailed MCP tool calls automatically redact credential patterns:\n- GitHub PATs (`ghp_...`)\n- OpenAI-style keys (`sk-...`)\n- Bearer tokens\n- Generic `token=`, `key=`, `API_KEY=`, `password=`, `secret=` patterns\n\n## Troubleshooting\n\n### \"MCP SDK not available -- skipping MCP tool discovery\"\n\n```bash\npip install mcp\n```\n\n### \"No MCP servers configured\"\n\nCheck `~\u002F.hermes\u002Fconfig.yaml` has `mcp_servers` key with at least one entry.\n\n### \"Failed to connect to MCP server 'X'\"\n\nCommon causes:\n- **Command not found:** Ensure `npx`, `uvx`, or the command is on PATH\n- **Package not found:** For npx servers, add `-y` to auto-install\n- **Timeout:** Increase `connect_timeout`\n- **Port conflict:** For HTTP servers, verify URL is reachable\n\n### Tools not appearing\n\n- Check server is under `mcp_servers` (not `mcp` or `servers`)\n- Verify YAML indentation\n- Tool names are prefixed: `mcp_{server}_{tool}`\n- Look at startup logs for connection messages\n\n### Connection keeps dropping\n\nClient retries up to 5 times with exponential backoff (1s, 2s, 4s, 8s, 16s, capped at 60s). If fundamentally unreachable, gives up after 5 attempts.\n\n## Pitfalls\n\n- **Don't list every subdirectory.** Specify parent directories instead — the server grants access to all subdirs automatically.\n- **Don't forget `-y` for npx servers.** Without it, npx may prompt for installation, which hangs in automated environments.\n- **Don't put secrets in `args`.** Use `env` for API keys and tokens. Args are visible in process listings.\n- **Don't use both `command` and `url`.** A server config must have one or the other, not both.\n- **Don't assume MCP tools are available.** Check `hermes mcp list` to verify server status and tool discovery.\n- **Don't skip the MCP SDK.** Without `pip install mcp`, MCP support is silently disabled.\n\n## Verification\n\nAfter adding MCP servers:\n\n```bash\n# Check server status\nhermes mcp list\n\n# Verify tools are discovered\nhermes tools | grep mcp_\n\n# Test a specific tool\nhermes chat -q \"List files in F:\\projects using the filesystem MCP\"\n```\n\n## Notes\n\n- MCP tools are called synchronously from the agent's perspective but run asynchronously on a dedicated background event loop\n- Server connections are persistent and shared across all conversations in the same agent process\n- Adding or removing servers requires restarting the agent (no hot-reload currently)\n- The native MCP client is independent of `mcporter` — you can use both simultaneously","# MCP Server Configuration Patterns\n\nPractical patterns for configuring MCP servers in Hermes Agent. Covers common setups, pitfalls, and optimization techniques.\n\n## Quick Reference\n\n### Filesystem MCP — Parent Directory Access\n\n**Key insight:** Specifying a parent directory grants access to ALL subdirectories automatically. No wildcards needed.\n\n```yaml\n# ❌ Verbose — listing every subdirectory\nfilesystem:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-filesystem'\n    - F:\\projects\\app1\n    - F:\\projects\\app2\n    - F:\\projects\\app3\n\n# ✅ Clean — parent directory covers all subdirs\nfilesystem:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-filesystem'\n    - F:\\projects          # ALL subdirs automatically accessible\n    - F:\\obsidian_note     # ALL Obsidian vaults\n```\n\n**Why this works:** The server treats specified directories as allowed roots. Any path under them is automatically accessible, including future subdirectories.\n\n### MCP SDK Installation\n\n**Prerequisite:** The `mcp` Python package must be installed for MCP support.\n\n```bash\n# Install MCP SDK\npip install mcp\n\n# Verify installation\npython -c \"import mcp; print('MCP SDK installed')\"\n```\n\n**Pitfall:** If you see \"MCP SDK not available -- skipping MCP tool discovery\", the package is missing. MCP support is silently disabled without it.\n\n### MCP Roots Protocol\n\nFor dynamic directory updates without server restart, use MCP Roots:\n\n```yaml\nfilesystem:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-filesystem'\n    # No directories specified — client provides via Roots protocol\n```\n\n**When to use:** When you need runtime directory updates via `roots\u002Flist_changed` notifications. Most users should stick with explicit directory args.\n\n## Common MCP Server Configurations\n\n### SearXNG — Privacy-respecting Web Search\n\n```yaml\nsearxng:\n  command: npx\n  args:\n    - -y\n    - mcp-searxng\n  env:\n    SEARXNG_URL: \"http:\u002F\u002Fyour-searxng-instance:8080\"\n  timeout: 30\n```\n\n**Why:** Replaces `ddgs` (often broken), private, no API key needed.\n\n### Brave Search — High-quality Web Search\n\n```yaml\nbrave-search:\n  command: npx\n  args:\n    - -y\n    - \"@brave\u002Fbrave-search-mcp-server\"\n  env:\n    BRAVE_API_KEY: \"your-brave-api-key\"  # Free at brave.com\u002Fsearch\u002Fapi\n  timeout: 30\n```\n\n### everyfile — Instant Local File Search via Everything\n\n`everyfile` does NOT ship a built-in MCP server module. You must write a bridge\nscript that wraps the `everyfile` Python API using the MCP SDK (`MCPServer` in\nMCP 2.x, `FastMCP` in 1.x).\n\n**Prerequisites:** Windows, Python ≥ 3.11, VoidTools Everything installed and\nrunning. Install: `pip install everyfile[mcp]` (or `pipx install everyfile[mcp]`).\n\n**Bridge script** (save as `everyfile_mcp_server.py`):\n\n```python\nfrom everyfile import Everything, EverythingError\nfrom mcp.server.mcpserver import MCPServer\n\nmcp = MCPServer(\"everyfile\")\n\n@mcp.tool()\ndef search_files(query: str, max_results: int = 50, sort: str = \"name\",\n                 descending: bool = False, match_case: bool = False,\n                 match_path: bool = False, regex: bool = False) -> str:\n    ev = Everything()\n    cursor = ev.search(query, sort=sort, descending=descending,\n                       limit=max_results, match_case=match_case,\n                       match_path=match_path, regex=regex)\n    results = [row.to_dict() for row in cursor]\n    return json.dumps({\"results\": results, \"count\": len(results),\n                       \"total\": cursor.total}, default=str, ensure_ascii=False)\n\nif __name__ == \"__main__\":\n    mcp.run()\n```\n\n**Config (Hermes + Claude Code):**\n\n```yaml\n# Hermes config.yaml\neveryfile:\n  command: \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fpipx\u002Fpipx\u002Fvenvs\u002Feveryfile\u002FScripts\u002Fpython.exe\"\n  args:\n    - \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fhermes\u002Feveryfile_mcp_server.py\"\n```\n\n```bash\n# Claude Code\nclaude mcp add -s user everyfile -- \\\n  \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fpipx\u002Fpipx\u002Fvenvs\u002Feveryfile\u002FScripts\u002Fpython.exe\" \\\n  \"C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002Fhermes\u002Feveryfile_mcp_server.py\"\n```\n\n**Why:** Sub-millisecond filename\u002Fpath\u002Fmetadata search across all NTFS drives\n(reads the MFT directly). Complements ripgrep — Everything for filenames, rg\nfor content. Also works as a standalone CLI (`ev` command) and Python API.\n\n**Pitfall — MCP 2.x API rename:** `FastMCP` was renamed to `MCPServer` in MCP\n2.x. If you see `ModuleNotFoundError: No module named 'mcp.server.fastmcp'`,\nyou're on MCP 2.x — import from `mcp.server.mcpserver` instead. The migration\nguide is at https:\u002F\u002Fpy.sdk.modelcontextprotocol.io\u002Fv2\u002Fmigration\u002F.\n\n**Pitfall — async functions in MCP 2.x:** Any `@mcp.tool()` that uses `await`\n(e.g. `await ctx.info(...)`) MUST be declared `async def`. A plain `def` with\n`await` inside produces `SyntaxError: 'await' outside async function`. If the\ntool doesn't need `await`, a plain `def` is fine.\n\n### Obsidian MCP — Direct Vault Manipulation\n\n```yaml\nobsidian:\n  command: npx\n  args:\n    - -y\n    - \"@fazer-ai\u002Fmcp-obsidian\"\n  env:\n    OBSIDIAN_API_KEY: \"your-obsidian-api-key\"  # Enable in Obsidian settings\n    OBSIDIAN_HOST: \"localhost\"\n    OBSIDIAN_PORT: \"27123\"\n  timeout: 30\n```\n\n### PostgreSQL — Database Access\n\n```yaml\npostgres:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-postgres'\n    - postgresql:\u002F\u002Fuser:pass@localhost:5432\u002Fdbname\n```\n\n### GitHub — Repository Management\n\n```yaml\ngithub:\n  command: npx\n  args:\n    - -y\n    - '@modelcontextprotocol\u002Fserver-github'\n  env:\n    GITHUB_PERSONAL_ACCESS_TOKEN: \"ghp_xxxxxxxxxxxx\"\n```\n\n## Transport Types\n\n### Stdio Transport (command-based)\n\n```yaml\nserver_name:\n  command: \"npx\"             # Executable to run\n  args: [\"-y\", \"pkg-name\"]   # Command arguments\n  env:                       # Environment variables for subprocess\n    SOME_API_KEY: \"value\"\n  timeout: 120               # Per-tool-call timeout (seconds)\n  connect_timeout: 60        # Initial connection timeout (seconds)\n```\n\n### HTTP Transport (url-based)\n\n```yaml\nserver_name:\n  url: \"https:\u002F\u002Fmcp.example.com\u002Fmcp\"\n  headers:\n    Authorization: \"Bearer sk-...\"\n  timeout: 180\n  connect_timeout: 60\n```\n\n**Note:** A server config must have either `command` (stdio) or `url` (HTTP), not both.\n\n## Security Considerations\n\n### Environment Variable Filtering\n\nFor stdio servers, Hermes only passes safe baseline variables:\n- `PATH`, `HOME`, `USER`, `LANG`, `LC_ALL`, `TERM`, `SHELL`, `TMPDIR`\n- Any `XDG_*` variables\n\nAll other environment variables are excluded unless explicitly added via `env`. This prevents accidental credential leakage.\n\n```yaml\ngithub:\n  command: \"npx\"\n  args: [\"-y\", \"@modelcontextprotocol\u002Fserver-github\"]\n  env:\n    # Only this token is passed to the subprocess\n    GITHUB_PERSONAL_ACCESS_TOKEN: \"ghp_...\"\n```\n\n### Credential Stripping in Error Messages\n\nFailed MCP tool calls automatically redact credential patterns:\n- GitHub PATs (`ghp_...`)\n- OpenAI-style keys (`sk-...`)\n- Bearer tokens\n- Generic `token=`, `key=`, `API_KEY=`, `password=`, `secret=` patterns\n\n## Troubleshooting\n\n### \"MCP SDK not available -- skipping MCP tool discovery\"\n\n```bash\npip install mcp\n```\n\n### \"No MCP servers configured\"\n\nCheck `~\u002F.hermes\u002Fconfig.yaml` has `mcp_servers` key with at least one entry.\n\n### \"Failed to connect to MCP server 'X'\"\n\nCommon causes:\n- **Command not found:** Ensure `npx`, `uvx`, or the command is on PATH\n- **Package not found:** For npx servers, add `-y` to auto-install\n- **Timeout:** Increase `connect_timeout`\n- **Port conflict:** For HTTP servers, verify URL is reachable\n\n### Tools not appearing\n\n- Check server is under `mcp_servers` (not `mcp` or `servers`)\n- Verify YAML indentation\n- Tool names are prefixed: `mcp_{server}_{tool}`\n- Look at startup logs for connection messages\n\n### Connection keeps dropping\n\nClient retries up to 5 times with exponential backoff (1s, 2s, 4s, 8s, 16s, capped at 60s). If fundamentally unreachable, gives up after 5 attempts.\n\n## Pitfalls\n\n- **Don't list every subdirectory.** Specify parent directories instead — the server grants access to all subdirs automatically.\n- **Don't forget `-y` for npx servers.** Without it, npx may prompt for installation, which hangs in automated environments.\n- **Don't put secrets in `args`.** Use `env` for API keys and tokens. Args are visible in process listings.\n- **Don't use both `command` and `url`.** A server config must have one or the other, not both.\n- **Don't assume MCP tools are available.** Check `hermes mcp list` to verify server status and tool discovery.\n- **Don't skip the MCP SDK.** Without `pip install mcp`, MCP support is silently disabled.\n\n## Verification\n\nAfter adding MCP servers:\n\n```bash\n# Check server status\nhermes mcp list\n\n# Verify tools are discovered\nhermes tools | grep mcp_\n\n# Test a specific tool\nhermes chat -q \"List files in F:\\projects using the filesystem MCP\"\n```\n\n## Notes\n\n- MCP tools are called synchronously from the agent's perspective but run asynchronously on a dedicated background event loop\n- Server connections are persistent and shared across all conversations in the same agent process\n- Adding or removing servers requires restarting the agent (no hot-reload currently)\n- The native MCP client is independent of `mcporter` — you can use both simultaneously",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"OraMesLita","1.0.0",{"hermes":27},{"triggers":28,"related_skills":37},[29,30,31,32,33,34,35,36],"add mcp server","mcp configuration","filesystem mcp","mcp not working","mcp tools missing","add searxng","add brave search","mcp server setup",[38],"hermes-agent","main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fhermes-main-profile\u002Fmcp-server-patterns",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add oat431\u002Fhermes_config_backup --skill mcp-server-patterns",{"tool":54,"command":55},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill mcp-server-patterns",{"tool":57,"command":58},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill mcp-server-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmcp-server-patterns\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fskill-backup-workflow.md","REFERENCE","参考文档",3724,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmcp-server-patterns\u002Freferences\u002Fskill-backup-workflow.md",[69,76,83,91,98,105],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]