Getfly CRM MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://getfly-crm.usefulapi.io/mcp

claude mcp add --transport http getfly-crm https://getfly-crm.usefulapi.io/mcp

{
  "mcpServers": {
    "getfly-crm": {
      "url": "https://getfly-crm.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "getfly-crm": {
      "type": "http",
      "url": "https://getfly-crm.usefulapi.io/mcp"
    }
  }
}

https://getfly-crm.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• getfly_list_users

  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.

• getfly_get_user

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

• getfly_list_accounts

  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, bil

• getfly_get_account

  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=.

• getfly_create_account

  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

• getfly_update_account

  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/acc

• getfly_list_campaigns

  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.

• getfly_get_campaign_stages

  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.

• getfly_list_opportunities

  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.

• getfly_get_opportunity

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

• getfly_list_opportunity_comments

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

• getfly_create_opportunity

  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.

• getfly_move_opportunity_stage

  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 no

• getfly_add_opportunity_comment

  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.

• getfly_list_products

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

• getfly_get_product

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

• getfly_list_sale_orders

  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.

• getfly_get_sale_order

  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.

• getfly_list_tickets

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

• getfly_get_ticket

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

• getfly_list_ticket_comments

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

• getfly_list_ticket_categories

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

• getfly_list_ticket_statuses

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

• getfly_create_ticket

  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

• getfly_list_tasks

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

• getfly_get_task

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

• getfly_create_task

  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.

• getfly_complete_task

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

• getfly_list_funds

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 626 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 29 tool descriptions and found no hidden instructions to the AI

Compared with others in Marketing & social mediai

• More stars than 0% of the other 2954 servers in this category
• Published to the registry more recently than 98% of the other 2954 servers in this category
• Basic checks equal to or better than 100% of the other 2954 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{