search_transcript_passages — BuildFeed MCP Tool Read-only
search_transcript_passages
(search transcript passages) is one of 10 tools on the
BuildFeed
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_transcript_passages from your client
- Claude Code BuildFeed search_transcript_passages run in your project directory
- Claude Desktop BuildFeed search_transcript_passages ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BuildFeed search_transcript_passages ~/.cursor/mcp.json
- VS Code BuildFeed search_transcript_passages .vscode/mcp.json
- Zed BuildFeed search_transcript_passages ~/.config/zed/settings.json
- Windsurf BuildFeed search_transcript_passages ~/.codeium/windsurf/mcp_config.json
- Cline BuildFeed search_transcript_passages ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BuildFeed search_transcript_passages ~/.gemini/settings.json
- Grok BuildFeed search_transcript_passages .mcp.json (in your project root)
- ChatGPT BuildFeed search_transcript_passages Settings → Connectors → Advanced → Developer mode
- Claude.ai BuildFeed search_transcript_passages Settings → Connectors → Add custom connector
- LangChain BuildFeed search_transcript_passages pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http buildfeed https://buildfeed.tech/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.