MCP App Store
by KeenEthics
Outreach icon

Outreach MCP Server for Claude and ChatGPT

By Outreach

Overview

Bring Outreach knowledge and actions into Claude so your teams can move faster, combine insights across systems, and complete advanced revenue tasks without switching tools. Outreach is an end-to-end AI Revenue Platform for all go-to-market teams. By embedding agentic AI across every revenue workflow, Outreach increases sales productivity, boosts pipeline, and gives leaders the visibility and predictability they need to grow revenue at scale.

How to connect

  1. Claude: Open the Outreach listing in the Claude connectors directory and choose Connect. Claude listing Outreach exposes 15 tools here.
  2. ChatGPT: Open the Outreach listing in the ChatGPT app directory and choose Connect. ChatGPT listing Outreach exposes 63 tools here.

Tools

account_answer_question

ChatGPT
Answers questions about an account by searching and analyzing account record, meeting transcription, and other related data in the time range if specified. Example questions include: - What specific challenges or pain points is the account experiencing? - What are the desired outcomes or business goals the account aims to achieve?

account_create

ChatGPT
Creates a new account in Outreach. The current user is automatically assigned as one of the account's assigned users. The current user is set as the owner if no owner is specified in the input. Returns the created account record including its id only. IMPORTANT: Every field value used to create the account MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. ALWAYS call input_fields_fetch with resource="Account" and action="Create" before calling this tool. input_fields_fetch returns the full list of available standard fields, their types, and any required custom fields with validation rules. This ensures you know exactly which fields are available and which are required before creating the account. Example: input: name: "Acme Corp" additional_fields: - field_name: "domain" value: "acme.com" - field_name: "companyType" value: "Enterprise" - field_name: "industry" value: "Technology" - field_name: "custom1" value: "NA"

account_delete

ChatGPT
Deletes an account in Outreach by its ID. Returns a confirmation message with the deleted account's ID. IMPORTANT: Always ask the user for explicit confirmation before invoking this tool. Do not proceed with deletion without the user's approval.

account_get_by_id

ChatGPT
Retrieve an account using its unique identifier and return the corresponding Account object which includes default fields: id, name, company_type, owner, touched_at, industry, default_connection Use the additional_fields param to include additional account fields in the response. For custom fields (e.g. "Current CRM") which are not already included in the additional_fields parameter description or default fields, first call the filter_fields_fetch tool with entity_type="account" to discover relevant custom fields, then pass that ID (ex. "custom8") in additional_fields. Never guess custom field IDs. Only use when you know the corresponding label. Note: This tool returns only summary information (id, name) for the owner. To get full details about the owner, use the user_get_by_id tool with the owner's id.

account_search_by_external_id

ChatGPT
Search for accounts using id of the associated object in external systems, such as Saleforce or Dynamics. The search will return a list of Accounts. The Account contains the same information returned by account_get_by_id tool.

account_update

ChatGPT
Updates an existing account in Outreach. Only the fields explicitly included in input are changed; fields omitted from input are left unchanged on the account. Returns the updated account (id, name, owner, assignedUsers). IMPORTANT: Every field value used to update the account MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. All fields defined on AccountUpdateInput can be set directly by name. For a custom field (customN), call input_fields_fetch with resource="Account" and action="Update" first to discover its label and validation rules. Example: id: 139 input: additional_fields: - field_name: "industry" value: "Technology"

calendar_events_fetch

ChatGPT
Retrieve a list of calendar events (meetings) based on optional filter criteria. A calendar event represents a scheduled meeting or appointment on a user's calendar. Use this tool to fetch scheduled meetings which have not yet occurred or to review past meetings regardless of whether they had transcripts or were processed by Kaia's meeting intelligence features. Use the kaia_meeting_fetch tool to retrieve contents about meetings which have already occurred (transcripts, etc). Use this tool to explore meetings from calendar metadata (e.g. scheduled date, source, cancellation status, etc). Notes: - Multiple filters are combined with AND logic. - Use limit to control how many results are returned. Response: - Each event includes the title, time range, associated prospect/account/opportunity, and attendees. - The 'count' field indicates the total number of matching events, which may exceed the limit. When count > limit, state both the total and the number shown, e.g., "Showing 10 of 247 total events." When count <= limit, state only the count, e.g., "Found 3 calendar events."

call_disposition_fetch

