# CentralStationCRM MCP by usefulapi (remote · centralstationcrm.usefulapi.io)

Read CentralStationCRM people, companies, deals, tasks; create and update people, companies, deals.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `centralstationcrm.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-centralstationcrm/centralstationcrm.md), [page](https://verifymcp.io/servers/io-usefulapi-centralstationcrm/centralstationcrm)

## Channel facts

- Endpoint: `https://centralstationcrm.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4041 tokens (~122/item across 33 items; 33 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the CentralStationCRM MCP by usefulapi server?

CentralStationCRM MCP by usefulapi is a hosted endpoint at https://centralstationcrm.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.io-usefulapi-centralstationcrm]
url = "https://centralstationcrm.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-centralstationcrm": {
      "type": "remote",
      "url": "https://centralstationcrm.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-centralstationcrm --url 'https://centralstationcrm.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-centralstationcrm:
    url: "https://centralstationcrm.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-centralstationcrm": {
      "Transport": "http",
      "Url": "https://centralstationcrm.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-centralstationcrm -t streamable-http -u 'https://centralstationcrm.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-centralstationcrm": {
      "type": "http",
      "url": "https://centralstationcrm.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.1.1

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (33)

### `centralstationcrm_get_current_user` (~58 tokens)

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` (~99 tokens)

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.

Input parameters:

- `active` (boolean): Only currently active users.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).

### `centralstationcrm_list_people` (~149 tokens)

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.

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `order` (string): Ordering (abc = by name, new = creation date, update = last change).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `tag_name` (string): Only people with this tag.

### `centralstationcrm_search_people` (~162 tokens)

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.

Input parameters:

- `email` (string): Email address (not combinable with phone).
- `first_name` (string): First name (max 80).
- `includes` (array): Related records to embed (an extra call is not needed for them).
- `name` (string): Last name.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `phone` (string): Phone number (not combinable with email).

### `centralstationcrm_get_person` (~76 tokens)

Get person

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

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `person_id` (integer, required): CentralStationCRM person id.

### `centralstationcrm_list_companies` (~145 tokens)

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.

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `order` (string): Ordering (abc = by name, new = creation date, update = last change).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `tag_name` (string): Only companies with this tag.

### `centralstationcrm_search_companies` (~101 tokens)

Search companies

Find companies by name. GET /companies/search.

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `name` (string, required): Company name (or part of it).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).

### `centralstationcrm_get_company` (~73 tokens)

Get company

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

Input parameters:

- `company_id` (integer, required): CentralStationCRM company id.
- `includes` (array): Related records to embed (an extra call is not needed for them).

### `centralstationcrm_list_deals` (~217 tokens)

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.

Input parameters:

- `company_id` (integer): Only deals of this company.
- `current_state` (string): Only deals in this state.
- `deal_type_id` (integer): Only deals in this pipeline (see list_deal_types).
- `includes` (array): Related records to embed (an extra call is not needed for them).
- `order` (string): Ordering.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `tag_name` (string): Only deals with this tag.
- `user_id` (integer): Only deals of this responsible user.

### `centralstationcrm_search_deals` (~102 tokens)

Search deals

Find deals by name. GET /deals/search.

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `name` (string, required): Deal name (or part of it).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).

### `centralstationcrm_get_deal` (~71 tokens)

Get deal

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

Input parameters:

- `deal_id` (integer, required): CentralStationCRM deal id.
- `includes` (array): Related records to embed (an extra call is not needed for them).

### `centralstationcrm_get_deal_stats` (~54 tokens)

Get deal statistics

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

Input parameters:

- `tag_name` (string): Only deals with this tag.

### `centralstationcrm_list_deal_types` (~48 tokens)

List deal pipelines

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` (~123 tokens)

List projects

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

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `order` (string): Ordering.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `tag_name` (string): Only projects with this tag.

### `centralstationcrm_search_projects` (~100 tokens)

Search projects

Find projects by name. GET /projects/search.

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `name` (string, required): Project name (or part of it).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).

### `centralstationcrm_get_project` (~69 tokens)

Get project

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

Input parameters:

- `includes` (array): Related records to embed (an extra call is not needed for them).
- `project_id` (integer, required): CentralStationCRM project id.

### `centralstationcrm_list_tasks` (~151 tokens)

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.

Input parameters:

- `after` (string): Only tasks after this date.
- `before` (string): Only tasks before this date.
- `order` (string): Ordering by id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `state` (string): Only open or only closed tasks.
- `user_id` (integer): Only tasks of this user.

### `centralstationcrm_get_task` (~35 tokens)

Get task

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

Input parameters:

- `task_id` (integer, required): CentralStationCRM task id.

### `centralstationcrm_list_notes` (~155 tokens)

List notes and activity log entries

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

Input parameters:

- `company_id` (integer): Only entries of this company.
- `deal_id` (integer): Only entries of this deal.
- `order` (string): Ordering by id (id-desc = newest first).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `person_id` (integer): Only entries of this person.
- `project_id` (integer): Only entries of this project.

### `centralstationcrm_get_note` (~42 tokens)

Get note

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

Input parameters:

- `note_id` (integer, required): CentralStationCRM protocol (note) id.

### `centralstationcrm_list_calendar_events` (~130 tokens)

List calendar events

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

Input parameters:

- `after` (string): Only events after this date.
- `before` (string): Only events before this date.
- `order` (string): Ordering by id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).
- `state` (string): Only upcoming or only past events.

### `centralstationcrm_search_all` (~39 tokens)

Search everything

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

Input parameters:

- `term` (string, required): Search term.

### `centralstationcrm_list_tags` (~70 tokens)

List tags

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

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perpage` (integer): Results per page, 1-250 (default 50).

### `centralstationcrm_count_records` (~61 tokens)

Count records

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

Input parameters:

- `resource` (string, required): Which records to count.
- `tag_name` (string): Only records with this tag.

### `centralstationcrm_create_person` (~183 tokens)

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.

Input parameters:

- `background` (string): Background notes about the person.
- `country_code` (string): Language of the person as a 2-letter ISO 639-1 code, e.g. de or en (the vendor field is called country_code).
- `emails` (array)
- `first_name` (string): First name (max 80).
- `name` (string, required): Last name (max 80).
- `phones` (array)
- `salutation` (string): Free-text salutation (max 80).
- `title` (string): Title, e.g. Dr. (max 80).
- `user_id` (integer): Responsible user id (default: the API user).

### `centralstationcrm_update_person` (~174 tokens)

Update person

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

Input parameters:

- `background` (string): New background notes (replaces the old text).
- `country_code` (string): New language of the person as a 2-letter ISO 639-1 code, e.g. de or en (the vendor field is called country_code).
- `first_name` (string): New first name (max 80).
- `name` (string): New last name (max 80).
- `person_id` (integer, required): CentralStationCRM person id.
- `salutation` (string): New salutation (max 80).
- `title` (string): New title (max 80).
- `user_id` (integer): New responsible user id.

### `centralstationcrm_create_company` (~70 tokens)

Create company

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

Input parameters:

- `background` (string): Background notes about the company.
- `name` (string, required): Company name (max 120).
- `user_id` (integer): Responsible user id (default: the API user).

### `centralstationcrm_update_company` (~88 tokens)

Update company

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

Input parameters:

- `background` (string): New background notes (replaces the old text).
- `company_id` (integer, required): CentralStationCRM company id.
- `name` (string): New company name (max 120).
- `user_id` (integer): New responsible user id.

### `centralstationcrm_create_deal` (~225 tokens)

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.

Input parameters:

- `background` (string): Details about the deal.
- `company_id` (integer): Company the deal belongs to.
- `currency` (string): Currency (account default if omitted).
- `deal_type_id` (integer): Pipeline id (see list_deal_types).
- `deal_type_stage_id` (integer): Stage id within the pipeline.
- `name` (string, required): Deal name (max 120).
- `probability` (integer): Probability of winning, percent.
- `target_date` (string): Date the deal shall be won.
- `user_id` (integer): Responsible user id.
- `value` (number): Monetary value (with value_type total: the full amount).
- `value_type` (string): How the value is billed (default total).

### `centralstationcrm_update_deal` (~242 tokens)

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

Input parameters:

- `background` (string): Details about the deal.
- `company_id` (integer): Company the deal belongs to.
- `currency` (string): Currency (account default if omitted).
- `current_state` (string): New state: open_0/25/50/75, won or lost.
- `deal_id` (integer, required): CentralStationCRM deal id.
- `deal_type_id` (integer): Pipeline id (see list_deal_types).
- `deal_type_stage_id` (integer): Stage id within the pipeline.
- `name` (string): New deal name (max 120).
- `probability` (integer): Probability of winning, percent.
- `target_date` (string): Date the deal shall be won.
- `user_id` (integer): Responsible user id.
- `value` (number): Monetary value (with value_type total: the full amount).
- `value_type` (string): How the value is billed (default total).

### `centralstationcrm_create_task` (~173 tokens)

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.

Input parameters:

- `attachable_id` (integer): Id of that record (required with attachable_type).
- `attachable_type` (string): Kind of record the task belongs to (omit for a general task).
- `badge` (string): Kind of task (default task).
- `fuzzy` (boolean): true = only the day of precise_time matters, not the hour.
- `name` (string, required): What has to be done.
- `precise_time` (string): When it is due.
- `user_id` (integer): User the task is assigned to (default: the user behind the API key).

### `centralstationcrm_update_task` (~136 tokens)

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

Input parameters:

- `badge` (string): New kind of task.
- `finished` (boolean): true = mark done, false = reopen.
- `fuzzy` (boolean): true = only the day of precise_time matters.
- `name` (string): New task text.
- `precise_time` (string): New due date-time.
- `task_id` (integer, required): CentralStationCRM task id.
- `user_id` (integer): New assignee.

### `centralstationcrm_create_note` (~144 tokens)

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.

Input parameters:

- `company_ids` (array): Companies the note belongs to.
- `confidential` (boolean): true = visible only to users with at least power-user rights (not only to you).
- `content` (string, required): Note text (markdown).
- `deal_ids` (array): Deals the note belongs to.
- `name` (string, required): Note title (max 100 characters).
- `person_ids` (array): People the note belongs to.
- `project_ids` (array): Projects the note belongs to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-centralstationcrm/centralstationcrm#diagnostics

## Score history

- 2026-10-25: 63
- 2026-10-24: 62

## Common questions

### What is the CentralStationCRM MCP by usefulapi server?

CentralStationCRM MCP by usefulapi is listed in the public MCP registry as io.usefulapi/centralstationcrm. Read CentralStationCRM people, companies, deals, tasks; create and update people, companies, deals. This page covers its hosted endpoint (https://centralstationcrm.usefulapi.io/mcp).

### Is the CentralStationCRM MCP by usefulapi server safe to use?

CentralStationCRM MCP by usefulapi scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CentralStationCRM MCP by usefulapi server expose?

CentralStationCRM MCP by usefulapi exposes 33 tools: centralstationcrm_get_current_user, centralstationcrm_list_users, centralstationcrm_list_people, centralstationcrm_search_people, centralstationcrm_get_person, and 28 more. Their descriptions and schemas cost roughly 3,765 tokens of context every time the server is loaded.

### Does the CentralStationCRM MCP by usefulapi server require authentication?

Yes. CentralStationCRM MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the CentralStationCRM MCP by usefulapi server still maintained?

CentralStationCRM MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://centralstationcrm.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/centralstationcrm/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-centralstationcrm/centralstationcrm.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-centralstationcrm/centralstationcrm.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-centralstationcrm/centralstationcrm