Manage Pipeline CRM deals, people, companies, notes and calendar entries. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"pipeline-crm": {
"url": "https://pipeline-crm.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"pipeline-crm": {
"type": "http",
"url": "https://pipeline-crm.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your API token (or legacy api_key).
Optional: App key — only with a legacy api_key.
Create the token in Pipeline CRM under your profile → API tokens (an account admin may first need to grant you access). Choose Read only if you only need reports. With an older api_key (Admin → API Keys), also enter the app key from Admin → API Integrations; with an API token, leave the app key empty. Your credentials are used only to call the Pipeline CRM API on your behalf; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API token (or legacy api_key). If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
pipelinecrm_get_profile | read | Get my 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 | read | 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 | read | Get user One user of the account by id. The user's api_key is never returned. GET /users/{id}. |
pipelinecrm_list_deals | read | 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. GET /deals. |
pipelinecrm_get_deal | read | 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 | read | 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 | read | List notes on a deal List the notes (activities) logged on one deal, with author, category and content. GET /deals/{id}/notes. |
pipelinecrm_create_deal | write | 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 | 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 | read | List people (leads and contacts) 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 | read | 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 | read | List deals of a person List the deals one person is associated with. GET /people/{id}/deals. |
pipelinecrm_list_person_notes | read | List notes on a person List the notes (activities) logged on one person. GET /people/{id}/notes. |
pipelinecrm_create_person | write | 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 | 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 | read | List companies List or search companies with address, website, phones, owner, tags and pipeline totals. GET /companies. |
pipelinecrm_get_company | read | Get company One company by id with address, phones, website, owner, tags and custom fields. GET /companies/{id}. |
pipelinecrm_list_company_people | read | List people at a company List the people (leads and contacts) who work at one company. GET /companies/{id}/people. |
pipelinecrm_create_company | write | Create company WRITE: create a company. POST /companies. |
pipelinecrm_update_company | write | Update company WRITE: change fields of a company; only the fields you pass change. PUT /companies/{id}. |
pipelinecrm_list_notes | read | 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 | read | Get note One note (activity) by id with its content, author, category, associations and comments. GET /notes/{id}. |
pipelinecrm_add_note | write | 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 | read | List tasks and events 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 | read | Get task or event One calendar entry (task or event) by id. GET /calendar_entries/{id}. |
pipelinecrm_create_calendar_entry | write | Create task or event 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 | Update task or event 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 | read | 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 | read | 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 | read | List lookup values 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>. |
pipelinecrm_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
pipelinecrm_request_feature | Request a missing feature Tell usefulapi that the user needs something the Pipeline CRM tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
pipelinecrm_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Pipeline CRM tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
pipelinecrm_cancel_subscription | Cancel the Pro subscription Cancel the caller's Pipeline CRM Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run pipelinecrm_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Pipeline CRM server only. Subscribe with pipelinecrm_upgrade (it returns a Stripe Checkout link). Cancel any time with pipelinecrm_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running pipelinecrm_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Pipeline CRM. The server calls the Pipeline CRM API with your own Pipeline CRM access, so it sees only the data that your account can see.
The login page asks for your API token (or legacy api_key). See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API token (or legacy api_key). If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Pipeline CRM API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Pipeline CRM.
Yes, if you approve it. 9 of the 30 Pipeline CRM tools can create or change data. The other 21 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Pipeline CRM server only. Run pipelinecrm_usage_status to see how many calls you used.
Ask the AI to run pipelinecrm_upgrade: it returns a Stripe Checkout link. To cancel, run pipelinecrm_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with pipelinecrm_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.