ChatGPT
Returns the list of call dispositions (call outcome options, e.g. "Connected", "No Answer", "Voicemail") configured for the organization. Use this tool when: - The user asks "what call dispositions do we have?" or "list all call dispositions" - You need to resolve a call disposition name to its ID - The user wants to know the available outcome categories for calls Response: - Each call disposition includes id, name, order, outcome, defaultForOutboundVoicemail, createdAt, and updatedAt fields. - The response 'count' field indicates the total number of call dispositions, which may exceed the number of records returned when a limit is applied.

call_purpose_fetch

ChatGPT
Returns the list of call purposes (the intent/reason categories for a call, e.g. "Discovery", "Demo", "Follow-up") configured for the organization. Use this tool when: - The user asks "what call purposes do we have?" or "list all call purposes" - You need to resolve a call purpose name to its ID Response: - Each call purpose includes id, name, order, createdAt, and updatedAt fields. - The response 'count' field indicates the total number of call purposes, which may exceed the number of records returned when a limit is applied.

current_org

ChatGPT
Returns the authenticated user's organization (single record): - id: the org's numeric ID. - shortname: short identifier of the org (string). - opportunityAssociationDefault: the org's default opportunity-association strategy — one of "manual", "noop", "recent_closed", "recent_closed_lost", "recent_closed_won", "recent_created", "recent_updated". Use this tool when: - The user asks "what's our default opportunity association?" or other org-configuration questions. - You need to know the server-side default for opportunityAssociation before calling task_create (the org default is applied when the parameter is omitted).

current_user

ChatGPT
Returns the user id and email of the caller

filter_fields_fetch

ChatGPT
Fetch fields for a specific entity type (ex. account) which can be used as: - filter attributes on that entity's search tool (ex. account_search, opportunity_search, prospect_search) through the additional_field_filters parameter. - additional output fields on that entity's search or get tools through the additional_fields parameter. Use this tool to retrieve up to 250 additional fields which can be used to retrieve the necessary data to answer user queries that can't be answered with built-in filters and args on existing entity search or get tools. ONLY Supported entity types: - prospect - account - opportunity Response format: - 'id' is the internal id used only for API calls. - 'label' is the human friendly name displayed in the UI that users will be familiar with. - 'validation_type' describes the data type (ex. numerical, inclusion, string, date). - 'validation_definition' describes accepted values for 'inclusion' and 'currency' validation_types. For 'inclusion' and 'currency' fields, the filter value must exactly match one of the entries in validation_definition. Example Response: { "entity_type": "account", "count": 2, "custom_fields": [ { "id": "amount", "label": "amount", "description": "The $ value of the opportunity in annual revenue.", "validation_type": "numerical", "validation_definition": null }, { "id": "custom3", "label": "Account Priority", "validation_type": "inclusion", "validation_definition": [ "Low", "Medium", "High" ] } ] }

filter_schema_fetch

