getting-started — BondTerminal MCP Resource
getting-started
is one of 6 resources on the
BondTerminal
MCP server. Connect the server and your client can attach it as context.
by client
How to attach getting-started from your client
- Claude Code BondTerminal Resource/getting-started run in your project directory
- Claude Desktop BondTerminal Resource/getting-started ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BondTerminal Resource/getting-started ~/.cursor/mcp.json
- VS Code BondTerminal Resource/getting-started .vscode/mcp.json
- Zed BondTerminal Resource/getting-started ~/.config/zed/settings.json
- Windsurf BondTerminal Resource/getting-started ~/.codeium/windsurf/mcp_config.json
- Cline BondTerminal Resource/getting-started ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BondTerminal Resource/getting-started ~/.gemini/settings.json
- Grok BondTerminal Resource/getting-started .mcp.json (in your project root)
- ChatGPT BondTerminal Resource/getting-started Settings → Connectors → Advanced → Developer mode
- Claude.ai BondTerminal Resource/getting-started Settings → Connectors → Add custom connector
- LangChain BondTerminal Resource/getting-started pip install langchain-mcp-adapters
Other resources on this server
BondTerminal 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 11 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.