Saber

Server Details

The Saber MCP server has tools available for creating company and contact buying signals, retrieving signals, managing lists and managing Saber settings. Helps revenue teams build qualified lead lists and convert more.

Status: Healthy
Last Tested: 2026-03-20 22:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

55 tools

company_lists.count_previewInspect

Preview expected company count and credit cost

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

company_lists.createInspect

Create a company list

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

company_lists.deleteInspect

Delete a company list

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the company list to delete

company_lists.exportInspect

Export a company list as CSV

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the company list
`__requestBody`	No	Request body

company_lists.getInspect

Get a company list by ID

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the company list

company_lists.get_companiesInspect

Get companies in a list

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of companies to return (1–100, default 25)
`listId`	Yes	The unique identifier of the company list
`offset`	No	Number of companies to skip for pagination (default 0)

company_lists.importInspect

Import a company list from HubSpot

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

company_lists.listInspect

List all company lists

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of lists to return (1–100, default 20)
`offset`	No	Number of lists to skip for pagination (default 0)

company_lists.searchInspect

Search companies matching a filter

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

company_lists.updateInspect

Update a company list

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the company list to update
`__requestBody`	Yes	Request body

company_signals.createInspect

Create a company signal asynchronously — returns immediately with a pending status; poll the returned ID or receive the result via webhook

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

company_signals.create_batchInspect

Create multiple company signals in batch — combines domains and questions using a Cartesian product; use templates for batches over 100 signals

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

company_signals.getInspect

Get a company signal by ID — returns current status and AI-generated answer if completed

ParametersJSON Schema

Name	Required	Description	Default
`signalId`	Yes	The unique identifier of the signal (UUID format)

company_signals.listInspect

List company signals with optional filters for domain, company ID, date range, and status

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results per page
`domain`	No	Filter signals by company domain (e.g., "acme.com")
`offset`	No	Number of results to skip for pagination
`status`	No	Filter by signal status (can be specified multiple times for multiple statuses)
`toDate`	No	Filter signals completed on or before this date (RFC3339 format)
`fromDate`	No	Filter signals completed on or after this date (RFC3339 format)
`companyId`	No	Filter signals by company ID
`subscriptionId`	No	Filter signals by subscription ID (UUID of the signal subscription that triggered execution)

company_signals.subscription_logsInspect

List signal executions for a specific subscription

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results per page
`domain`	No	Filter signals by company domain
`offset`	No	Number of results to skip for pagination
`status`	No	Filter by signal status (can be specified multiple times)
`toDate`	No	Filter signals completed on or before this date (RFC3339 format)
`fromDate`	No	Filter signals completed on or after this date (RFC3339 format)
`companyId`	No	Filter signals by company ID
`subscriptionId`	Yes	The UUID of the signal subscription

connectors.listInspect

List connectors and their connection status

ParametersJSON Schema

Name	Required	Description	Default
No parameters

contact_lists.createInspect

Create a contact list — runs a Sales Navigator search and stores a snapshot of matching contacts

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

contact_lists.deleteInspect

Delete a contact list and all its stored contacts

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the contact list

contact_lists.getInspect

Get a contact list by ID — returns metadata and contact count

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the contact list

contact_lists.get_contactsInspect

Get contacts in a list — returns the stored snapshot, no new Sales Navigator call

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of contacts to return (1–100, default 25)
`listId`	Yes	The unique identifier of the contact list
`offset`	No	Number of contacts to skip for pagination (default 0)

contact_lists.listInspect

List all contact lists — paginated

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of lists to return (1–100, default 20)
`offset`	No	Number of lists to skip for pagination (default 0)

contact_lists.updateInspect

Rename a contact list

ParametersJSON Schema

Name	Required	Description	Default
`listId`	Yes	The unique identifier of the contact list
`__requestBody`	Yes	Request body

contacts.create_researchInspect

Start a contact research job — AI gathers insights from LinkedIn and other sources asynchronously; use contacts.get_research to poll for results

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

contacts.create_signalInspect

Create a contact signal asynchronously — returns immediately with a pending status; poll the returned ID or receive the result via webhook

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

contacts.get_researchInspect

Get contact research by ID — returns status and AI-generated insights if completed

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	The unique identifier of the contact research request

contacts.get_signalInspect

Get a contact signal by ID — returns current status and AI-generated answer if completed

ParametersJSON Schema

Name	Required	Description	Default
`signalId`	Yes	The unique identifier of the contact signal (UUID format)

contacts.list_signalsInspect

List contact signals with optional filters for LinkedIn profile URL and pagination

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results per page
`offset`	No	Number of results to skip for pagination
`contactProfileUrl`	No	Filter signals by contact profile URL (LinkedIn or other professional profile)

contacts.searchInspect

Search for contacts at a company via LinkedIn Sales Navigator — requires a LinkedIn Sales Navigator connection on the API key owner's account

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

createCompanySignalSyncInspect