ChatGPT
Fetch the complete filter schema for a specific entity type, including: 1. Available additional custom fields that can be used as filter attributes and output fields 2. Available additional output fields. 3. The allowed standard filter attributes and their operators, grouped by data type (string, number, date, id). Use this tool to discover: - What custom and standard fields exist for filtering and output selection. - What operators are valid for each standard filter attribute. - What validation types and allowed values apply to custom fields. ONLY Supported entity types: - prospect - account - opportunity - task - sequence_state - schedule - ruleset - call - template - custom_object Response contains three sections: - fields: Lists standard fields can be retrieved. - custom_fields: Lists custom_fields with id, label, validation_type, validation_definition. - filters: Groups standard filter attributes by data type with allowed operators and optional instruction for each group. HOW TO USE FILTERS Each filter object has three fields: - "attribute": field id from this response (e.g. "custom8", "engagedAt"). - "operator": comparison operator (must be valid for the attribute's data type). - "value": list of string values. Value rules: - For "is" operator: multiple values use OR logic (e.g. ["High", "Medium"]). - For "between" operator: exactly two values — [min, max] (e.g. ["1", "100"] or ["2025-01-01", "2025-06-30"]). - For all other value-taking operators: a single value in the list (e.g. ["1000000"]). - For no-value operators (isEmpty, isNotEmpty, and all relative-date operators like today, last7Days, etc.): provide an empty list []. Operator rules: - For "string": use "is" for exact matches, "contains" for partial matches, and "startswith" to match the beginning of a string. Determining allowed operators: - For STANDARD filter attributes: use the operators listed in the filters response for the attribute's type group. - For CUSTOM fields: use the validation_type from the fields response to determine allowed operators: - "string": is, isNot, startsWith, contains, notContains, isEmpty, isNotEmpty - "numerical" or "currency": is, isNot, between, gte, lte, isEmpty, isNotEmpty - "date" or "date_time": is, between, gte, lte, isEmpty, isNotEmpty, plus relative-date operators (today, last7Days, last30Days, etc.) - "boolean": is, isNot, isEmpty, isNotEmpty - "inclusion" or "multi_inclusion": is, isNot, isEmpty, isNotEmpty (values MUST exactly match entries from validation_definition, case-sensitive) If a filter group includes an "instruction" field, follow it for additional guidance on how to construct filter values for that type. HOW TO USE ADDITIONAL FIELDS Use field IDs from the fields or custom_fields response (e.g. "custom8", "engagedAt") as values in the additional_fields parameter on search/get tools. Only pick fields needed to answer the user's query. Rules: - Never guess field IDs. Always use this tool first to discover valid IDs. - Both custom_fields and standard_fields from the response can be used for filtering and additional output. HOW TO USE CUSTOM OBJECTS Custom objects are admin-defined data structures unique to the organization (e.g. Campaigns, Webinars), distinct from standard objects like Prospects and Accounts — and distinct from a standard object's custom fields, which are a different thing fetched with entity_type "account" / "prospect" / etc. With entity_type "custom_object" the response is a custom_objects list plus a custom_objects_count, instead of the three sections above, and a custom_objects_instruction you must follow.

input_fields_fetch

ChatGPT
Fetch the available input fields for a resource create/update action. Returns a ResourceInputSchema with three sections: - standard_fields: typed optional fields (e.g. companyType, industry, assignedTeams). - ref_types: definitions of non-scalar types referenced by standard_fields (e.g. TeamRelationship, UserRelationship — each with its 'id' field). - custom_fields: organization-specific custom fields with validation metadata. Supported resources: Account Supported actions: Create Response structure: resource (str): The resource type (e.g. 'Account'). action (str): The action type (e.g. 'Create'). standard_fields (list): Standard optional fields, each containing: - name: camelCase GQL field name (e.g. 'companyType', 'assignedTeams') - type: concise type string (e.g. 'string', 'int', 'float', 'TeamRelationship', 'list[UserRelationship]', 'list[string]') - required: whether the field is required for the action - description: description of the field ref_types (list): Non-scalar type definitions referenced by standard_fields. Each contains: - name: type name (e.g. 'TeamRelationship', 'UserRelationship') - description: description of the type - fields: list of fields in this type, each with name, type, required custom_fields (list): Custom fields with validation rules, each containing: - name: internal field identifier (e.g. 'custom1') - label: human-readable label (e.g. 'Region') - required: whether the field is required - description: description of the custom field - validation_type: validation kind ('numerical', 'inclusion', 'string', 'currency', 'date') - validation_definition: accepted values for 'inclusion' type, currency code for 'currency' type, etc. Example response: { "resource": "Account", "action": "Create", "standard_fields": [ {"name": "companyType", "type": "string", "required": false, "description": "Company type of the account"}, {"name": "assignedTeams", "type": "list[TeamRelationship]", "required": false, "description": "Teams assigned to the account"} ], "ref_types": [ {"name": "TeamRelationship", "description": "A relationship reference to a Team entity.", "fields": [{"name": "id", "type": "int", "required": true, "description": "ID of the related entity"}]}, {"name": "UserRelationship", "description": "A relationship reference to a User entity.", "fields": [{"name": "id", "type": "int", "required": true, "description": "ID of the related entity"}]} ], "custom_fields": [ {"name": "custom1", "label": "Region", "required": true, "description": "Region", "validation_type": "inclusion", "validation_definition": ["NA", "EMEA", "APAC"]} ] }

job_role_fetch

ChatGPT
Returns the list of job roles configured for the organization. Job roles classify an user's role within their company's buying process (e.g. "SDR", "Sales Manager", "AE", "CSM", "Customer Success Manager"). Use this tool when: - The user asks "what job roles do we have?" or "list all job roles" - You need to resolve a job role name to its ID Response shape: - count: the TOTAL number of matching job roles (server-side, not limited by limit). - job_roles: the list of job role records (up to limit items). When count > limit, state both the total and the number shown, e.g., "Showing 10 of 50 total job roles." When count <= limit, state only the count, e.g., "Found 3 job roles."

kaia_meeting_fetch

ChatGPT
Fetch call and meeting recording information (summaries and/or transcripts) for specific meetings by instance ID. Use this when you already know the meeting instance IDs. BATCHING RULE: - ALWAYS pass all meeting instance IDs in a single call as a list. - CORRECT: instance_id=["id1","id2","id3"] (one call) - WRONG: three separate calls with instance_id=["id1"], instance_id=["id2"], instance_id=["id3"] Do NOT use for searching by topic or keyword — use kaia_meeting_search instead. RETRIEVAL STRATEGY: - For high-level overviews, action items, or follow-up emails: include_summary=true is usually sufficient. - For exact quotes or verbatim discussion: include_transcript=true. - If summaries do not contain the needed information, immediately call again with include_transcript=true. Do NOT ask the user — retrieve automatically in the same turn.

kaia_scorecard_fetch

ChatGPT
Fetch a page of Kaia scorecards configured for the organization. Returns a list of Scorecard objects, each including: id: str name: str | None enabled: bool | None autoScoringEnabled: bool | None metadata: creator/lastEditor/publisher (only id and name are returned for each user), createdAtUtc, modifiedAtUtc, publishedAtUtc questions: list of scorecard questions, each with a type discriminator (ScorecardFreeTextQuestion, ScorecardYesNoQuestion, ScorecardRangeQuestion, ScorecardSingleOptionQuestion, or ScorecardMultiOptionQuestion), plus id, order, question, isDefault, state, metadata (creator/lastEditor/publisher, createdAtUtc, modifiedAtUtc, publishedAtUtc), aiInstructions, and (for option questions) options/intents, and (for range questions) rangeMin/rangeMax Note: This tool returns only summary information (id, name) for creator/lastEditor/publisher. To get full details about a user, use the user_get_by_id tool with the user's id. Note: This endpoint does not report a total count. Use offset/limit to page through results; fewer scorecards than limit in the response indicates the last page.

kaia_scorecard_get_by_id

ChatGPT
Retrieve a Kaia scorecard using its unique identifier and return the corresponding Scorecard object including: id: str name: str | None enabled: bool | None autoScoringEnabled: bool | None metadata: creator/lastEditor/publisher (only id and name are returned for each user), createdAtUtc, modifiedAtUtc, publishedAtUtc questions: list of scorecard questions, each with a type discriminator (ScorecardFreeTextQuestion, ScorecardYesNoQuestion, ScorecardRangeQuestion, ScorecardSingleOptionQuestion, or ScorecardMultiOptionQuestion), plus id, order, question, isDefault, state, metadata (creator/lastEditor/publisher, createdAtUtc, modifiedAtUtc, publishedAtUtc), aiInstructions, and (for option questions) options/intents, and (for range questions) rangeMin/rangeMax Note: This tool returns only summary information (id, name) for creator/lastEditor/publisher. To get full details about a user, use the user_get_by_id tool with the user's id.

opportunity_add_prospects

ChatGPT
Associates one or more prospects with an opportunity in Outreach. This is the ONLY way to add a prospect to an opportunity. Outreach's API rejects a prospects field on opportunity_create/ opportunity_update outright (it errors as a private relationship that cannot be written, regardless of value) -- never attempt that; always call this tool instead. This runs as an asynchronous bulk-action job, not an immediate write: it returns a Batch describing that job's id and state (e.g. 'queued', 'started', 'finished'), not the opportunity or prospect records themselves. Tell the user the association was submitted/ queued, using the returned state -- do not tell them the prospect has definitely been added unless state indicates the job finished. Example: input: opportunityId: 7 prospectIds: ["42"]

opportunity_answer_question

ChatGPT
Answers questions about an opportunity by searching and analyzing opportunity record, meeting transcription, and other related data in the time range if specified. Example questions include: - What business goals is the buyer aiming to achieve? - What specific challenges is the buyer trying to solve?

opportunity_create

ChatGPT
Creates a new opportunity record in Outreach. The current user is automatically assigned as the owner if no owner is specified in the input. Returns an opportunity record with only the id field populated; all other fields are not set. IMPORTANT: Every field value used to create the opportunity MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. ALWAYS call input_fields_fetch with resource="Opportunity" and action="Create" before calling this tool. input_fields_fetch returns the full list of available standard fields, their types, and any required custom fields with validation rules. This ensures you know exactly which fields are available and which are required before creating the opportunity. Example: input: name: "Q1 Enterprise Deal" closeDate: "2026-05-17T16:48:12.000Z" additional_fields: - field_name: "amount" value: 50000 - field_name: "opportunityStage" value: {"id": 3} - field_name: "custom1" value: "Inbound"

opportunity_delete

ChatGPT
Deletes an opportunity in Outreach by its ID. Returns a confirmation response with the deleted opportunity's ID. IMPORTANT: Always ask the user for explicit confirmation before invoking this tool. Do not proceed with deletion without the user's approval.

opportunity_get_by_id

ChatGPT
Retrieve a opportunity and associated sales methodology using its unique identifier and return the corresponding Opportunity object including: id: int name: str | None account: Account | None (only id and name are returned) amount: int | None close_date: str | None created_at: str | None health_score: float | None next_step: str | None last_contacted_at: str | None updated_at: str | None assigned_users: list[User] (only id and name are returned for each user) opportunity_stage: OpportunityStage | None owner: User | None (only id and name are returned) primary_prospect: Prospect | None (only id and name are returned) default_connection: DataConnection | None sales_methodology: SalesMethodology | None (only present when include_sales_methodology=True) fields: list[SalesMethodologyField] SalesMethodologyField contains the definition of a sales methodology field and the opportunity's value for that field, and includes: order: int | None label: str | None name: str | None label_short: str | None type: str | None definition: str | None value: str | None (the opportunity's value for this field) use type and definition if set to determine how to interpret the value field. For example, when type is "RELATIONSHIP", definition is "PROSPECT", and value is "1280273", it means the value is id of the prospect resource. To get more details about the resource, use the corresponding get_by_id tool with the id, or other appropriate tools. In this example, use prospect_get_by_id with id 1280273 to get more details about the prospect. Note: sales_methodology is only available from this tool, not from opportunity_search or other opportunity tools. This tool returns only summary information (id, name) for nested objects such as owner, assigned_users, and primary_prospect. The account field contains the parent account's id and name — use account.id (not the opportunity id) for account-scoped lookups. To get full details about the owner or an assigned user, use the user_get_by_id tool with the user's id. To get full details about the primary prospect, use the prospect_get_by_id tool with the prospect's id.

