Name: Getfly CRM MCP by usefulapi
Author: usefulapi

Getfly CRM MCP by usefulapi

MCP server for Getfly CRM — customers, opportunities, orders, tickets and tasks.

Tool-list grade A Remote · Streamable HTTP No auth needed 29 tools v1.0.1 MIT

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

MCP server for Getfly CRM — customers, opportunities, orders, tickets and tasks.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http getfly-crm-mcp-by-usefulapi https://getfly-crm.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   getfly_list_users, getfly_get_user, getfly_list_accounts and 26 more

Getfly CRM MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

usefulapi421 servers

24 categories

All 421 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List the Getfly CRM users (employees): user id, name, department, email, phone. Use the user_name (login name) for the recipient/manager arguments of the create tools. Filters: user_id, contact_name, email, contact_mobile, valid (1 = active users). GET /api/v6.1/users.

Parameter	Type	Required	Notes
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
filters	object	no	Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Example

One user by id or by login name (exactly one of user_id and user_username). GET /api/v6.1/user.

Parameter	Type	Required	Notes
user_id	integer	no	User id (from getfly_list_users).
user_username	string	no	User login name.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

List customers (accounts, i.e. companies or individuals) with code, name, phone, email, address, type, source, relationship, manager, total revenue and contacts. Filters: id, account_code, account_name, phone_office, email, account_type, account_source, relation_id, industry, billing_address_street, created_at, updated_at (gte/lte/between), account_manager (user id), sale_order_status. Newest firs

Parameter	Type	Required	Notes
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
filters	object	no	Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Example

One customer by its customer code (account_code, e.g. KH/2025/000001): full profile with contacts, custom fields, type, source, industry, manager and revenue. GET /api/v6.1/account?account_code=.

Parameter	Type	Required	Notes
account_code	string	yes	Customer code (account_code), from getfly_list_accounts.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

WRITE: Create a new customer (account) in Getfly CRM. The customer code must be unique (leave it out to let Getfly generate one). Type, source, industry, relationship, country, province, district and ward are given by NAME and must match the names configured in Getfly. Optionally adds one primary contact. Creating records may trigger the workflows and notifications set up in the CRM. POST /api/v6.

Parameter	Type	Required	Notes
account_name	string	yes	Customer name (company or person).
account_code	string	no	Unique customer code. Optional.
email	string	no	—
phone_office	string	no	Office phone number.
billing_address_street	string	no	Street address.
website	string	no	—
description	string	no	—
sic_code	string	no	Tax code.
birthday	string	no	Birthday or founding date, yyyy-mm-dd.
account_manager_username	string	no	Login name of the managing user (getfly_list_users → user_name).
account_type_names	array	no	Customer type names.
account_source_names	array	no	Customer source names.
industry_names	array	no	Industry names.
relation_name	string	no	Relationship name (e.g. New customer).
country_name	string	no	—
province_name	string	no	—
district_name	string	no	—
ward_name	string	no	—
contact	object	no	One primary contact person.
custom_fields	object	no	Custom field values by field key.

WRITE: Update fields of an existing customer, found by its current customer code. Send only the fields to change. Names (relationship, country, province...) must match those configured in Getfly. Contacts and the type/source/industry lists are not editable here. PUT /api/v6.1/account.

Parameter	Type	Required	Notes
current_account_code	string	yes	The customer's current code (account_code).
account_code	string	no	New customer code, only to rename the code.
account_name	string	no	—
email	string	no	—
phone_office	string	no	—
billing_address_street	string	no	—
website	string	no	—
description	string	no	—
sic_code	string	no	Tax code.
birthday	string	no	yyyy-mm-dd.
account_manager_username	string	no	Login name of the new managing user.
relation_name	string	no	—
country_name	string	no	—
province_name	string	no	—
district_name	string	no	—
ward_name	string	no	—
custom_fields	object	no	Custom field values by field key.

List sales campaigns (opportunity pipelines): campaign code and name, responsible user, lock state, related users and the pipeline stages (status ids and names). GET /api/v6.1/campaigns.

Parameter	Type	Required	Notes
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

The pipeline stages of one campaign (status id, name and how many opportunities are in each). Pass exactly one of campaign_id and campaign_code. GET /api/v6.1/campaign/status.

