Pipeline CRM MCP by usefulapi
REMOTE · PIPELINE-CRM.USEFULAPI.IO
Manage Pipeline CRM deals, people, companies, notes and calendar entries.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 16 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4970 tokens (~165/item across 30 items; 30 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://pipeline-crm.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pipeline-crm.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://pipeline-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://pipeline-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://pipeline-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://pipeline-crm.usefulapi.io/mcp |
| Authorisation server | https://pipeline-crm.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pipeline-crm.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/pipeline-crm/ |
| http (plaintext) | http://pipeline-crm.usefulapi.io/mcp | Inconclusive | 302 | http://pipeline-crm.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pipelinecrm_add_note Add note ~122
WRITE: log a note (activity) on a deal, person or company. Pass at least one of deal_id, person_id, company_id. POST /notes.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Attach to this company. |
| content | string | yes | The note text. |
| deal_id | integer | – | Attach to this deal. |
| note_category_id | integer | – | Note category id (see pipelinecrm_list_lookup with kind note_categories). |
| person_id | integer | – | Attach to this person. |
| title | string | – | Optional note title. |
No output schema declared.
No examples provided.
pipelinecrm_create_calendar_entry Create task or event ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | boolean | – | All-day entry (events default to false, tasks to true). |
| association_id | integer | – | Id of the deal, person or company this entry belongs to. |
| association_type | string | – | Type of the record this entry belongs to (with association_id). |
| category_id | integer | yes | Event category id (required by Pipeline CRM; see pipelinecrm_list_lookup with kind event_categories). |
| description | string | – | Details. |
| due_date | string | – | Tasks only: the due date (yyyy-mm-dd). |
| end_time | string | – | Events only: end time. |
| name | string | yes | Title of the task or event. |
| start_time | string | – | Events only: start time. |
| type | string | yes | CalendarTask or CalendarEvent. |
No output schema declared.
No examples provided.
pipelinecrm_create_company Create company ~182
WRITE: create a company. POST /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| address_1 | string | – | Address line 1. |
| address_2 | string | – | Address line 2. |
| city | string | – | City. |
| country | string | – | Country. |
| custom_fields | object | – | Custom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM). |
| description | string | – | Description. |
| string | – | Company email address. | |
| name | string | yes | Company name. |
| owner_id | integer | – | Owner user id. |
| phone1 | string | – | Primary business phone. |
| postal_code | string | – | Postal code. |
| state | string | – | State or province. |
| tag_ids | array | – | Full list of company tag ids. |
| web | string | – | Website. |
No output schema declared.
No examples provided.
pipelinecrm_create_deal Create deal ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Existing company id. |
| company_name | string | – | Creates a new company with this name for the deal. |
| custom_fields | object | – | Custom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM). |
| expected_close_date | string | – | Expected close date (yyyy-mm-dd). |
| name | string | yes | Deal name. |
| owner_id | integer | – | User id of the owner (default: the authenticated user). |
| person_ids | array | – | Ids of the people associated with the deal. |
| primary_contact_id | integer | – | Existing person id of the primary contact. |
| source_id | integer | – | Lead source id (see pipelinecrm_list_lookup with kind lead_sources). |
| stage_id | integer | – | Deal stage id (see pipelinecrm_list_deal_stages). |
| summary | string | – | Description of the deal. |
| tag_ids | array | – | Deal tag ids. |
| value | – | – | The deal's value in its currency. |
No output schema declared.
No examples provided.
pipelinecrm_create_person Create person ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Existing company id. |
| company_name | string | – | Links the company with this name, creating it when none matches. |
| custom_fields | object | – | Custom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM). |
| string | – | Work email address. | |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| lead_source_id | integer | – | Lead source id. |
| lead_status_id | integer | – | Lead status id. |
| mobile | string | – | Mobile phone. |
| owner_id | integer | – | Owner user id. |
| phone | string | – | Work phone. |
| position | string | – | Job title. |
| summary | string | – | Notes about the person. |
| tag_ids | array | – | Full list of contact tag ids. |
| type | string | – | Lead or Contact (default: the account's default). |
No output schema declared.
No examples provided.
pipelinecrm_deal_totals_by_stage Deal totals by stage ~44
Count and total value of the deals visible to the user in every deal stage: the pipeline summary. GET /deals/totals_by_stage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pipelinecrm_get_calendar_entry Get task or event ~43
One calendar entry (task or event) by id. GET /calendar_entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_entry_id | integer | yes | Pipeline CRM calendar entry id. |
No output schema declared.
No examples provided.
pipelinecrm_get_company Get company ~46
One company by id with address, phones, website, owner, tags and custom fields. GET /companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | Pipeline CRM company id. |
No output schema declared.
No examples provided.
pipelinecrm_get_deal Get deal ~59
One deal by id with owner, company, people, stage, status, loss/won reasons, tags, custom fields and the next task. GET /deals/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | yes | Pipeline CRM deal id. |
No output schema declared.
No examples provided.
pipelinecrm_get_note Get note ~47
One note (activity) by id with its content, author, category, associations and comments. GET /notes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | integer | yes | Pipeline CRM note id. |
No output schema declared.
No examples provided.
pipelinecrm_get_person Get person ~51
One person (lead or contact) by id with all contact details, company, owner, tags and custom fields. GET /people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | integer | yes | Pipeline CRM person id. |
No output schema declared.
No examples provided.
pipelinecrm_get_profile Get my profile ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pipelinecrm_get_user Get user ~44
One user of the account by id. The user's api_key is never returned. GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | Pipeline CRM user id. |
No output schema declared.
No examples provided.
pipelinecrm_list_calendar_entries List tasks and events ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Only entries on or after this date (yyyy-mm-dd). |
| kind | string | – | Only tasks or only events. |
| owner_id | integer | – | Only entries owned by this user id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| status | string | – | Only incomplete, completed or late (overdue) entries. |
| to_date | string | – | Only entries on or before this date (yyyy-mm-dd). |
No output schema declared.
No examples provided.
pipelinecrm_list_companies List companies ~257
List or search companies with address, website, phones, owner, tags and pipeline totals. GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Companies in this city. |
| country | string | – | Companies in this country. |
| created_after | string | – | Created on or after this date (yyyy-mm-dd). |
| created_before | string | – | Created on or before this date (yyyy-mm-dd). |
| is_customer | boolean | – | true = customers only, false = non-customers only. |
| modified_after | string | – | Modified on or after this date (yyyy-mm-dd). |
| name | string | – | Companies whose name starts with this text. |
| owner_id | integer | – | Only companies owned by this user id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| sort | string | – | Sort column key, with a leading - for descending; several keys separated by commas. Example: -deal_value,deal_name. Custom fields sort as custom_label_<id>. |
| tag_ids | array | – | Only companies with these tag ids. |
No output schema declared.
No examples provided.
pipelinecrm_list_company_people List people at a company ~91
List the people (leads and contacts) who work at one company. GET /companies/{id}/people.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | Pipeline CRM company id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
No output schema declared.
No examples provided.
pipelinecrm_list_deal_notes List notes on a deal ~96
List the notes (activities) logged on one deal, with author, category and content. GET /deals/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | yes | Pipeline CRM deal id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
No output schema declared.
No examples provided.
pipelinecrm_list_deal_pipelines List deal pipelines ~88
List the deal pipelines (each has its own stages) with id, name and which one is the default. GET /admin/deal_pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
No output schema declared.
No examples provided.
pipelinecrm_list_deal_stages List deal stages ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
No output schema declared.
No examples provided.
pipelinecrm_list_deals List deals ~496
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. GET /deals.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = archived deals only, false = not archived only. |
| closed_after | string | – | Closed (won or lost) on or after this date (yyyy-mm-dd). |
| closed_before | string | – | Closed (won or lost) on or before this date (yyyy-mm-dd). |
| company_name | string | – | Only deals whose company name contains this text. |
| created_after | string | – | Created on or after this date (yyyy-mm-dd). |
| created_before | string | – | Created on or before this date (yyyy-mm-dd). |
| expected_close_after | string | – | Expected to close on or after this date (yyyy-mm-dd). |
| expected_close_before | string | – | Expected to close on or before this date (yyyy-mm-dd). |
| max_value | number | – | Only deals worth at most this much. |
| min_value | number | – | Only deals worth at least this much. |
| modified_after | string | – | Modified on or after this date (yyyy-mm-dd). |
| name | string | – | Deals whose name contains this text. |
| owner_id | integer | – | Only deals owned by this user id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| pipeline_id | integer | – | Only deals in this deal pipeline id (see pipelinecrm_list_deal_pipelines). |
| primary_contact_id | integer | – | Only deals whose primary contact is this person id. |
| sort | string | – | Sort column key, with a leading - for descending; several keys separated by commas. Example: -deal_value,deal_name. Custom fields sort as custom_label_<id>. |
| stage_id | integer | – | Only deals in this deal stage id (see pipelinecrm_list_deal_stages). |
| status_id | integer | – | Only deals with this deal status id (open, won, lost... see pipelinecrm_list_lookup with kind deal_statuses). |
No output schema declared.
No examples provided.
pipelinecrm_list_lookup List lookup values ~137
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which lookup list to return. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
No output schema declared.
No examples provided.
pipelinecrm_list_notes List notes ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id | integer | – | Only notes written by this user id. |
| category_id | integer | – | Only notes in this note category id (see pipelinecrm_list_lookup with kind note_categories). |
| company_id | integer | – | Notes on this company. |
| created_after | string | – | Created on or after this date (yyyy-mm-dd). |
| created_before | string | – | Created on or before this date (yyyy-mm-dd). |
| deal_id | integer | – | Notes on this deal. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| person_id | integer | – | Notes on this person. |
| query | string | – | Free-text search across title, content, category and comments. |
| sort | string | – | Sort column key, with a leading - for descending; several keys separated by commas. Example: -deal_value,deal_name. Custom fields sort as custom_label_<id>. |
No output schema declared.
No examples provided.
pipelinecrm_list_people List people (leads and contacts) ~353
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Only people at this company id. |
| company_name | string | – | Only people whose company name contains this text. |
| created_after | string | – | Created on or after this date (yyyy-mm-dd). |
| created_before | string | – | Created on or before this date (yyyy-mm-dd). |
| string | – | Matches the work email address. | |
| modified_after | string | – | Modified on or after this date (yyyy-mm-dd). |
| name | string | – | Matches the first or last name. |
| owner_id | integer | – | Only people owned by this user id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| search | string | – | Matches first name, last name, email or company name. |
| sort | string | – | Sort column key, with a leading - for descending; several keys separated by commas. Example: -deal_value,deal_name. Custom fields sort as custom_label_<id>. |
| source_id | integer | – | Only people with this lead source id. |
| status_id | integer | – | Only people with this lead status id (see pipelinecrm_list_lookup with kind lead_statuses). |
| tag_ids | array | – | Only people with these tag ids. |
| type | string | – | Only leads or only contacts. |
No output schema declared.
No examples provided.
pipelinecrm_list_person_deals List deals of a person ~87
List the deals one person is associated with. GET /people/{id}/deals.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| person_id | integer | yes | Pipeline CRM person id. |
No output schema declared.
No examples provided.
pipelinecrm_list_person_notes List notes on a person ~87
List the notes (activities) logged on one person. GET /people/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
| person_id | integer | yes | Pipeline CRM person id. |
No output schema declared.
No examples provided.
pipelinecrm_list_users List users ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Only users with this email address. | |
| including_inactive | boolean | – | Also return deactivated users. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-200 (default 25). |
No output schema declared.
No examples provided.
pipelinecrm_update_calendar_entry Update task or event ~150
WRITE: change a task or event; only the fields you pass change. Pass complete: true to mark a task done. PUT /calendar_entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_entry_id | integer | yes | Pipeline CRM calendar entry id. |
| category_id | integer | – | New event category id. |
| complete | boolean | – | true marks the entry complete, false reopens it. |
| description | string | – | New details. |
| due_date | string | – | Tasks only: new due date (yyyy-mm-dd). |
| end_time | string | – | Events only: new end time. |
| name | string | – | New title. |
| start_time | string | – | Events only: new start time. |
No output schema declared.
No examples provided.
pipelinecrm_update_company Update company ~206
WRITE: change fields of a company; only the fields you pass change. PUT /companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| address_1 | string | – | Address line 1. |
| address_2 | string | – | Address line 2. |
| city | string | – | City. |
| company_id | integer | yes | Pipeline CRM company id. |
| country | string | – | Country. |
| custom_fields | object | – | Custom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM). |
| description | string | – | Description. |
| string | – | Company email address. | |
| name | string | – | New company name. |
| owner_id | integer | – | Owner user id. |
| phone1 | string | – | Primary business phone. |
| postal_code | string | – | Postal code. |
| state | string | – | State or province. |
| tag_ids | array | – | Full list of company tag ids. |
| web | string | – | Website. |
No output schema declared.
No examples provided.
pipelinecrm_update_deal Update deal ~379
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true archives the deal, false restores it. |
| closed_time | string | – | Actual close date (yyyy-mm-dd). |
| company_id | integer | – | Company id. |
| custom_fields | object | – | Custom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM). |
| deal_id | integer | yes | Pipeline CRM deal id. |
| expected_close_date | string | – | New expected close date (yyyy-mm-dd). |
| loss_reason_id | integer | – | Deal loss reason id. |
| loss_reason_notes | string | – | Why the deal was lost. |
| name | string | – | New deal name. |
| owner_id | integer | – | New owner user id. |
| person_ids | array | – | Full list of associated person ids (replaces the list). |
| primary_contact_id | integer | – | Primary contact person id. |
| probability | integer | – | Probability of closing, 0-100. 100 closes the deal as won, 0 as lost. |
| stage_id | integer | – | Move the deal to this deal stage id. |
| status_id | integer | – | Deal status id. |
| summary | string | – | New description. |
| tag_ids | array | – | Full list of deal tag ids (replaces the list). |
| value | – | – | New value. |
| won_reason_id | integer | – | Deal won reason id. |
| won_reason_notes | string | – | Why the deal was won. |
No output schema declared.
No examples provided.
pipelinecrm_update_person Update person ~244
WRITE: change fields of a person; only the fields you pass change. Pass type Contact to convert a lead. PUT /people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Existing company id. |
| company_name | string | – | Links the company with this name, creating it when none matches. |
| custom_fields | object | – | Custom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM). |
| string | – | Work email address. | |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| lead_source_id | integer | – | Lead source id. |
| lead_status_id | integer | – | Lead status id. |
| mobile | string | – | Mobile phone. |
| owner_id | integer | – | Owner user id. |
| person_id | integer | yes | Pipeline CRM person id. |
| phone | string | – | Work phone. |
| position | string | – | Job title. |
| summary | string | – | Notes about the person. |
| tag_ids | array | – | Full list of contact tag ids. |
| type | string | – | Convert the record to a Lead or a Contact. |
No output schema declared.
No examples provided.
How do I install the Pipeline CRM MCP by usefulapi server?
Pipeline CRM MCP by usefulapi is a hosted endpoint at https://pipeline-crm.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pipeline-crm.usefulapi.io
claude mcp add --transport http io-usefulapi-pipeline-crm 'https://pipeline-crm.usefulapi.io/mcp'
What is the Pipeline CRM MCP by usefulapi server?
Pipeline CRM MCP by usefulapi is listed in the public MCP registry as io.usefulapi/pipeline-crm. Manage Pipeline CRM deals, people, companies, notes and calendar entries. This page covers its hosted endpoint (https://pipeline-crm.usefulapi.io/mcp).
Is the Pipeline CRM MCP by usefulapi server safe to use?
Pipeline CRM MCP by usefulapi scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pipeline CRM MCP by usefulapi server expose?
Pipeline CRM MCP by usefulapi exposes 30 tools: pipelinecrm_get_profile, pipelinecrm_list_users, pipelinecrm_get_user, pipelinecrm_list_deals, pipelinecrm_get_deal, and 25 more. Their descriptions and schemas cost roughly 4,763 tokens of context every time the server is loaded.
Does the Pipeline CRM MCP by usefulapi server require authentication?
Yes. Pipeline CRM MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Pipeline CRM MCP by usefulapi server still maintained?
Pipeline CRM MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.