opportunity_search_by_external_id

ChatGPT
Search for opportunities using id of the associated object in external systems, such as Saleforce or Dynamics. The search will return a list of Opportunities. The Opportunity contains the same information returned by opportunity_get_by_id tool, except sales_methodology which is only available via opportunity_get_by_id.

opportunity_stage_fetch

ChatGPT
Returns a list of opportunity stages with optional filtering. Opportunity stages represent the different phases in a sales process (e.g., 'Discovery', 'Negotiation', 'Closed Won'). Supported filter attributes: - id - name - isClosed Examples: - filter:[] → returns all opportunity stages - filter:[{"attribute": "isClosed", "operator": "is", "value": "true"}] → only stages that are subtypes of 'closed' - filter:[{"attribute": "id", "operator": "is", "value": ["1", "2"]}] → only stages with id 1 or 2 - filter:[{"attribute": "name", "operator": "is", "value": ["Discovery"]}] → only stages with name that exactly matches 'Discovery' Notes: - Partial string matching is not supported for 'name'. - Multiple filters are combined with AND logic (all must match). Response: - Each stage includes id, name, isActive, isWon, and isClosed fields. - The response 'count' field indicates the total number of matching stages, which may exceed the number of records returned when a limit is applied.

opportunity_update

ChatGPT
Updates an existing opportunity in Outreach. Only the fields explicitly included in input are changed; fields omitted from input are left unchanged on the opportunity. Returns the updated opportunity (id, name, closeDate, owner). IMPORTANT: Every field value used to update the opportunity MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. All fields defined on OpportunityUpdateInput can be set directly by name. For a custom field (customN), call input_fields_fetch with resource="Opportunity" and action="Update" first to discover its label and validation rules. Example: id: 7 input: closeDate: "2026-09-30T00:00:00.000Z"