Create a company signal and block until the result is ready — returns the answer in the same response (recommended over async)

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

createContactSignalSyncInspect

Create a contact signal and block until the result is ready — returns the answer in the same response (recommended over async)

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

credits.get_balanceInspect

Get remaining credits balance — returns how many API credits your organization has left in the current billing period

ParametersJSON Schema

Name	Required	Description	Default
No parameters

getContactResearchByExternalIDInspect

Get contact research using an external system's ID (e.g. a HubSpot contact ID) and source name

ParametersJSON Schema

Name	Required	Description	Default
`externalId`	Yes	The external identifier of the contact research request (e.g., HubSpot contact ID)
`externalSource`	Yes	The source system that provided the external ID (e.g., "hubspot")

organisation.getInspect

Get your organisation profile

ParametersJSON Schema

Name	Required	Description	Default
No parameters

organisation.updateInspect

Update your organisation profile

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

signal_subscriptions.createInspect

Create a signal subscription — schedules recurring signal execution for a template

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

signal_subscriptions.getInspect

Get a signal subscription by ID

ParametersJSON Schema

Name	Required	Description	Default
`subscriptionId`	Yes	The unique identifier of the subscription

signal_subscriptions.listInspect

List all signal subscriptions for your organization

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of subscriptions to return
`offset`	No	Number of subscriptions to skip for pagination

signal_subscriptions.startInspect

Start a signal subscription

ParametersJSON Schema

Name	Required	Description	Default
`subscriptionId`	Yes	The unique identifier of the subscription to start

signal_subscriptions.stopInspect

Stop a signal subscription

ParametersJSON Schema

Name	Required	Description	Default
`subscriptionId`	Yes	The unique identifier of the subscription to stop

signal_subscriptions.triggerInspect

Trigger an immediate run of a signal subscription

ParametersJSON Schema

Name	Required	Description	Default
`subscriptionId`	Yes	The unique identifier of the subscription to trigger

signal_subscriptions.updateInspect

Update a signal subscription

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body
`subscriptionId`	Yes	The unique identifier of the subscription to update

signal_summaries.generateInspect

Generate an AI summary consolidating insights from all completed company signals for a domain

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

signal_summaries.listInspect

List all AI-generated signal summaries for a domain, ordered by creation date (latest first)

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results per page
`domain`	Yes	Filter summaries by company domain (e.g., "acme.com")
`offset`	No	Number of results to skip for pagination

signal_templates.createInspect

Create a reusable signal template — templates define standard research questions that can be applied to many companies in batch

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body

signal_templates.deleteInspect

Soft-delete a signal template — marks it as deleted but preserves it for historical tracking

ParametersJSON Schema

Name	Required	Description	Default
`templateId`	Yes	The unique identifier of the template to delete

signal_templates.getInspect

Get a signal template by ID

ParametersJSON Schema

Name	Required	Description	Default
`templateId`	Yes	The unique identifier of the template

signal_templates.listInspect

List all signal templates for your organization

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of templates to return
`offset`	No	Number of templates to skip for pagination
`includeDeleted`	No	Include deleted templates in the response

signal_templates.updateInspect

Update a signal template — creates a new version while preserving the template ID; omitted fields retain their previous values

ParametersJSON Schema

Name	Required	Description	Default
`templateId`	Yes	The unique identifier of the template to update
`__requestBody`	Yes	Request body

subscription_actions.createInspect

Create a subscription action

ParametersJSON Schema

Name	Required	Description	Default
`__requestBody`	Yes	Request body
`subscriptionId`	Yes	The subscription to add the action to

subscription_actions.deleteInspect

Delete a subscription action

ParametersJSON Schema

Name	Required	Description	Default
`actionId`	Yes	The action ID to delete
`subscriptionId`	Yes	The subscription that owns the action

subscription_actions.getInspect

Get a subscription action by ID

ParametersJSON Schema

Name	Required	Description	Default
`actionId`	Yes	The action ID
`subscriptionId`	Yes	The subscription that owns the action

subscription_actions.listInspect

List all actions for a subscription

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of actions to return
`offset`	No	Number of actions to skip for pagination
`subscriptionId`	Yes	The subscription whose actions to list

subscription_actions.pauseInspect

Pause a subscription action

ParametersJSON Schema

Name	Required	Description	Default
`actionId`	Yes	The action ID to pause
`subscriptionId`	Yes	The subscription that owns the action

subscription_actions.unpauseInspect

Unpause a subscription action

ParametersJSON Schema

Name	Required	Description	Default
`actionId`	Yes	The action ID to unpause
`subscriptionId`	Yes	The subscription that owns the action

subscription_actions.updateInspect

Update a subscription action

ParametersJSON Schema

Name	Required	Description
`actionId`	Yes	The action ID to update
`__requestBody`	Yes	Request body
`subscriptionId`	Yes	The subscription that owns the action

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Server Details

Available Tools

Verify Ownership

Discussions

Your Connectors

Resources