OXO / MCP CONNECTOR

Ask for prospects.
Get outreach.

You already had the answer. Acting on it meant leaving the chat. The OXO MCP Connector lets an MCP-compatible assistant like Claude or ChatGPT read the outbound context in OXO and move approved work forward.

ASSISTANT / OXOCONNECTED
YOU

Find finance leaders at 200–1,000 person SaaS companies in Australia. Put the best 50 into a campaign.

OXO

230 companies resolved. 50 people match the active criteria.

  1. Market checked
  2. Contacts resolved
  3. Campaign draft ready
Action boundaryReview campaign →

ONE CONNECTOR / FOUR JOBS

Don't browse the system.
Operate it.

The connector is useful because the answer does not end as text. It can resolve the next piece of work inside the same outbound system.

01FIND

Resolve companies and people from the market already inside OXO.

02BUILD

Create a campaign and apply the right sequence and playbook.

03READ

Check campaign state, approvals, replies and performance.

04ACT

Move the work forward through the controls your team already uses.

AUTONOMY WITH A BOUNDARY

The assistant asks.
OXO applies the rules.

  1. 01 / CONNECTConnect an MCP-compatible assistant to OXO.
  2. 02 / REQUESTAsk for data or a supported outbound action in plain language.
  3. 03 / CONTROLOXO uses the campaign, sequence and approval controls already in the product.
  4. 04 / CONTINUEInspect the result, approve the boundary and keep moving.

THE WORK RECEIPT

Every answer should show
what will move.

An assistant can be fast without becoming opaque. OXO returns the request, the evidence it used, the proposed action and the point where approval is required.

01 / REQUESTWho did you ask for?

The market, buyer roles, exclusions and quantity stay visible beside the result.

02 / EVIDENCEWhy these records?

Matched criteria and available contact routes explain why each record entered the working set.

03 / PROPOSED ACTIONWhat happens next?

The campaign, channel and sequence are shown before the work begins to move.

04 / BOUNDARYWhere does OXO stop?

Drafts wait where your existing approval controls require a person to decide.

DRAFT / WAITING FOR REVIEW
01 / ASK FOR THE MARKET

Describe who you need. Get the working set.

Ask your MCP-compatible assistant for the companies or people you want. OXO resolves the request against the prospect workspace, so the answer can become the starting point for outreach.

Resolved by assistant
Companies resolved230
People matched50
AustraliaSaaS200–1,000 peopleFinance leaders
50 of 230 carried into the campaign draft.
SAMPLE WORKSPACE DATA / OXO PRODUCT VIEW
02 / TURN THE ANSWER INTO A MOTION

Build the sequence without rebuilding the context.

Create a campaign, choose the channels and carry the selected records into a controlled sequence. The connector shortens the path between deciding what to do and setting the work in motion.

Drafted by assistant
  1. Email · Introduction
    Wait 3 days
  2. Call · Intro call
    Wait 2 days
  3. LinkedIn · Connection noteadded
Approval stays with your team — nothing sends on its own.
SAMPLE WORKSPACE DATA / OXO PRODUCT VIEW
03 / RETURN TO THE CONVERSATION

Read replies. Inspect state. Decide what moves next.

Ask what is waiting, what replied and what needs a person. OXO returns the operating context behind the answer, while approvals and judgment stay where your team set them.

Summarised by assistant
Replies126
Positive48
Demo booked12
  • Positive
    Ana DuarteCFO · Meridian Cloud
    Demo booked
  • Neutral
    Marcus LeeVP Finance · Northwind
    Follow up
  • Positive
    Priya RamanHead of RevOps · Loop
    Owner assigned
126 replies read · 1 flagged for a person.
SAMPLE WORKSPACE DATA / OXO PRODUCT VIEW

LESS SWITCHING. SAME CONTROL.

Your outbound engine
is one message away.

Find the market. Build the motion. Read the reply. Keep judgment with your team.