prospect_create

ChatGPT
Creates a new prospect in Outreach. The current user is automatically assigned as one of the prospect's assigned users. The current user is set as the owner if no owner is specified in the input. Returns the created prospect record including its id only. IMPORTANT: Every field value used to create the prospect MUST be explicitly provided by the user. NEVER infer, guess, or fabricate field values. Do NOT make up field names. If the user has not supplied a value for a field, do not include that field. At least one of first_name or last_name must be provided. ALWAYS call input_fields_fetch with resource="Prospect" and action="Create" before calling this tool. input_fields_fetch returns the full list of custom fields with validation rules. This ensures you know exactly which fields are available and which are required before creating the prospect. HOW TO BUILD THE INPUT — follow these steps in order: Step 1: Set first_name and/or last_name from the user's request. Step 2: Set owner and assigned_users if specified by the user. Step 3: Collect ALL remaining data the user provided (standard fields like title, company, emails, AND custom fields like custom1, custom2) and place them into additional_fields. Custom fields (custom1 through custom150) are always strings. Step 4: Check input_fields_fetch results for any field with required: true. If ANY required field is missing from custom_fields, STOP and ask the user for the value. Step 5: Verify additional_fields is NOT null and NOT empty [] if you collected any values in Steps 3-4. custom_fields handling: Any field whose name starts with "custom" (e.g. custom1, custom2, …, custom150) MUST be placed inside additional_fields — they are NOT top-level parameters. Each entry has a field_name (e.g. "custom1") and a value (always a string for custom fields). Example — user says "Create prospect Jane Smith, VP of Sales at Acme Corp, set custom1 to NA": input: first_name: "Jane" last_name: "Smith" additional_fields: - field_name: "title" value: "VP of Sales" - field_name: "company" value: "Acme Corp" - field_name: "custom1" value: "NA"

