Pipeline CRM MCP by usefulapi

io.usefulapi/pipeline-crm · v1.0.0 · productivity

Pipeline CRM MCP by usefulapi is healthy: it completed an MCP handshake in 770 ms and exposes 30 tools.

Manage Pipeline CRM deals, people, companies, notes and calendar entries.

Endpoint: https://pipeline-crm.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)	0
Handshake	Healthy
Auth needed	None
Tool count	30
Latency	770 ms
Last checked (UTC)	2026-10-15T12:10:10.623Z

Health history

Checked (UTC)	Status	Latency	Error
2026-10-15T12:10:10.623Z	Healthy	770

Tools (30)

`pipelinecrm_get_profile`	The Pipeline CRM user this credential acts as: id, name and whether they are an account admin. The user's api_key is never returned. GET /profile.
`pipelinecrm_list_users`	List the users of the Pipeline CRM account (id, name, email, team, admin flag). Use the ids as owners of deals, people and companies. api_key values are never returned. GET /users.
`pipelinecrm_get_user`	One user of the account by id. The user's api_key is never returned. GET /users/{id}.
`pipelinecrm_list_deals`	List or search deals with stage, owner, company, primary contact, value, probability and expected close date. Filter by name, stage, pipeline, status, owner, company, contact, archived flag, value range and created, expected-close, closed or modified dates. Money values come back as decimal strings.
`pipelinecrm_get_deal`	One deal by id with owner, company, people, stage, status, loss/won reasons, tags, custom fields and the next task. GET /deals/{id}.
`pipelinecrm_deal_totals_by_stage`	Count and total value of the deals visible to the user in every deal stage: the pipeline summary. GET /deals/totals_by_stage.
`pipelinecrm_list_deal_notes`	List the notes (activities) logged on one deal, with author, category and content. GET /deals/{id}/notes.
`pipelinecrm_create_deal`	WRITE: create a deal. Give the owner (user id), stage id, value, expected close date and company or primary contact when known; a new company is created from company_name if no company_id is given. No email is sent to the owner. POST /deals.
`pipelinecrm_update_deal`	WRITE: change fields of a deal; only the fields you pass change. Move it to another stage with stage_id. Setting probability to 100 or 0 closes the deal as won or lost; give won/loss reason ids when you do. Archive with archived: true. No email is sent to a new owner. PUT /deals/{id}.
`pipelinecrm_list_people`	List or search people (leads and contacts) with email, phones, position, company, owner, lead status and tags. Use search for a quick match on name, email or company name, or filter precisely. GET /people.
`pipelinecrm_get_person`	One person (lead or contact) by id with all contact details, company, owner, tags and custom fields. GET /people/{id}.
`pipelinecrm_list_person_deals`	List the deals one person is associated with. GET /people/{id}/deals.
`pipelinecrm_list_person_notes`	List the notes (activities) logged on one person. GET /people/{id}/notes.
`pipelinecrm_create_person`	WRITE: create a lead or contact. Pass at least a first or last name or an email. No email is sent to the owner. POST /people.
`pipelinecrm_update_person`	WRITE: change fields of a person; only the fields you pass change. Pass type Contact to convert a lead. PUT /people/{id}.
`pipelinecrm_list_companies`	List or search companies with address, website, phones, owner, tags and pipeline totals. GET /companies.
`pipelinecrm_get_company`	One company by id with address, phones, website, owner, tags and custom fields. GET /companies/{id}.
`pipelinecrm_list_company_people`	List the people (leads and contacts) who work at one company. GET /companies/{id}/people.
`pipelinecrm_create_company`	WRITE: create a company. POST /companies.
`pipelinecrm_update_company`	WRITE: change fields of a company; only the fields you pass change. PUT /companies/{id}.
`pipelinecrm_list_notes`	List notes (called activities in the Pipeline CRM app) attached to a deal, person or company. Pass at least one of deal_id, person_id, company_id. Filter by text, category, author and created date. GET /notes.
`pipelinecrm_get_note`	One note (activity) by id with its content, author, category, associations and comments. GET /notes/{id}.
`pipelinecrm_add_note`	WRITE: log a note (activity) on a deal, person or company. Pass at least one of deal_id, person_id, company_id. POST /notes.
`pipelinecrm_list_calendar_entries`	List calendar entries: tasks (a due date) and events (a start and end time) tied to deals, people or companies. Filter by kind, owner, a date range, and completed, incomplete or late. GET /calendar_entries.
`pipelinecrm_get_calendar_entry`	One calendar entry (task or event) by id. GET /calendar_entries/{id}.
`pipelinecrm_create_calendar_entry`	WRITE: create a task (CalendarTask, optional due date) or an event (CalendarEvent, start_time and end_time required), optionally tied to a deal, person or company. POST /calendar_entries.
`pipelinecrm_update_calendar_entry`	WRITE: change a task or event; only the fields you pass change. Pass complete: true to mark a task done. PUT /calendar_entries/{id}.
`pipelinecrm_list_deal_stages`	List the deal stages with id, name, default win probability and the pipeline each belongs to. Use the ids to filter or move deals. GET /admin/deal_stages.
`pipelinecrm_list_deal_pipelines`	List the deal pipelines (each has its own stages) with id, name and which one is the default. GET /admin/deal_pipelines.
`pipelinecrm_list_lookup`	List one set of account lookup values to get ids for filters and writes. kind: deal_statuses, deal_loss_reasons, deal_won_reasons, deal_tags, lead_statuses, lead_sources, contact_tags, company_tags, note_categories, event_categories, task_priorities, task_statuses, teams. GET /admin/<kind>.