positioning (en) — UkraineBorder — travel guidance and war-risk insurance MCP Resource
positioning (en)
is one of 6 resources on the
UkraineBorder — travel guidance and war-risk insurance
MCP server. Connect the server and your client can attach it as context.
by client
How to attach positioning (en) from your client
- Claude Code UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) run in your project directory
- Claude Desktop UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) ~/.cursor/mcp.json
- VS Code UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) .vscode/mcp.json
- Zed UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) ~/.config/zed/settings.json
- Windsurf UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) ~/.codeium/windsurf/mcp_config.json
- Cline UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) ~/.gemini/settings.json
- Grok UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) .mcp.json (in your project root)
- ChatGPT UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) Settings → Connectors → Advanced → Developer mode
- Claude.ai UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) Settings → Connectors → Add custom connector
- LangChain UkraineBorder — travel guidance and war-risk insurance Resource/positioning (en) pip install langchain-mcp-adapters
Other resources on this server
UkraineBorder — travel guidance and war-risk insurance also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, 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 resource's type and contents.