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