Record a NethLink heartbeat (last-seen)

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL


        
          
            https://bump.sh/nethesis/doc/nethcti-middleware/mcp

Standard setup for AI tools providing an mcp.json file

{
  "NethVoice - NethCTI middleware MCP server": {
    "url": "https://bump.sh/nethesis/doc/nethcti-middleware/mcp"
  }
}

POST /user/nethlink

Bearer auth

Upserts the NethLink last-seen row for the authenticated user (one row per user). The username is taken from the JWT and the timestamp is generated server-side. The optional body carries the client's extension and, additionally to the legacy nethcti-server endpoint, the NethLink version and OS details.

application/json

Body

extension string

NethLink extension id (the JWT does not carry it)
nethlink_version string

NethLink application version
os_type string

OS family (win32, linux, darwin)
os_release string

OS release/kernel version
arch string

CPU architecture (x64, arm64, ...)

Responses

200 application/json

Heartbeat recorded
Hide response attributes Show response attributes object
- code integer
- message string
- data
- error string
401 application/json

Unauthorized
Hide response attributes Show response attributes object
- code integer
- message string
- data
- error string
500 application/json

Failed to store the heartbeat
Hide response attributes Show response attributes object
- code integer
- message string
- data
- error string

POST /user/nethlink

curl \
 --request POST 'http://localhost:8080/user/nethlink' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --data '{
  "extension": "string",
  "nethlink_version": "string",
  "os_type": "string",
  "os_release": "string",
  "arch": "string"
}'

Request examples

{
  "extension": "string",
  "nethlink_version": "string",
  "os_type": "string",
  "os_release": "string",
  "arch": "string"
}

Response examples (200)

{
  "code": 42,
  "message": "string",
  "error": "string"
}

Response examples (401)

{
  "code": 42,
  "message": "string",
  "error": "string"
}

Response examples (500)

{
  "code": 42,
  "message": "string",
  "error": "string"
}