메뉴
Configure and use Hermes Agent's built-in MCP client for stdio and HTTP MCP servers, including testing, troubleshooting, and TLS trust fixes for internal HTTPS endpoints.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/arm2arm/AstroAgentAssistant --skill hermes-native-mcp명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | hermes-native-mcp |
| description | Configure and use Hermes Agent's built-in MCP client for stdio and HTTP MCP servers, including testing, troubleshooting, and TLS trust fixes for internal HTTPS endpoints. |
| version | 1.0.0 |
| author | AstroAgent / AIP |
| license | MIT |
| metadata | {"hermes":{"tags":["mcp","hermes","infrastructure","tools","http","stdio"],"category":"infrastructure","related_skills":["docs-mcp-at-aip","mcporter-cli","hermes-api-server"]}} |
Use this skill when configuring Hermes Agent to connect to MCP servers directly so their tools appear natively in conversations.
Typical cases:
python3 - <<
import importlib.util
(, importlib.util.find_spec() is not None)
PY
-v npx ||
-v uvx ||
If the Python MCP SDK is missing:
pip install mcp
# or
uv pip install mcp
~/.hermes/config.yamlHTTP MCP server:
mcp_servers:
docs:
url: https://docs-mcp-server.kube.aip.de/mcp
stdio MCP server:
mcp_servers:
filesystem:
command: npx
args: ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
Valid per-server options include:
commandargsenvurlheaderstimeoutconnect_timeoutA server entry must use either command or url, not both.
hermes mcp list
hermes mcp test docs
In a fresh Hermes process, MCP tools appear with the naming pattern:
mcp_<server>_<tool>Example:
mcp_docs_search_docsmcp_docs_find_versionAfter a restart or fresh session, ask Hermes to use the MCP tools directly.
Example prompt:
Use the docs MCP server to find the best matching indexed version for dask.
If an internal MCP endpoint works with direct networking but Hermes reports certificate verification failures, prefer fixing trust instead of disabling TLS verification.
Symptoms:
CERTIFICATE_VERIFY_FAILEDunable to verify the first certificateReliable local pattern:
Example variables in ~/.hermes/.env:
SSL_CERT_FILE=/home/$USER/.hermes/certs/custom-ca-bundle.pem
REQUESTS_CA_BUNDLE=/home/$USER/.hermes/certs/custom-ca-bundle.pem
NODE_EXTRA_CA_CERTS=/home/$USER/.hermes/certs/custom-ca-bundle.pem
CURL_CA_BUNDLE=/home/$USER/.hermes/certs/custom-ca-bundle.pem
hermes mcp test docs
hermes chat -q "Use the docs MCP server to list three indexed libraries."
mcp_servers: is the correct config key, not mcp.servers:.mcp_<server>_*.hermes mcp test <name> connects successfully and lists tools.hermes chat session exposes the expected mcp_<server>_* tools.