Manage deals, contacts, companies and tasks in your Pipeline CRM account
Connect to Pipeline CRM to view and manage deals, people, companies, notes and calendar entries. Create and update deals and contacts, log activities, and track sales pipeline progress across stages.
Try asking Muse: "Show me all open deals in my pipeline worth over $10,000 and their expected close dates"
Source: Found in the official MCP Registry (io.usefulapi/pipeline-crm) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 3 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://pipeline-crm.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Pipeline CRM is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://pipeline-crm.usefulapi.io/mcpResponse time at the last check: 1533ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
pipelinecrm_get_profileThe 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_usersList 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_userOne user of the account by id. The user's api_key is never returned. GET /users/{id}.pipelinecrm_list_dealsList 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 backpipelinecrm_get_dealOne 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_stageCount 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_notesList the notes (activities) logged on one deal, with author, category and content. GET /deals/{id}/notes.pipelinecrm_create_dealWRITE: 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_dealWRITE: 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/pipelinecrm_list_peopleList 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_personOne person (lead or contact) by id with all contact details, company, owner, tags and custom fields. GET /people/{id}.pipelinecrm_list_person_dealsList the deals one person is associated with. GET /people/{id}/deals.pipelinecrm_list_person_notesList the notes (activities) logged on one person. GET /people/{id}/notes.pipelinecrm_create_personWRITE: 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_personWRITE: change fields of a person; only the fields you pass change. Pass type Contact to convert a lead. PUT /people/{id}.pipelinecrm_list_companiesList or search companies with address, website, phones, owner, tags and pipeline totals. GET /companies.pipelinecrm_get_companyOne company by id with address, phones, website, owner, tags and custom fields. GET /companies/{id}.pipelinecrm_list_company_peopleList the people (leads and contacts) who work at one company. GET /companies/{id}/people.pipelinecrm_create_companyWRITE: create a company. POST /companies.pipelinecrm_update_companyWRITE: change fields of a company; only the fields you pass change. PUT /companies/{id}.pipelinecrm_list_notesList 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_noteOne note (activity) by id with its content, author, category, associations and comments. GET /notes/{id}.pipelinecrm_add_noteWRITE: 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_entriesList 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_entryOne calendar entry (task or event) by id. GET /calendar_entries/{id}.pipelinecrm_create_calendar_entryWRITE: 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_entryWRITE: 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_stagesList 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_pipelinesList the deal pipelines (each has its own stages) with id, name and which one is the default. GET /admin/deal_pipelines.pipelinecrm_list_lookupList 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 /adhttps://pipeline-crm.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Pipeline CRM to help me. It is a free service with an MCP server at https://pipeline-crm.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 29, 2026, 09:16 UTC) the endpoint was working, answering in 1533ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 30 tools, including pipelinecrm_get_profile, pipelinecrm_list_users, pipelinecrm_get_user, pipelinecrm_list_deals. For example, you could ask Muse: "Show me all open deals in my pipeline worth over $10,000 and their expected close dates"
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/pipeline-crm)). If you build Pipeline CRM, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/pipeline-crm"><img src="https://musedirectory.ai/badge/pipeline-crm.svg" alt="Pipeline CRM on musedirectory.ai" width="236" height="40"></a>