kem_encapsulate — qeaas mcp MCP Tool
kem_encapsulate
(kem encapsulate) is one of 6 tools on the
qeaas mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call kem_encapsulate from your client
- Claude Code qeaas mcp kem_encapsulate run in your project directory
- Claude Desktop qeaas mcp kem_encapsulate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor qeaas mcp kem_encapsulate ~/.cursor/mcp.json
- VS Code qeaas mcp kem_encapsulate .vscode/mcp.json
- Zed qeaas mcp kem_encapsulate ~/.config/zed/settings.json
- Windsurf qeaas mcp kem_encapsulate ~/.codeium/windsurf/mcp_config.json
- Cline qeaas mcp kem_encapsulate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI qeaas mcp kem_encapsulate ~/.gemini/settings.json
- Grok qeaas mcp kem_encapsulate .mcp.json (in your project root)
- ChatGPT qeaas mcp kem_encapsulate Settings → Connectors → Advanced → Developer mode
- Claude.ai qeaas mcp kem_encapsulate Settings → Connectors → Add custom connector
- LangChain qeaas mcp kem_encapsulate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http qeaas-mcp https://api.qeaas.eu/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.