prospect_delete

ChatGPT
Deletes a prospect in Outreach by its ID. Returns a confirmation message with the deleted prospect's ID. IMPORTANT: Always ask the user for explicit confirmation before invoking this tool. Do not proceed with deletion without the user's approval.

prospect_get_by_id

ChatGPT
Retrieve a prospect using its unique identifier and return the corresponding Prospect object including: id: int name: str | None owner: User | None (only id and name are returned) account: Account | None (only id, name, company_type, touched_at, and industry are returned) assigned_users: list[User] (only id and name are returned for each user) campaign_name: str | None engaged_score: float | None engaged_at: str | None touched_at: str | None stage: Stage | None default_connection: DataConnection | None Note: This tool returns only summary information for nested objects. To get full details about the owner or an assigned user, use the user_get_by_id tool with the user's id. To get full details about the account, use the account_get_by_id tool with the account's id. To get multiple prospects by their IDs, use the prospect_search tool with the ids parameter.

prospect_search_by_external_id

ChatGPT
Search for prospects using id of the associated object in external systems, such as Saleforce or Dynamics. The search will return a list of Prospects. The Prospect contains the same information returned by prospect_get_by_id tool.

prospect_update

ChatGPT
Updates an existing prospect in Outreach. Only the fields explicitly included in input are changed; fields omitted from input are left unchanged on the prospect. Returns the updated prospect (id, name, owner, assignedUsers). IMPORTANT: Every field value used to update the prospect MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. All fields defined on ProspectUpdateInput can be set directly by name. For a custom field (customN), call input_fields_fetch with resource="Prospect" and action="Update" first to discover its label and validation rules. Example: id: 42 input: additional_fields: - field_name: "title" value: "VP of Sales"

sequence_add_prospects

ChatGPT
Adds prospects to a sequence in Outreach by creating a batch operation. Returns a BatchRecord containing the batch ID and status. After receiving the batch response, use the batch_get_by_id tool with the returned batch ID to check its progress and report the final state (total, failures, pending) to the user. Required inputs: - prospect_ids: list of prospect IDs to add to the sequence. - sequence_id: ID of the target sequence. Optional inputs allow controlling mailbox, starting template, opportunity association, batch confirmation, and scheduling. IMPORTANT: Prospect IDs and sequence ID must be explicitly provided by the user. NEVER guess or fabricate IDs.

sequence_create

ChatGPT
Creates a new sequence in Outreach. Only the following fields can be set on creation: name, description, salesMotion, owner, sequenceType, shareType, schedule, throttleMaxAddsPerDay, and ruleset. The current user is set as the owner if no owner is specified in the input. For any field the user does not supply a value for: if the field has a documented default value, that default is used; otherwise the field is excluded entirely (no value is fabricated). Returns the created sequence record including its id only. IMPORTANT: Every field value used to create the sequence MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field, unless the field has a documented default (see parameter descriptions below), in which case that default applies automatically when the field is omitted.

sequence_delete

ChatGPT
Deletes a sequence in Outreach by its ID. Returns a confirmation response with the deleted sequence's ID. IMPORTANT: Always ask the user for explicit confirmation before invoking this tool. Do not proceed with deletion without the user's approval.

sequence_disable

ChatGPT
Disables a sequence in Outreach by its ID. Use this for "disable", "deactivate", or "turn off" a sequence. Clears the sequence's enabled flag, then cascades that flip to everyone enrolled: each active or failed sequence state is moved to disabled, and its scheduled mailings and tasks are torn down (call tasks are kept). Prospects stay enrolled, but that scheduled work is deleted, not held — re-enabling reschedules from where each prospect stands rather than restoring it. The per-prospect cascade is batched, so on a large sequence it finishes shortly after this call returns. No-op if the sequence is already disabled. Fails if an enable of the same sequence is still in flight. Returns the updated Sequence (id, name, enabled). To turn a sequence back on, use sequence_enable.

