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