CentralStationCRM 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: Other

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://centralstationcrm.usefulapi.io/mcp

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

{
  "mcpServers": {
    "centralstationcrm": {
      "url": "https://centralstationcrm.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "centralstationcrm": {
      "type": "http",
      "url": "https://centralstationcrm.usefulapi.io/mcp"
    }
  }
}

https://centralstationcrm.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.

• centralstationcrm_get_current_user

  The CentralStationCRM user this API key belongs to: id, name, login email, the account (subdomain) it is signed in to, timezone. Use the user id to assign records or tasks. GET /user.

• centralstationcrm_list_users

  List the users of the CentralStationCRM account (id, name, email). Use the ids for responsible-user filters and for assigning records. GET /users.

• centralstationcrm_list_people

  List contact people. Optionally filter by tag and order by name, creation or last update. Use search_people to find a person by name, email or phone. GET /people.

• centralstationcrm_search_people

  Find people by last name, first name, email address or phone number (email and phone cannot be combined). Give at least one criterion. GET /people/search.

• centralstationcrm_get_person

  One person by id, optionally with related records (companies, deals, tags, tasks, email addresses, phone numbers, addresses). GET /people/{id}.

• centralstationcrm_list_companies

  List companies. Optionally filter by tag and order by name, creation or last update. Use search_companies to find one by name. GET /companies.

• centralstationcrm_search_companies

  Find companies by name. GET /companies/search.

• centralstationcrm_get_company

  One company by id, optionally with related records (people, deals, tags, tasks, contact details, addresses). GET /companies/{id}.

• centralstationcrm_list_deals

  List deals (sales opportunities) with value, state (open_0/25/50/75, won, lost), pipeline and stage ids, target date. Filter by company, responsible user, pipeline or state; order by date, value, state or name. GET /deals.

• centralstationcrm_search_deals

  Find deals by name. GET /deals/search.

• centralstationcrm_get_deal

  One deal by id, optionally with its tags, people, company, tasks and calendar events. GET /deals/{id}.

• centralstationcrm_get_deal_stats

  Number and total value of all deals (optionally only those with a tag), with the account currency. GET /deals/stats.

• centralstationcrm_list_deal_types

  List the deal types (pipelines) with their stages. Use the ids (and stage ids) to create deals and to move them between stages. GET /deal_types.

• centralstationcrm_list_projects

  List projects with state, target date and company. Filter by tag; order by date, state or name. GET /projects.

• centralstationcrm_search_projects

  Find projects by name. GET /projects/search.

• centralstationcrm_get_project

  One project by id, optionally with its tags, people, company, tasks and calendar events. GET /projects/{id}.

• centralstationcrm_list_tasks

  List tasks (to-dos, calls, emails, visits) of the account. Filter by open/closed state, due-date range and responsible user. GET /tasks.

• centralstationcrm_get_task

  One task by id. GET /tasks/{id}.

• centralstationcrm_list_notes

  List protocols: notes, logged emails and other history entries. Filter by the person, company, deal or project they belong to. GET /protocols.

• centralstationcrm_get_note

  One note / history entry by id. GET /protocols/{id}.

• centralstationcrm_list_calendar_events

  List calendar events (appointments, meetings) of the account. Filter by upcoming/old and date range. GET /cal_events.

• centralstationcrm_search_all

  Full-text search across people, companies, deals and projects for a term. GET /search.

• centralstationcrm_list_tags

  List all tag names used in the account. GET /tags/list.

• centralstationcrm_count_records

  Total number of people, companies, deals or projects (optionally only those with a tag). GET / /count.

• centralstationcrm_create_person

  WRITE: create a contact person (last name required), optionally with email addresses and phone numbers. Nothing is sent to the contact. POST /people.

• centralstationcrm_update_person

  WRITE: change fields of a person. Only the fields you give are sent; the rest stays. PUT /people/{id}.

• centralstationcrm_create_company

  WRITE: create a company. Nothing is sent to the contact. POST /companies.

• centralstationcrm_update_company

  WRITE: change fields of a company. Only the fields you give are sent. PUT /companies/{id}.

• centralstationcrm_create_deal

  WRITE: create a deal (sales opportunity). Use list_deal_types for pipeline and stage ids. Pipelines with a monetary value or target date need value and target_date (value_type defaults to total); the vendor says what is missing. Nothing is sent to the contact. POST /deals.

• centralstationcrm_update_deal

  WRITE: change fields of a deal, for example move it to another stage or set its state to won or lost. Only the fields you give are sent. PUT /deals/{id}.

• centralstationcrm_create_task

  WRITE: create a task (to-do, call, email, visit...) optionally attached to a person, company or deal and assigned to a user. Nothing is sent to the contact. POST /tasks.

• centralstationcrm_update_task

  WRITE: change a task, for example mark it done (finished = true), rename it or reschedule it. Only the fields you give are sent. PUT /tasks/{id}.

• centralstationcrm_create_note

  WRITE: add a note to the history of one or more people, companies, deals or projects. Nothing is sent to the contact. POST /protocols.

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 58 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

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

Compared with others in Otheri

• More stars than 0% of the other 32476 servers in this category
• Published to the registry more recently than 99% of the other 32476 servers in this category
• Basic checks equal to or better than 100% of the other 32476 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

{