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