Parameter	Type	Required	Notes
campaign_id	integer	no	—
campaign_code	string	no	—

List sales opportunities (deals in a campaign pipeline) with code, name, stage, probability, handler, customer and campaign. Filter by campaign with the campaign_code argument. GET /api/v6.1/opportunities.

Parameter	Type	Required	Notes
campaign_code	string	no	Only opportunities of this campaign (campaign code from getfly_list_campaigns).
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
filters	object	no	Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Example

One opportunity by its code (e.g. CH2284): stage, probability, handler, customer and campaign. GET /api/v6.1/opportunity.

Parameter	Type	Required	Notes
opportunity_code	string	yes	Opportunity code (opportunity_code).
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

The discussion (comments) on an opportunity: author, text and time. GET /api/v6.1/opportunity/{id}/comments.

Parameter	Type	Required	Notes
opportunity_id	integer	yes	Opportunity id (the numeric id, not the code).
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

WRITE: Create a sales opportunity in a campaign for a customer and assign it to a user. Creates (or links) the customer and contact from the details given. The assigned user and the campaign rules may be notified by Getfly. POST /api/v6.1/opportunity.

Parameter	Type	Required	Notes
campaign_code	string	yes	Campaign code (getfly_list_campaigns).
account_name	string	yes	Customer name.
account_phone	string	yes	Customer phone number.
contact_name	string	yes	Contact person name.
contact_phone	string	yes	Contact phone number.
recipient_username	string	yes	Login name of the user who handles it (getfly_list_users → user_name).
account_code	string	no	Existing customer code, if the customer already exists.
account_email	string	no	—
contact_email	string	no	—

WRITE: Move an opportunity to another stage of its campaign pipeline, without changing anything else. Identify the opportunity by code (or id) and the campaign by code (or id); the new stage by name (or status id) from getfly_get_campaign_stages. Won/lost/cancelled results are not set here. PUT /api/v6.1/opportunity/stage.

Parameter	Type	Required	Notes
opportunity_code	string	no	Opportunity code. Use this or opportunity_id.
opportunity_id	integer	no	—
campaign_code	string	no	Campaign code. Use this or campaign_id.
campaign_id	integer	no	—
opportunity_status_name	string	no	New stage name. Use this or opportunity_status.
opportunity_status	integer	no	New stage (status) id.

WRITE: Post a comment in the discussion of an opportunity, as the given user. Other users following the opportunity may be notified. POST /api/v6.1/opportunity/{id}/comments.

Parameter	Type	Required	Notes
opportunity_id	integer	yes	Opportunity id (the numeric id, not the code).
content	string	yes	Comment text.
user_id	integer	yes	User id posting the comment (getfly_list_users).

List products and services with code, name, category, unit, retail/wholesale/online price, sale price, VAT and dates. GET /api/v6.1/products.

Parameter	Type	Required	Notes
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

One product by its code (e.g. SP.00192): prices, unit, category, VAT, variants and custom fields. GET /api/v6.1/product.

Parameter	Type	Required	Notes
product_code	string	yes	Product code (product_code).
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

List sales orders with code, customer, amounts, discount, VAT, status, payment status, assigned user and line items. Filters: id, order_date, created_at, updated_at (eq, gte, lte, between). Newest first. GET /api/v6.1/sale_orders.

Parameter	Type	Required	Notes
order_date_from	string	no	Orders dated on or after this day, yyyy-mm-dd.
order_date_to	string	no	Orders dated on or before this day, yyyy-mm-dd.
updated_since	string	no	Orders updated at or after this time, yyyy-mm-dd hh:mm:ss.
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
filters	object	no	Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Example

One sales order by its order code: status, payment status, amounts, customer, line items, shipping info and custom fields. Add payment_periods to fields to include the payment schedule. GET /api/v6.1/sale_order.

Parameter	Type	Required	Notes
order_code	string	yes	Order code (order_code), from getfly_list_sale_orders.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

List support tickets with code, title, content, category, customer and custom fields. GET /api/v6.1/tickets.

Parameter	Type	Required	Notes
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
filters	object	no	Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Example

One support ticket by its ticket code. GET /api/v6.1/ticket.

Parameter	Type	Required	Notes
ticket_code	string	yes	Ticket code (ticket_code), from getfly_list_tickets.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

