border-result-view — Border MCP Resource
border-result-view
is one of 2 resources on the
Border
MCP server. Connect the server and your client can attach it as context.
by client
How to attach border-result-view from your client
- Claude Code Border Resource/border-result-view run in your project directory
- Claude Desktop Border Resource/border-result-view ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Border Resource/border-result-view ~/.cursor/mcp.json
- VS Code Border Resource/border-result-view .vscode/mcp.json
- Zed Border Resource/border-result-view ~/.config/zed/settings.json
- Windsurf Border Resource/border-result-view ~/.codeium/windsurf/mcp_config.json
- Cline Border Resource/border-result-view ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Border Resource/border-result-view ~/.gemini/settings.json
- Grok Border Resource/border-result-view .mcp.json (in your project root)
- ChatGPT Border Resource/border-result-view Settings → Connectors → Advanced → Developer mode
- Claude.ai Border Resource/border-result-view Settings → Connectors → Add custom connector
- LangChain Border Resource/border-result-view pip install langchain-mcp-adapters
Other resources on this server
Border also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 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.