get_brief_pool — TechFabric MCP Tool Read-only
get_brief_pool
(get brief pool) is one of 36 tools on the
TechFabric
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_brief_pool from your client
- Claude Code TechFabric get_brief_pool run in your project directory
- Claude Desktop TechFabric get_brief_pool ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TechFabric get_brief_pool ~/.cursor/mcp.json
- VS Code TechFabric get_brief_pool .vscode/mcp.json
- Zed TechFabric get_brief_pool ~/.config/zed/settings.json
- Windsurf TechFabric get_brief_pool ~/.codeium/windsurf/mcp_config.json
- Cline TechFabric get_brief_pool ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TechFabric get_brief_pool ~/.gemini/settings.json
- Grok TechFabric get_brief_pool .mcp.json (in your project root)
- ChatGPT TechFabric get_brief_pool Settings → Connectors → Advanced → Developer mode
- Claude.ai TechFabric get_brief_pool Settings → Connectors → Add custom connector
- LangChain TechFabric get_brief_pool pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http techfabric https://www.techfabric.com/mcpOther tools on this server
- search
- get_page
- list_posts
- get_services
- explore_post
- compare_case_studies
- assess_databricks_readiness
- quiz_me
- visualize
- get_brief
- lint_draft
- check_draft
- submit_draft
- update_draft
- list_drafts
- get_status
- review_before_publishing
- publish_draft
- preview_draft
- revise_post
- start_post
- check_outline
- propose_edits
- apply_edits
- ask_author
- social_post_kit
- lint_social
- reddit_post_kit
- post_performance
- suggest_links_and_topics
- preview_diagram
- propose_brief
- open_editor
- request_image_upload
- place_image
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.