sequence_enable

ChatGPT
Enables a sequence in Outreach by its ID. Use this for "enable", "activate", or "turn on" a sequence. Sets the sequence's enabled flag, then cascades that flip to everyone enrolled: each disabled sequence state is moved to active, so their steps resume being scheduled. The per-prospect cascade is batched, so on a large sequence it finishes shortly after this call returns. No-op if the sequence is already enabled. Fails if a disable of the same sequence is still in flight. Returns the updated Sequence (id, name, enabled). To turn a sequence off instead, use sequence_disable.

sequence_states_destroy

ChatGPT
Destroy (delete/remove) sequence states in bulk. Sequence states track a prospect's involvement in a specific outreach sequence. Destroying a sequence state removes the prospect from that sequence entirely. Use this tool when: - The user wants to remove prospects from a sequence - The user wants to bulk-delete sequence states by ID Accepts an input with sequence state IDs to destroy. Returns a Batch object representing the bulk operation. IMPORTANT: Always ask the user for explicit confirmation before invoking this tool. Do not proceed with destroy without the user's approval. After receiving the batch response, use the batch_get_by_id tool with the returned batch ID to check its progress and report the final state (total, failures, pending) to the user.

sequence_step_add

ChatGPT
Adds a NEW step to an EXISTING sequence in Outreach. The step is always appended as the last step of the sequence; its position cannot be chosen. Use it when the user asks to add, append, or create a step (an email, call, task, LinkedIn, or SMS touch) in a sequence. NEVER guess, infer, or fabricate a sequenceId, templateId, or any other id — look them up first. Templates can be attached to the new step in the same call via templates, or afterwards with sequence_template_add using the new step's id. Returns the affected sequence as {sequence: {id, name, sequenceSteps}}. The newly added step is the LAST element of sequenceSteps; use its id for follow-up calls such as sequence_template_add.

sequence_template_add

ChatGPT
Attaches an EXISTING template to an EXISTING step of a sequence in Outreach. This tool does NOT create the template and does NOT create the sequence step. Both must already exist; this only links them. Use it when the user asks to add, attach, use, or assign a template to a sequence step, or to add another template variant (for A/B testing) to a step that already has one. Takes the id of the sequence, the id of the step within that sequence, and the id of the template to attach. NEVER guess, infer, or fabricate a sequenceId, stepId, or templateId. Templated step types include automatic and manual email, LinkedIn connection requests, LinkedIn messages, and manual SMS. Call and task steps take a note rather than a template, so do not attach a template to those. Returns the affected sequence (id, name) as a confirmation only; the newly created sequence template is not part of the response.

sequence_update

ChatGPT
Updates an existing sequence in Outreach. Only the following fields can be updated: name, description, schedule, scheduleIntervalType, salesMotion, tags, transactional, owner, and shareType. Fields omitted from the input are left unchanged on the sequence. Returns the updated Sequence (id, name, owner, tags).

show_task_list

ChatGPT
Renders a read-only task list in the MCP Apps UI. Takes exactly the same input as task_search; see the task_search description for arguments and how to build filters. Use show_task_list only when the user wants to see their tasks displayed. Use task_search instead when you need the tasks as data, e.g. to summarize them, reason about them, or pass them to another tool; show_task_list does not return task data for further use. It runs the search itself, so do NOT call task_search alongside it just to render. Results are sorted by due date unless sort is given.

stage_fetch

ChatGPT
Returns the list of prospect lifecycle stages configured for the organization. Stages are org-level configuration labels that classify where a prospect sits in the outreach pipeline. They describe the prospect's overall disposition, NOT their enrollment in a specific sequence. Example stage names: - 'Not Started' - 'Not Started - Added to Sequence' - 'Attempting to Contact' - 'In Progress with Rep' - 'Closed - Unresponsive' - 'Closed - Not Interested - Unsubscribe' - 'Closed - Using Competitive Product' - 'Closed - Left Company' - 'Closed - Bad Timing' Use this tool when: - The user asks "what stages do we have?" or "list all prospect stages" - You need to resolve a stage name to its ID for filtering prospects by stage - The user wants to know the available disposition categories for prospects Do NOT use this tool to find which prospects are enrolled in a sequence or to check a prospect's progress through sequence steps — use sequence_state_search for that. Response: - Each stage includes id and name fields. - The response 'count' field indicates the total number of stages, which may exceed the number of records returned when a limit is applied.

