Vayora MCP tools for clients, contacts and deals
Search clients and read their records and contacts, get the desk's brief on how a client works, create a client, find decision makers at a company, look up a contact's email, and read and annotate the business development pipeline.
Written by the Vayora team. Updated 29 October 2026.
The tools
11 tools: 6 read and 5 write. A read tool works on a connection made read-only. A write tool needs the person to have ticked Allow changes when they connected.
search_clientsFree-text search across company name, industry and country.
Takes: query='', limit=25 (max 100)
Returns: Matching clients; an empty query returns the most recent.
Credits: None
get_clientA client's full record, including the contacts on file.
Takes: client_id
Returns: The company and its contacts.
Credits: None
get_client_briefThe desk's distilled intel on a client, for submission prep.
Takes: client_id
Returns: What they value, dealbreakers, how they run a process, who decides and what to watch, each with an evidence quote. Says so if no brief exists.
Credits: None
list_open_dealsOpen deals in the business development pipeline.
Takes: limit=25
Returns: Deals with stage (the stored id) and stage_label (the word to say).
Credits: None
search_dealsSearch deals by title and description, optionally by stage.
Takes: query='', stage=None, limit=25 (max 100)
Returns: Matching deals with stage and stage_label. Stage can be the recruiter's word, an older word or the stored id.
Credits: None
get_dealOne deal's full record.
Takes: deal_id
Returns: The deal with stage and stage_label.
Credits: None
create_clientAdd a client company, with duplicate detection.
Takes: name, website='', linkedin_url='', market='' (UK or US), do_not_contact=False
Returns: The client with created, a duplicate flag and warnings for anything that did not go through, such as making you its account manager.
Credits: None
add_client_notePin a note to a client's record.
Takes: client_id, content, is_pinned=False
Returns: The saved note, shown in the client's Notes tab.
Credits: None
add_deal_notePin a note to a deal's record.
Takes: deal_id, content, is_pinned=False
Returns: The saved note, shown in the deal's Notes tab.
Credits: None
find_contact_emailLook for a client contact's work email.
Takes: contact_id
Returns: A status of queued or skipped with the reason and credits remaining. The email lands on the contact within a minute or two.
Credits: 1 credit, charged only when an email is found
find_people_at_clientFind people who work at a client, leaving out contacts already on file.
Takes: client_id, titles=None, seniority=None, limit=10 (1 to 25)
Returns: Names, titles and LinkedIn addresses, with a total and the credits used. No emails or phones.
Credits: A quarter of a credit for each person returned
Clients and the do not contact label
create_client adds a company and will not create a duplicate. Before creating anything it compares the website domain, the LinkedIn company page and the name with endings such as Ltd, Inc, UK and Group ignored, so Acme UK Ltd and Acme are the same client. A match returns the existing record with duplicate true. The tool only creates: it cannot change or delete a client.
A client can be filed with a do not contact label. The label is visible and, on this connector, it is enforced where it matters: find_people_at_client and find_contact_email refuse a labelled client, and a client campaign that would email the client or its contacts will not start. Outreach to candidates for that client's roles is not affected, because the label means the client's own people.
Contacts, briefs and the deal pipeline
get_client returns the record with the contacts on file. get_client_brief returns the desk's distilled view of what a client values, their dealbreakers, how they run a process and who decides, with an evidence quote for every claim. Deals carry two fields, stage and stage_label: the stored id and the word to say to a person, such as Client meeting or Terms sent. search_deals accepts either, in any case.
The two contact tools queue lookups instead of returning details. find_contact_email costs 1 credit, charged only if an email is found. find_people_at_client costs a quarter of a credit for each person returned and gives names, titles and LinkedIn addresses without emails or phones, so the recruiter adds the ones they want as contacts in the app. The client needs a website or LinkedIn page on file for the search to run.
What to ask
These are the kind of messages a recruiter types into Claude or ChatGPT once Vayora is connected. The assistant chooses the tools itself.
- What does Harlow Group care about, and who decides there? Anything in the brief I should know before I submit?
- Which deals are at Terms sent, and when did each last move?
- Add Brightwater Logistics as a client, UK, with their website, and flag them do not contact.
- Who runs engineering at Harlow Group? Give me up to five names and tell me the cost first.
Common questions
- What does the do not contact label actually stop?
- On this connector it stops the lookups that reach a client's own people, the search for people at the company, and any client campaign that would email the client or its contacts. Outreach to candidates for that client's roles carries on, because the label is about the client's people.
- Will it find two copies of the same company?
- create_client checks the website domain, the LinkedIn company page and the name with endings such as Ltd, Inc, UK and Group removed, within your workspace only. A match is returned with duplicate true and nothing is created.
- Can it edit or delete a client or a deal?
- No. Clients are created and annotated, deals are read and annotated. Changing or deleting either is done in the app.
- Does find_people_at_client return email addresses?
- No, only names, titles and LinkedIn addresses. To get an email, the recruiter adds a person as a contact in the app and the assistant can then run find_contact_email for that contact.
Every tool acts as the person who connected it, inside their own workspace. The MCP overview covers connecting, the read and write split and limits. The developers page has the API and webhooks, integrations lists the rest of what Vayora connects to, and ATS or CRM for a recruitment agency explains why the records sit in one place. To try it on your own book, start a free trial.