The discussion (comments) on a support ticket: author, text and time. GET /api/v6.1/ticket/{id}/comments.

Parameter	Type	Required	Notes
ticket_id	integer	yes	Ticket id (the numeric id, not the code).
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

The support ticket categories (id and name). Use a name as cate_name when creating a ticket. GET /api/v6.1/ticket/categories.

No parameter schema on file.

The support ticket statuses (id and name). Use a name as status_name when creating a ticket. GET /api/v6.1/ticket/status.

No parameter schema on file.

WRITE: Create a support ticket, optionally for a customer. Category and status are given by NAME and must match the names configured in Getfly (getfly_list_ticket_categories, getfly_list_ticket_statuses). The content may contain HTML. Getfly may notify the support team. POST /api/v6.1/ticket.

Parameter	Type	Required	Notes
ticket_title	string	yes	Short title.
ticket_content	string	yes	Ticket text (HTML allowed).
cate_name	string	no	Category name.
status_name	string	no	Initial status name.
account_code	string	no	Customer code.
account_email	string	no	Customer email.
contact_name	string	no	Contact person name.
expected_at	string	no	Expected resolution date, yyyy-mm-dd.
emergency_phone	string	no	Emergency contact phone.

List tasks with code, name, start/end time, status, progress, assignee, project and related customers. GET /api/v6.1/tasks.

Parameter	Type	Required	Notes
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

One task by its task code: status, progress, assignee, project, dates and custom fields. GET /api/v6.1/task.

Parameter	Type	Required	Notes
task_code	string	yes	Task code (task_code), from getfly_list_tasks.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.

WRITE: Create a task, optionally in a project, assigned to a user and linked to a customer. Project and task type are given by NAME and must exist in Getfly; users by login name. The assignee may be notified by Getfly. POST /api/v6.1/task.

Parameter	Type	Required	Notes
task_name	string	yes	Task name.
task_start_date	string	no	Start, yyyy-mm-dd hh:mm:ss.
task_end_date	string	no	End, yyyy-mm-dd hh:mm:ss.
project_name	string	no	Project name (must exist).
task_type_name	string	no	Task type name.
task_description	string	no	Description (HTML allowed).
task_receiver_username	string	no	Login name of the assignee (getfly_list_users → user_name).
related_users	array	no	Login names of related users.
task_code	string	no	Unique task code. Optional.
task_parent_code	string	no	Code of the parent task.
account_code	string	no	Code of a customer to link to the task.

WRITE: Mark a task as completed, by its task code. POST /api/v6.1/task/complete.

Parameter	Type	Required	Notes
task_code	string	yes	Task code (task_code).

List the cash/bank funds (accounts for receipts and payments) with id, name, parent, level and financial account. GET /api/v6.1/funds.

Parameter	Type	Required	Notes
sort	string	no	Field to sort by (e.g. id, created_at, updated_at). Default: newest id first.
direction	string	no	Sort direction, used with sort (default asc).
limit	integer	no	Records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.
fields	string	no	Comma-separated field names to return (e.g. id,account_name,email). Leave empty for the default set.
filters	object	no	Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt. in, not_in, between and not_between take an array. Example

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Getfly CRM MCP by usefulapi or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.1 · scanned 31 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 1 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digestb0385a189f4a52d19c7bb283bfa7140457d3d70819af938667a5e79b611e6fe1

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
getfly_list_users	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_user	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_accounts	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_account	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_create_account	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
getfly_update_account	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
getfly_list_campaigns	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_campaign_stages	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_opportunities	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_opportunity	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_opportunity_comments	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_create_opportunity	external-sink	external-sink: parameter "recipient", declares readOnlyHint: false, openWorldHint: true
getfly_move_opportunity_stage	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
getfly_add_opportunity_comment	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
getfly_list_products	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_product	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_sale_orders	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_sale_order	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_tickets	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_ticket	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_ticket_comments	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_ticket_categories	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_list_ticket_statuses	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_create_ticket	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
getfly_list_tasks	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_get_task	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
getfly_create_task	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
getfly_complete_task	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
getfly_list_funds	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digestb0385a189f4a52d1

Scanned2026-10-31

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Getfly CRM MCP by usefulapi

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also