GateKeeperAI CRM
Server Details
Remote MCP server for GateKeeperAI, a CRM with an AI phone receptionist for service businesses. Lets ChatGPT, Claude and Cursor search leads, read call transcripts and notes, update pipeline stages and log activity for your business. OAuth 2.0 with read and write scopes.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 38 tools
Most tools map cleanly to a distinct resource and action, with descriptions that explicitly separate contacts from leads and deals from pipelines. There is some residual overlap between create_contact/create_lead, log_activity/log_outreach, and get_lead/list_lead_messages, but the descriptions generally resolve the boundaries.
The set is overwhelmingly consistent snake_case with verb_noun names such as create_contact, update_task, and move_deal_stage. The main blemish is the deal resource being called list_opportunities while the rest of the set uses deal terminology.
At 38 tools, the surface is well above the 3–15 well-scoped range and exceeds the 25+ threshold for being too large. The CRM domain is broad, but the set still feels like several feature areas were exposed without consolidation.
Contacts, pipelines, stages, tasks, communications, and Meta routing are well covered, but there are notable lifecycle gaps: leads have no update/delete, deals have no get/update, and tasks have no get-by-id. Core workflows are supported, but full CRM CRUD coverage is uneven.
Available Tools
38 toolscreate_contactCreate a contactAInspect
Add a person to the CRM who has not called, chatted or filled in a form. Needs at least one of name, email or phone. IF THE EMAIL OR PHONE ALREADY BELONGS TO A CONTACT, NO NEW CONTACT IS CREATED: the existing one is returned with created=false. Whenever created is false, any identifier the existing contact was missing is filled in from what you sent, and so is a first or last name whose stored value is null; a name they already have is never overwritten, and their lifecycle stage is never touched. created is the ONLY field that tells you whether a person was added. matchedOn names the identifier this tool matched on when it can attribute the match, and is null otherwise — it is a hint, never the answer to "did this already exist". Worked examples: a new person gives created=true, matchedOn=null. An email that already belongs to someone gives created=false, matchedOn=email. Never re-run this to force a second contact.
Inputs: email, phone, last_name, first_name, +1 more.
create_dealCreate a dealAInspect
Create a deal, optionally linked to a contact. It starts in the FIRST stage of the pipeline and move_deal_stage moves it on from there; you cannot pick a starting stage, because a stage only means anything relative to its own pipeline. By default the deal goes into the account default pipeline. Pass pipeline_id to put it in a different one: from THIS tool set that is the only way a non-default pipeline receives a deal, so a pipeline created by create_pipeline stays an empty board until you do. (A website form can also be configured to file its submissions into a chosen pipeline, which is outside these tools.) Get pipeline ids from list_pipeline_stages, whose rows carry pipeline_id, pipeline_name and pipeline_is_default. The result reports the pipeline_id the deal actually landed in.
Inputs: name (required), amount, contact_id, pipeline_id.
create_leadLog a leadAInspect
Record an enquiry that arrived off-platform: a walk-in, a referral, a card taken at an event. Needs at least one of name, email or phone. The source is always "manual" and cannot be set — do not use this to backfill a lead that really came from a call, a form or an ad, because source drives attribution and reporting. The matching contact is created or linked automatically IN ALMOST EVERY CASE, and the result tells you when it was not. contact_linked false means the lead IS saved but no contact was linked to it, so it is on nobody's timeline and is invisible to contact search. THERE IS NO TOOL THAT CAN ATTACH IT AFTERWARDS, so never tell the user it can be fixed. Do not retry create_lead either, that leaves a duplicate lead behind even when it succeeds. Report it plainly. To preserve the enquiry itself, call create_contact for the same person and then log_activity on that contact with what they wanted: that puts the enquiry on their timeline, which the orphaned lead never will. create_contact alone does not rescue this lead. No new-lead alert is sent. The message you send is recorded as your team's internal note about this person, never as something they wrote: the AI reply draft is told not to quote it, and get_lead, list_leads and get_contact all return it with its authorship attached. It is still your own note, so write it for your team and assume a colleague will read it on the lead's record.
Inputs: name, email, phone, message.
create_pipelineCreate a pipelineAInspect
Create a deal pipeline. To set one up the way the business actually works, pass stages: the OPEN stages in left-to-right order (1 to 15, e.g. ["Inquiry", "Consult booked", "Proposal sent"]), and optionally won_stage_name and lost_stage_name (default "Won" and "Lost", e.g. "Retained" and "Not hired"). The won and lost stages are always added at the end and drive lead outcomes and win reporting. Without stages it is seeded with the standard New, Qualified, Proposal, Won, Lost. Every stage name must be different, ignoring case. If the account has no default pipeline yet, this one becomes the default. Most accounts need only one pipeline: to change an existing one, use rename_pipeline_stage, create_pipeline_stage, delete_pipeline_stage and reorder_pipeline_stages instead of making a second. IF A PIPELINE WITH THAT NAME ALREADY EXISTS, ignoring case, NOTHING IS CREATED OR CHANGED: the existing one is returned with created=false, and created is the ONLY field that tells you which happened. Do not work around it by adding a number to the name. A new pipeline starts with no deals; pass its pipeline_id to create_deal, or make it the default with set_default_pipeline so new leads land in it.
Inputs: name (required), stages, won_stage_name, lost_stage_name.
create_pipeline_stageAdd a pipeline stageAInspect
Add a stage to a pipeline. It is inserted before the Won and Lost stages so the pipeline still reads in order. Probability is a FRACTION between 0 and 1 (0.6 means 60 percent), matching the existing stages. Get pipeline_id from list_pipeline_stages, whose rows also carry pipeline_name and pipeline_is_default so you can tell one pipeline from another — to add a step to the pipeline new deals go into, pick the pipeline_id whose pipeline_is_default is true. An account with no pipeline yet has no stages to list and no pipeline_id to pass here: call create_pipeline to make one, or create_deal, which creates the default pipeline as a side effect. IF A STAGE WITH THAT NAME ALREADY EXISTS IN THAT PIPELINE, ignoring case, NO NEW ONE IS CREATED: the existing one is returned with created=false. Two columns with one heading cannot be told apart on the board. To change an existing stage use rename_pipeline_stage, delete_pipeline_stage or reorder_pipeline_stages.
Inputs: name (required), pipeline_id (required), probability.
create_taskCreate a taskAInspect
Create a task, optionally linked to a contact and with a due date. If this account has a connected Google Tasks calendar, a dated task also appears there.
Inputs: title (required), due_at, contact_id.
delete_contactDelete a contactADestructiveInspect
Permanently delete a contact along with its tasks and the notes members wrote. System-generated history (calls, emails, receipts) is kept as the record but unlinked from any contact timeline. The result reports historyKept: system history kept unlinked. Deals are kept, so revenue history survives. This permanently deletes data and cannot be undone. Call without confirm to see what would be removed.
Inputs: contact_id (required), confirm.
delete_dealDelete a dealADestructiveInspect
Permanently remove one deal (a card on the pipeline board). This permanently deletes data and cannot be undone. Only the deal goes: the lead it came from, the linked contact and their timeline are kept. Use it for a duplicate or junk card. If the deal simply did not close, move_deal_stage into a Lost stage instead, which keeps the record. Get deal ids from list_opportunities. Call without confirm to see what would be removed.
Inputs: opportunity_id (required), confirm.
delete_pipelineDelete a pipelineADestructiveInspect
Delete a pipeline and its stages. Only allowed when nothing would be lost: it is not the default (make another one the default first), it has no deals, no automation rule moves deals into it, and no website form files deals into it. Each refusal says which of these to resolve. This permanently deletes data and cannot be undone. Call without confirm first to see what would be deleted.
Inputs: pipeline_id (required), confirm.
delete_pipeline_stageDelete a pipeline stageADestructiveInspect
Delete an open stage from a pipeline. Won and Lost cannot be deleted, and the last open stage of a pipeline cannot be deleted. If the stage has deals in it, move_to_stage_id is required and must be another stage of the SAME pipeline; every deal moves there first. Moving them does not trigger stage automations. Refused while an automation rule targets the stage. This permanently deletes data and cannot be undone. Call without confirm to see how many deals would move.
Inputs: stage_id (required), confirm, move_to_stage_id.
delete_taskDelete a taskADestructiveInspect
Permanently delete a task and its calendar event. This permanently deletes data and cannot be undone. To simply mark it finished, use set_task_status instead, which keeps the record. Call without confirm to see what would be removed.
Inputs: task_id (required), confirm.
get_call_transcriptGet a call transcriptARead-onlyInspect
Fetch one call with its spoken transcript and any message the agent took during it. transcript is the conversation itself; messages is the separate intake or voicemail the agent saved, which many calls do not have. Long text is clipped and marked.
Inputs: call_id (required).
get_contactGet one contactARead-onlyInspect
Fetch a single contact with its recent activity timeline (calls, emails, notes, outreach). The timeline is capped and says so when it is truncated. A timeline row is NOT necessarily something the contact said. Rows derived from a lead carry body_author saying who wrote the body: a manually logged lead is your own team's internal note, a web chat is your assistant's summary, a call is your voice agent's summary. Every row reads direction=inbound regardless. Never quote a body back to the contact, and never write "you said" or "you mentioned" about one, unless body_author says the contact wrote it. Each row also carries latest_status: the delivery state (e.g. sent, delivered, bounced). A failure always outranks success, and engagement such as opened or clicked appears only in receipts, never in latest_status. When any exist, each row also carries receipts: dated status events as "status@time", oldest first, where "status~@time" means the time is approximate. Times are the provider's own time when it gave one, otherwise when we received the event. If a row has more than 20 receipts only the first 5 and last 15 are listed and receipts_omitted says how many were dropped. receipts_unavailable (top level) means receipts could not be read; no receipts are shown in that case.
Inputs: contact_id (required), activity_limit.
get_leadGet one leadARead-onlyInspect
Fetch a single lead with its linked contact and, when the lead came from a phone call, that call, the spoken transcript, and any message the agent took. Whenever a lead has a message, the record also carries message_author saying WHO WROTE IT. That field is not decoration: a manually logged lead's message is your own team's private note about the person, a web chat's message is the chat assistant's summary, and a visibility checker's message is a generated scan result. Only when message_author is "the lead" are those their own words. Never quote a message back to the lead, and never write "you said" or "you mentioned" about one, unless message_author says the lead wrote it.
Inputs: lead_id (required).
list_callsList callsBRead-onlyInspect
List phone calls handled for this account, most recent first.
Inputs: limit, since.
list_contactsList contactsBRead-onlyInspect
List contacts for this account, most recently active first.
Inputs: limit, lifecycle_stage.
list_lead_messagesList messages sent to a leadARead-onlyInspect
The emails and texts already exchanged with one lead, newest first, including whether each was delivered. Read this before composing a message so you do not repeat or contradict something they already received.
Inputs: lead_id (required), limit.
list_leadsList leadsARead-onlyInspect
List leads for this account, newest first. Filter by source, status, or a created-after timestamp. Returns lead records as data. Whenever a lead has a message, the record also carries message_author saying WHO WROTE IT. That field is not decoration: a manually logged lead's message is your own team's private note about the person, a web chat's message is the chat assistant's summary, and a visibility checker's message is a generated scan result. Only when message_author is "the lead" are those their own words. Never quote a message back to the lead, and never write "you said" or "you mentioned" about one, unless message_author says the lead wrote it.
Inputs: limit, since, source, status.
list_mailboxesList sending mailboxesARead-onlyInspect
The verified mailboxes this account can send email from. Use one of these ids as mailbox_id for send_lead_email. Unverified mailboxes are listed but cannot send.
Inputs: no named parameters.
list_meta_lead_routesList Meta lead routingARead-onlyInspect
Show where Meta (Facebook and Instagram) lead-ad leads go. Returns the Pages this account has connected, each with pipeline_id (null = the account default pipeline), and every lead form that has delivered at least one lead, with its own pipeline_id override (null = same as its Page), an optional label, and its lead count. A lead goes to its form's pipeline if set, else its Page's, else the default. Forms only appear after their first lead (Meta does not let this app list a Page's forms), so a brand-new form cannot be routed yet. Pipeline names and ids come from list_pipeline_stages.
Inputs: no named parameters.
list_opportunitiesList opportunitiesARead-onlyInspect
List deals for this account with their pipeline stage name, most recently updated first.
Inputs: limit, status.
list_pipeline_stagesList pipeline stagesARead-onlyInspect
List this account pipeline stages in board order. Each row carries the stage id plus the pipeline it belongs to: pipeline_id, pipeline_name, and pipeline_is_default. Call this before move_deal_stage and before create_pipeline_stage — both need an id from here. An account can have more than one pipeline, and stage names and positions repeat across them, so group by pipeline_id rather than assuming one board. A deal can only move between stages of its OWN pipeline, and pipeline_is_default marks the one new deals are filed into.
Inputs: no named parameters.
list_tasksList tasksARead-onlyInspect
List follow-up tasks for this account, soonest due first.
Inputs: limit, status, due_before.
log_activityLog an activity on a contactAInspect
Add a note, call, voicemail, meeting or text to a contact timeline. This is how you record something that already happened. It also bumps the contact to the top of the list.
Inputs: body (required), kind (required), contact_id (required).
log_outreachLog outreach and optionally schedule a follow-upAInspect
Record that you texted, called or left a voicemail for a contact, and optionally create a dated follow-up task. The follow-up date is computed in this account timezone, not UTC.
Inputs: channel (required), contact_id (required), contact_name, followup_days.
move_deal_stageMove a deal to another stageAInspect
Move a deal along the pipeline. Get stage ids from list_pipeline_stages and deal ids from list_opportunities. The stage must belong to the same pipeline the deal is already in — check the stage pipeline_id against the deal pipeline_id, since stage names repeat across pipelines. This tool moves a deal WITHIN its pipeline; it cannot move one to a different pipeline. Whether the deal counts as won or lost is decided by the stage you move it into, not by anything you pass here.
Inputs: stage_id (required), opportunity_id (required).
rename_pipelineRename a pipelineAInspect
Rename a pipeline. Its stages, deals and default status do not change. Get pipeline_id from list_pipeline_stages. Refused if another pipeline in this account already has that name, ignoring case.
Inputs: name (required), pipeline_id (required).
rename_pipeline_stageRename a pipeline stageAInspect
Rename a stage. Any stage can be renamed, including Won and Lost (for example "Retained" and "Declined"); a stage keeps its role, so deals and lead statuses are unaffected. Get stage_id from list_pipeline_stages. Refused if another stage in the same pipeline already has that name, ignoring case.
Inputs: name (required), stage_id (required).
reorder_pipeline_stagesReorder pipeline stagesAInspect
Set the left-to-right order of a pipeline's OPEN stages. Pass open_stage_ids as the COMPLETE list of that pipeline's stages that are neither Won nor Lost, in the new order; Won and Lost always stay last and must not be included. The first stage is where new leads land. Read the stages with list_pipeline_stages immediately before calling. Refused if the list is not exactly the current open stages. To also be refused when someone has REORDERED them since you read them, pass current_order; without it, your order simply replaces theirs.
Inputs: pipeline_id (required), open_stage_ids (required), current_order.
search_contactsSearch contactsARead-onlyInspect
Find contacts by name, email, or phone. A phone number matches however it is typed: "(864) 555-1234", "864-555-1234" and "+18645551234" all find the same contact.
Inputs: query (required), limit.
send_lead_emailEmail a leadADestructiveInspect
Send one email to a lead from one of this account's verified mailboxes and record it on the lead. Use list_mailboxes to get a mailbox id. You do not choose the recipient address; it is read from the lead record. Sending is refused if the address has opted out. The lead is moved to contacted automatically if it was still new.
Inputs: body (required), lead_id (required), subject (required), mailbox_id (required).
send_lead_smsText a leadADestructiveInspect
Send one SMS to a lead, from this account's registered number, and record it on the lead. You do not choose the recipient number or the sending number: both are resolved from the lead record and the account. Sending is refused unless the recipient has a recorded opt-in, is not on the do-not-text or opt-out list, and it is inside their local allowed hours. Those checks run on the server and cannot be overridden by anything you pass. A refusal is not a fault to report as an outage, it is the answer. Set message_class to marketing for anything promotional, a follow-up, or anything with a call to action; transactional is only for a direct reply about what this person contacted us about. If you are unsure, it is marketing. An opt-out line is added automatically, so do not write one.
Inputs: body (required), lead_id (required), message_class (required).
set_default_pipelineMake a pipeline the defaultAInspect
Make a pipeline the default: new leads from calls, web chat, forms without their own pipeline and Meta lead ads, and deals created without a pipeline_id, land in its first stage from now on. Exactly one pipeline is the default (pipeline_is_default in list_pipeline_stages). Existing deals do not move. Calling it on the current default changes nothing.
Inputs: pipeline_id (required).
set_lead_statusSet lead statusAInspect
Move a lead between new, contacted and closed. Use list_leads or get_lead first to find the lead id.
Inputs: status (required), lead_id (required).
set_meta_lead_routeRoute Meta leads to a pipelineAInspect
Choose which pipeline new Meta lead-ad leads go to. Give page_id alone to set the Page's route (every form on that Page), or page_id and form_id to override one form. pipeline_id null clears the route at that level (a Page falls back to the account default; a form falls back to its Page). Only connected Pages, and only forms that have already sent a lead, can be routed: get both from list_meta_lead_routes. Clearing (pipeline_id null, no form_id) also works for a Page that is no longer connected (stale_pages) and clears that Page's form routes too, since leftover routes would otherwise block deleting the pipeline they name. Existing deals do not move; it applies to leads that arrive from now on.
Inputs: page_id (required), pipeline_id (required), form_id.
set_task_statusComplete or reopen a taskAInspect
Mark a task done or put it back to open. Completing it removes its calendar event, because the calendar shows open work only; reopening puts the event back.
Inputs: done (required), task_id (required).
update_contactUpdate a contactAInspect
Edit a contact: name, email, phone, lifecycle stage, company, or address (address_line1, address_line2, city, state, postal_code, country). Only the fields you send are changed; anything you omit keeps its current value. Send an empty string to clear a field. A contact must keep at least one of name, email or phone.
Inputs: contact_id (required), city, email, phone, +9 more.
update_taskUpdate a taskAInspect
Change a task title and/or due date. Both are replaced, so send the title even when only the date is changing. Any linked calendar event is reconciled to match.
Inputs: title (required), task_id (required), due_at.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.