contacts-get_research — Saber MCP Tool
contacts-get_research
(contacts get research) is one of 76 tools on the
Saber
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call contacts-get_research from your client
- Claude Code Saber contacts-get_research run in your project directory
- Claude Desktop Saber contacts-get_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Saber contacts-get_research ~/.cursor/mcp.json
- VS Code Saber contacts-get_research .vscode/mcp.json
- Zed Saber contacts-get_research ~/.config/zed/settings.json
- Windsurf Saber contacts-get_research ~/.codeium/windsurf/mcp_config.json
- Cline Saber contacts-get_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Saber contacts-get_research ~/.gemini/settings.json
- Grok Saber contacts-get_research .mcp.json (in your project root)
- ChatGPT Saber contacts-get_research Settings → Connectors → Advanced → Developer mode
- Claude.ai Saber contacts-get_research Settings → Connectors → Add custom connector
- LangChain Saber contacts-get_research pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http saber https://mcp.saber.app/mcpOther tools on this server
- contacts-enrich_work_email_batch
- contacts-enrich_work_email_batch_get
- companies-enrich_custom
- companies-enrich_custom_batch
- contacts-enrich_custom
- companies-resolve-domain
- companies-enrich_firmographics
- companies-enrich_funding
- companies-enrich_mna
- companies-enrich_open_jobs
- companies-enrich_tech_stack
- contacts-enrich_work_email
- enrichment_types-list
- enrichment_runs-list
- enrichment_runs-get
- companies-list_summaries
- companies-generate_summary
- enrichment_templates-list
- enrichment_templates-create
- enrichment_templates-get
- enrichment_templates-update
- enrichment_templates-delete
- monitors-list
- monitors-create
- monitors-get
- monitors-update
- monitors-delete
- monitors-pause
- monitors-resume
- monitors-trigger
- monitors-list_signals
- monitors-list_actions
- monitors-create_action
- monitors-get_action
- monitors-update_action
- monitors-delete_action
- monitors-pause_action
- monitors-resume_action
- contacts-get_research_by_external_id
- contacts-create_research
- contacts-search
- contact_lists-list
- contact_lists-create
- contact_lists-get
- contact_lists-update
- contact_lists-delete
- contact_lists-get_contacts
- connectors-list
- credits-get_balance
- organisation-get
- organisation-update
- company_lists-import
- company_lists-count_preview
- company_lists-list
- company_lists-create
- company_lists-get
- company_lists-update
- company_lists-delete
- company_lists-get_companies
- company_lists-export
- company_lists-search
- scoring-profile-list
- scoring-profile-create
- scoring-profile-get
- scoring-profile-update
- scoring-profile-delete
- scoring-rule-list
- scoring-rule-upsert
- scoring-rule-delete
- scoring-assignment-list
- scoring-assignment-create
- scoring-assignment-bulk-create
- scoring-assignment-delete
- scoring-scores-get
- scoring-compute
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.