task_create

ChatGPT
Creates a new task in Outreach. Returns the created task record including its id only. IMPORTANT: Every field value used to create the task MUST be explicitly provided by the user. NEVER infer, guess, or fabricate field values. Required fields: - taskPriority: Relationship to a TaskPriority entity (use task_priority_fetch to get available priorities). - taskTheme: Relationship to a TaskTheme entity. - subject: Relationship to the Prospect entity this task pertains to. - dueAt: Due date/time in ISO 8601 format in UTC (e.g. '2025-01-15T09:00:00Z'). - opportunityAssociation: Strategy for opportunity association (defaults to 'recent_closed'). The current user is automatically assigned as the owner if no owner is specified in the input. ALWAYS call task_priority_fetch and task_theme_search before calling this tool to get the list of available task priorities, the task themes and their IDs.

task_priority_fetch

ChatGPT
Returns the list of task priority lookup values configured for the organization (typically Urgent / High / Normal / Low). Each entry has an id and a name. Use this tool when: - The user asks "what task priorities do we have?" or "list task priority options". - You need to resolve a task priority name (e.g. "Urgent") to its ID for filtering tasks with task_search — the taskPriority filter attribute expects priority IDs, not names. Response: - count: total number of task priorities configured for the organization. The tool returns the first 30 of them, which is every priority for any realistic org; if count is larger than the list, the remainder is not retrievable through this tool. - taskPriorities: list of records, each with id and name.

task_update

ChatGPT
Updates an existing task in Outreach. Only the following fields can be updated: taskPriority, taskTheme, subject (the prospect the task is for), owner, dueAt, and note. Fields omitted from input are left unchanged on the task. IMPORTANT: Every field value used to update the task MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field.

team_get_by_id

ChatGPT
Retrieve a team using its unique identifier and return the corresponding Team object including: id: int created_at: str | None name: str | None users: list[User] (only id and name are returned for each user) Note: This tool returns only summary information (id, name) for users. To get full details about a user, use the user_get_by_id tool with the user's id.

template_create

ChatGPT
Creates a new template in Outreach. Returns only the id of the created template. Rules for filling in the input: - name (required): MUST come from the user. If the user has not given a name, ask for it before calling this tool. Never make one up, even when you draft the subject and body. - subject, bodyHtml: by default, take them from the user and use their wording verbatim. Draft them yourself ONLY when the user explicitly asks you to write the content, e.g. "create a template named Intro and draft the subject and body for a first email to a new prospect". That permission covers subject and bodyHtml only. When drafting, do not add merge-field variables unless the user asks for specific ones. If the user wants a subject or body but has neither supplied it nor asked you to draft it, ask for it. - bodyHtml should be valid HTML, e.g. "<p>Hi there,</p><p>Thanks for reaching out.</p>". Plain text is also accepted: when the user supplies plain text, pass their wording unchanged. - All other fields (owner, toRecipients, ccRecipients, bccRecipients, shareType, tags, locale, trackLinks, trackOpens, clonedFromId, containsCustomHtml, statsTarget, contentCategoryMemberships) MUST be explicitly provided by the user or resolved from their request via a lookup tool. NEVER infer, guess, or fabricate these values or any IDs; omit a field the user did not ask for. The current user is automatically assigned as the owner if no owner is specified in the input; the call fails if no owner is given and the current user cannot be determined. The template is always created unarchived. Use user_search to resolve an owner's name to a user id, and template_search to resolve the ids of existing templates for statsTarget or clonedFromId. Behavior: - If no owner is given and the current user cannot be determined, the call fails. - The template is always created unarchived.

user_get_by_id

ChatGPT
Retrieve an user using its unique identifier and return the corresponding User object including: id: int name: str | None first_name: str | None last_name: str | None email: str | None teams: list[Team] (only id and name are returned for each team) Note: This tool returns only summary information (id, name) for teams. To get full details about a team, use the team_get_by_id tool with the team's id. To get multiple users by their IDs, use the user_search tool with the ids parameter.

account_get_by_id

Claude

account_search_by_ext_id

Claude

account_search_by_name

Claude

fetch_kaia_meetings

Claude

opportunity_get_by_id

Claude

opportunity_search_by_ext_id

Claude

opportunity_search_by_name

Claude

prospect_get_by_id

Claude

prospect_search_by_ext_id

Claude

prospect_search_by_name

Claude

sequence_search_by_name

Claude

user_get_by_id

Claude

user_search_by_ext_id

Claude

user_search_by_nam

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/outreach"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/outreach)