territory_brief — Kiltikonet (public) MCP Prompt
territory_brief
is one of 1 prompt on the
Kiltikonet (public)
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke territory_brief from your client
- Claude Code Kiltikonet (public) Prompt/territory_brief run in your project directory
- Claude Desktop Kiltikonet (public) Prompt/territory_brief ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Kiltikonet (public) Prompt/territory_brief ~/.cursor/mcp.json
- VS Code Kiltikonet (public) Prompt/territory_brief .vscode/mcp.json
- Zed Kiltikonet (public) Prompt/territory_brief ~/.config/zed/settings.json
- Windsurf Kiltikonet (public) Prompt/territory_brief ~/.codeium/windsurf/mcp_config.json
- Cline Kiltikonet (public) Prompt/territory_brief ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Kiltikonet (public) Prompt/territory_brief ~/.gemini/settings.json
- Grok Kiltikonet (public) Prompt/territory_brief .mcp.json (in your project root)
- ChatGPT Kiltikonet (public) Prompt/territory_brief Settings → Connectors → Advanced → Developer mode
- Claude.ai Kiltikonet (public) Prompt/territory_brief Settings → Connectors → Add custom connector
- LangChain Kiltikonet (public) Prompt/territory_brief pip install langchain-mcp-adapters
Kiltikonet (public) also offers 1 resource — 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 25 October 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.