claim_site_key — BorealHost MCP Prompt
claim_site_key
is one of 5 prompts on the
BorealHost
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke claim_site_key from your client
- Claude Code BorealHost Prompt/claim_site_key run in your project directory
- Claude Desktop BorealHost Prompt/claim_site_key ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BorealHost Prompt/claim_site_key ~/.cursor/mcp.json
- VS Code BorealHost Prompt/claim_site_key .vscode/mcp.json
- Zed BorealHost Prompt/claim_site_key ~/.config/zed/settings.json
- Windsurf BorealHost Prompt/claim_site_key ~/.codeium/windsurf/mcp_config.json
- Cline BorealHost Prompt/claim_site_key ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BorealHost Prompt/claim_site_key ~/.gemini/settings.json
- Grok BorealHost Prompt/claim_site_key .mcp.json (in your project root)
- ChatGPT BorealHost Prompt/claim_site_key Settings → Connectors → Advanced → Developer mode
- Claude.ai BorealHost Prompt/claim_site_key Settings → Connectors → Add custom connector
- LangChain BorealHost Prompt/claim_site_key pip install langchain-mcp-adapters
Other prompts on this server
BorealHost also offers 5 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.