Teamleader Focus MCP by usefulapi
REMOTE · TEAMLEADER-FOCUS.USEFULAPI.IO
Read Teamleader Focus contacts, companies, deals, invoices, projects; create deals, tasks.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5239 tokens (~145/item across 36 items; 36 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 36 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
- Server version: 1.5.0 → 1.5.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “teamleader_add_time_tracking”, which the server declares destructive security
- New tool “teamleader_complete_task”, which the server declares destructive security
- New tool “teamleader_create_event”, which the server declares destructive security
- Schema quality: 3446 → 5239 ▼ functional
- Schema quality: 3446 → 5223 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.4.0 → 1.5.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.0.0 → 1.3.0 functional
- New tool “teamleader_get_product” functional
- New tool “teamleader_get_quotation” functional
- New tool “teamleader_get_subscription” functional
- New tool “teamleader_list_activity_types” functional
- New tool “teamleader_list_departments” functional
- New tool “teamleader_list_events” functional
- New tool “teamleader_list_notes” functional
- New tool “teamleader_list_product_categories” functional
- New tool “teamleader_list_products” functional
- New tool “teamleader_list_quotations” functional
- New tool “teamleader_list_subscriptions” functional
- 23 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://teamleader-focus.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of teamleader-focus.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://teamleader-focus.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://teamleader-focus.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://teamleader-focus.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://teamleader-focus.usefulapi.io/mcp |
| Authorisation server | https://teamleader-focus.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://teamleader-focus.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/teamleader-focus/ |
| http (plaintext) | http://teamleader-focus.usefulapi.io/mcp | Inconclusive | 302 | http://teamleader-focus.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
teamleader_add_note Add a note ~120
WRITE: add a note to a contact, company, deal, invoice, quotation, project and more, e.g. a call summary. Optionally notify colleagues. Returns the new note's id. Teamleader: notes.create.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The note text. |
| notify_user_ids | array | – | Users to notify about this note. |
| subject_id | string | yes | The subject id (a UUID). |
| subject_type | string | yes | What the note is attached to (nextgenProject = a project in the projects module). |
No output schema declared.
No examples provided.
teamleader_add_time_tracking Add tracked time ~286
WRITE: record time spent, e.g. 90 minutes of development for a company. Give started_at plus duration_minutes or ended_at; optionally a work type, a description, the subject (customer, ticket, task, ...) and whether it is invoiceable. Teamleader splits an entry that passes midnight. Returns the new entry's id. Teamleader: timeTracking.add.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| duration_minutes | integer | – | Time spent, in minutes. Give this or ended_at. |
| ended_at | string | – | End; give this or duration_minutes (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
| invoiceable | boolean | – | – |
| started_at | string | yes | Start (ISO 8601 with offset, e.g. 2026-02-04T09:00:00+01:00). |
| subject_id | string | – | The subject id (a UUID). |
| subject_type | string | – | With subject_id: what the time was spent on (todo = a task, nextgenTask = a task in the projects module). |
| user_id | string | – | Record the time for another user (default: the signed-in user). |
| work_type_id | string | – | The work type id (a UUID). |
No output schema declared.
No examples provided.
teamleader_complete_task Complete a task ~50
WRITE: mark a task (to-do) as complete. It can be reopened in Teamleader. Teamleader: tasks.complete.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task id (a UUID). |
No output schema declared.
No examples provided.
teamleader_create_company Create a company ~145
WRITE: create a new company in Teamleader. Only name is required. Returns the new company's id. Teamleader: companies.add.
| Name | Type | Req | Description |
|---|---|---|---|
| business_type_id | string | – | Legal structure id (e.g. NV/BV). |
| string | – | Primary email address. | |
| language | string | – | Language code, e.g. en, nl, fr. |
| name | string | yes | – |
| remarks | string | – | – |
| responsible_user_id | string | – | The user id (a UUID). |
| tags | array | – | Tag names. |
| telephones | array | – | – |
| vat_number | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
teamleader_create_contact Create a contact ~117
WRITE: create a new contact (person) in Teamleader. Only last_name is required. Returns the new contact's id. Teamleader: contacts.add.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Primary email address. | |
| first_name | string | – | – |
| language | string | – | Language code, e.g. en, nl, fr. |
| last_name | string | yes | – |
| remarks | string | – | – |
| tags | array | – | Tag names. |
| telephones | array | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
teamleader_create_deal Create a deal ~253
WRITE: create a new deal for an existing contact or company. Requires the customer and a title; optionally a phase (see teamleader_list_deal_phases), value, probability and expected closing date. Returns the new deal's id. Teamleader: deals.create.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_person_id | string | – | For a company customer: the contact person. |
| customer_id | string | yes | The customer's contact or company id. |
| customer_type | string | yes | Whether the customer is a contact or a company. |
| department_id | string | – | Department (company entity) id. |
| estimated_closing_date | string | – | Expected closing date (YYYY-MM-DD). |
| estimated_probability | number | – | Win probability, 0 to 1. |
| estimated_value_amount | number | – | Expected value; needs estimated_value_currency. |
| estimated_value_currency | string | – | – |
| phase_id | string | – | Starting phase; defaults to the default pipeline's first phase. |
| responsible_user_id | string | – | The user id (a UUID). |
| source_id | string | – | The deal source id (a UUID). |
| summary | string | – | The deal's remarks field. |
| title | string | yes | – |
No output schema declared.
No examples provided.
teamleader_create_event Create a calendar event ~208
WRITE: put a meeting or call on the Teamleader calendar. Requires a title, an activity type id (see teamleader_list_activity_types), a start and an end. Attendees are firm users only; link the customer or deal with links. Returns the new event's id. Teamleader: events.create.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type_id | string | yes | The activity type id (a UUID). |
| attendee_user_ids | array | – | Firm users who attend. |
| description | string | – | – |
| ends_at | string | yes | End (ISO 8601 with offset). |
| links | array | – | Contacts, companies or deals the event is about. |
| location | string | – | – |
| starts_at | string | yes | Start (ISO 8601 with offset, e.g. 2026-02-04T16:00:00+01:00). |
| title | string | yes | – |
| work_type_id | string | – | The work type id (a UUID). |
No output schema declared.
No examples provided.
teamleader_create_task Create a task ~222
WRITE: create a task (to-do). Requires a title, a due date and a work type id (see teamleader_list_work_types). Optionally assign it to a user or team and link a customer, deal, project or ticket. Returns the new task's id. Teamleader: tasks.create.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | string | – | The assignee id (a UUID). |
| assignee_type | string | – | With assignee_id. |
| customer_id | string | – | The customer id (a UUID). |
| customer_type | string | – | With customer_id. |
| deal_id | string | – | The deal id (a UUID). |
| description | string | – | – |
| due_on | string | yes | Due date (YYYY-MM-DD). |
| estimated_duration_minutes | integer | – | – |
| project_id | string | – | The project id (a UUID). |
| ticket_id | string | – | The ticket id (a UUID). |
| title | string | yes | – |
| work_type_id | string | yes | Work type id (required by Teamleader). |
No output schema declared.
No examples provided.
teamleader_get_company Get a company ~56
Fetch one company in full: addresses, VAT number, responsible user, related contacts and companies, tags, custom fields and remarks. Teamleader: companies.info.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company id (a UUID). |
No output schema declared.
No examples provided.
teamleader_get_contact Get a contact ~56
Fetch one contact in full: emails, telephones, addresses, linked companies (with position), tags, custom fields and remarks. Teamleader: contacts.info.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact id (a UUID). |
No output schema declared.
No examples provided.
teamleader_get_current_user Get the current user ~51
Fetch the Teamleader user the sign-in belongs to: name, email, account id, language, time zone and teams. A cheap way to confirm the connection works. Teamleader: users.me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
teamleader_get_deal Get a deal ~66
Fetch one deal in full: lead (customer + contact person), value, probability, current phase, phase history, linked quotations, responsible users, lost reason and custom fields. Teamleader: deals.info.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | The deal id (a UUID). |
No output schema declared.
No examples provided.
teamleader_get_invoice Get an invoice ~63
Fetch one invoice in full: invoicee, grouped line items, discounts, totals and taxes, payment term, payments received, payment reference and Peppol status. Teamleader: invoices.info.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | The invoice id (a UUID). |
No output schema declared.
No examples provided.
teamleader_get_product Get a product ~54
Fetch one product in full: code, description, purchase and selling prices, tax rate, unit, stock and category. Teamleader: products.info.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | The product id (a UUID). |
No output schema declared.
No examples provided.
teamleader_get_quotation Get a quotation ~53
Fetch one quotation in full: deal, grouped line items, discounts, totals, taxes, status and expiry. Teamleader: quotations.info.
| Name | Type | Req | Description |
|---|---|---|---|
| quotation_id | string | yes | The quotation id (a UUID). |
No output schema declared.
No examples provided.
teamleader_get_subscription Get a subscription ~55
Fetch one subscription in full: invoicee, line items, totals, billing cycle, start and end dates and payment term. Teamleader: subscriptions.info.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | The subscription id (a UUID). |
No output schema declared.
No examples provided.
teamleader_list_activity_types List activity types ~84
List the activity types of calendar events (Teamleader has three: tasks, meetings and calls). An activity type id is REQUIRED to create a calendar event. Teamleader: activityTypes.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
No output schema declared.
No examples provided.
teamleader_list_companies List companies ~207
List or search companies (organisations). Filter by search term, primary email, VAT number, tags, status or last update. Teamleader: companies.list.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Exact primary email address. | |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| status | string | – | – |
| tags | array | – | Only companies carrying these tag names. |
| term | string | – | Search name, VAT number, emails and telephones. |
| updated_since | string | – | Only companies updated since (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
| vat_number | string | – | Exact VAT number, e.g. BE 0899.623.035. |
No output schema declared.
No examples provided.
teamleader_list_contacts List contacts ~198
List or search contacts (people). Filter by search term, primary email, linked company, tags, status or last update. Teamleader: contacts.list.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | Only contacts linked to this company id. |
| string | – | Exact primary email address. | |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| status | string | – | – |
| tags | array | – | Only contacts carrying ALL of these tags. |
| term | string | – | Search first name, last name, email and telephone. |
| updated_since | string | – | Only contacts updated since (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
No output schema declared.
No examples provided.
teamleader_list_deal_phases List deal phases ~98
List the phases (stages) of deal pipelines, in flow order, with their probability. Use a phase id when creating a deal. Teamleader: dealPhases.list.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_pipeline_id | string | – | Only phases of this pipeline. |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
No output schema declared.
No examples provided.
teamleader_list_deal_pipelines List deal pipelines ~100
List the sales pipelines; the reply's meta names the default pipeline. Use a pipeline id with teamleader_list_deal_phases. Teamleader: dealPipelines.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| status | array | – | – |
| term | string | – | Search pipeline names. |
No output schema declared.
No examples provided.
teamleader_list_deals List deals ~266
List or search deals (sales opportunities). Filter by customer, phase, pipeline, status, responsible user, expected closing date or last update. Teamleader: deals.list.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only deals for this contact/company id. |
| customer_type | string | – | With customer_id: the customer's type. |
| estimated_closing_date_from | string | – | Expected closing date from (YYYY-MM-DD). |
| estimated_closing_date_until | string | – | Expected closing date until (YYYY-MM-DD). |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| phase_id | string | – | Only deals in this phase. |
| pipeline_ids | array | – | Only deals in these pipelines. |
| responsible_user_id | string | – | Only deals this user is responsible for. |
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| status | array | – | Deal statuses. |
| term | string | – | Search term. |
| updated_since | string | – | Only deals updated since (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
No output schema declared.
No examples provided.
teamleader_list_departments List departments ~80
List the account's departments (company entities that issue invoices and quotations). A department id is needed to filter subscriptions and product categories or to create a deal for a specific entity. Teamleader: departments.list.
| Name | Type | Req | Description |
|---|---|---|---|
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| status | array | – | Filter by status. |
No output schema declared.
No examples provided.
teamleader_list_events List calendar events ~306
List calendar events (meetings, calls) in a time window. Filter by user, activity type, search term, an attending contact, a linked contact / company / deal, a task or done state. Teamleader: events.list.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type_id | string | – | The activity type id (a UUID). |
| attendee_contact_id | string | – | Only events this contact attends. |
| done | boolean | – | – |
| ends_after | string | – | Start of the period: events ending after (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
| link_id | string | – | Only events linked to this contact, company or deal. |
| link_type | string | – | With link_id: the linked record's type. |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| sort_order | string | – | Sort by start time (starts_at). |
| starts_before | string | – | End of the period: events starting before (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
| task_id | string | – | Only events planned for this task. |
| term | string | – | Search the title and description. |
| user_id | string | – | Only this user's events. |
No output schema declared.
No examples provided.
teamleader_list_invoices List invoices ~296
List or search outgoing invoices. Filter by term, invoice number, status (draft / outstanding / matched = paid), customer, deal, project, invoice date range or last update. Returns totals, due date and paid state. Teamleader: invoices.list.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only invoices for this contact/company id. |
| customer_type | string | – | With customer_id: the customer's type. |
| deal_id | string | – | The deal id (a UUID). |
| invoice_date_after | string | – | Invoice date from, inclusive (YYYY-MM-DD). |
| invoice_date_before | string | – | Invoice date until, inclusive (YYYY-MM-DD). |
| invoice_number | string | – | Full invoice number, e.g. "2026 / 5". |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| project_id | string | – | The project id (a UUID). |
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| status | array | – | – |
| term | string | – | Search invoice number, PO number, payment reference and invoicee. |
| updated_since | string | – | Only invoices updated since (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
No output schema declared.
No examples provided.
teamleader_list_notes List notes ~115
List the notes on one contact, company, deal, invoice, quotation, project and more, with their text and date. Teamleader: notes.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| subject_id | string | yes | The subject id (a UUID). |
| subject_type | string | yes | What the notes are attached to (nextgenProject = a project in the projects module). |
No output schema declared.
No examples provided.
teamleader_list_product_categories List product categories ~48
List the product categories (each one is a ledger account), optionally for one department. Teamleader: productCategories.list.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | string | – | Only categories of this department. |
No output schema declared.
No examples provided.
teamleader_list_products List products ~118
List or search products (the price list) by name or code. Teamleader: products.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| term | string | – | Search the product name or code. |
| updated_since | string | – | Only products updated since (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
No output schema declared.
No examples provided.
teamleader_list_projects List projects ~158
List projects (the projects module). Filter by term, status, customer or deal. Returns budget, time tracked, billed/unbilled amounts, dates and owners. Teamleader: projects-v2/projects.list.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only projects for this contact/company id. |
| customer_type | string | – | With customer_id: the customer's type. |
| deal_ids | array | – | Only projects linked to these deals. |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| status | string | – | – |
| term | string | – | Search project number, title, customer, assignee and owner names. |
No output schema declared.
No examples provided.
teamleader_list_quotations List quotations ~101
List quotations (offers) with their status, totals and deal. Teamleader filters quotations only by id: to find a deal's quotations, take the ids from teamleader_get_deal. Teamleader: quotations.list.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these quotations. |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
No output schema declared.
No examples provided.
teamleader_list_subscriptions List subscriptions ~185
List subscriptions (recurring invoices): title, status, customer, billing cycle and next invoice date. Filter by customer, deal, department, status or the invoice a subscription generated. Teamleader: subscriptions.list.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only this contact's or company's subscriptions. |
| customer_type | string | – | With customer_id: the customer's type. |
| deal_id | string | – | Only subscriptions created from this deal. |
| department_id | string | – | The department id (a UUID). |
| invoice_id | string | – | The subscription that generated this invoice. |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| status | array | – | – |
No output schema declared.
No examples provided.
teamleader_list_tasks List tasks ~199
List tasks (to-dos). Filter by assigned user, completed, scheduled, due date range, search term or customer. Teamleader: tasks.list.
| Name | Type | Req | Description |
|---|---|---|---|
| completed | boolean | – | – |
| customer_id | string | – | Only tasks for this contact/company id. |
| customer_type | string | – | With customer_id: the customer's type. |
| due_by | string | – | Due on or before (YYYY-MM-DD). |
| due_from | string | – | Due on or after (YYYY-MM-DD). |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| scheduled | boolean | – | – |
| sort_field | string | – | – |
| sort_order | string | – | Sort order. |
| term | string | – | Search the task description. |
| user_id | string | – | Tasks assigned to this user or one of their teams. |
No output schema declared.
No examples provided.
teamleader_list_tickets List tickets ~136
List support tickets: subject, status, assignee, customer, project and last message time. Filter by customer, project or assignee. Teamleader: tickets.list.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_ids | array | – | Only tickets assigned to one of these users. |
| customer_id | string | – | Only tickets relating to this contact/company id. |
| customer_type | string | – | With customer_id: the customer's type. |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| project_ids | array | – | – |
No output schema declared.
No examples provided.
teamleader_list_time_tracking List time tracking ~230
List tracked time entries: who, when, duration (seconds), work type, subject, invoiceable flag and hourly rate. Filter by user, start range or subject. Teamleader: timeTracking.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| sort_order | string | – | Sort by start time (starts_on). |
| started_after | string | – | Entries that started on/after (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
| started_before | string | – | Entries that started on/before (ISO 8601 with offset, e.g. 2026-01-31T00:00:00+00:00). |
| subject_id | string | – | Only entries tracked on this subject. |
| subject_type | string | – | With subject_id: the subject's type. |
| user_id | string | – | The user id (a UUID). |
No output schema declared.
No examples provided.
teamleader_list_users List users ~106
List the users (colleagues) in the Teamleader account. Use it to find a user id to assign deals or tasks to. Teamleader: users.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| status | array | – | Filter by status. |
| term | string | – | Search first name, last name, email and function. |
No output schema declared.
No examples provided.
teamleader_list_work_types List work types ~89
List work types (e.g. Design, Development), alphabetically. A work type id is REQUIRED to create a task. Teamleader: workTypes.list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Page size, 1-100 (Teamleader default 20). |
| term | string | – | Search work type names. |
No output schema declared.
No examples provided.
How do I install the Teamleader Focus MCP by usefulapi server?
Teamleader Focus MCP by usefulapi is a hosted endpoint at https://teamleader-focus.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.
remote · teamleader-focus.usefulapi.io
claude mcp add --transport http io-usefulapi-teamleader-focus 'https://teamleader-focus.usefulapi.io/mcp'
What is the Teamleader Focus MCP by usefulapi server?
Teamleader Focus MCP by usefulapi is listed in the public MCP registry as io.usefulapi/teamleader-focus. Read Teamleader Focus contacts, companies, deals, invoices, projects; create deals, tasks. This page covers its hosted endpoint (https://teamleader-focus.usefulapi.io/mcp).
Is the Teamleader Focus MCP by usefulapi server safe to use?
Teamleader Focus MCP by usefulapi scores 62 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 Teamleader Focus MCP by usefulapi server expose?
Teamleader Focus MCP by usefulapi exposes 36 tools: teamleader_get_current_user, teamleader_list_users, teamleader_list_contacts, teamleader_get_contact, teamleader_list_companies, and 31 more. Their descriptions and schemas cost roughly 4,975 tokens of context every time the server is loaded.
Does the Teamleader Focus MCP by usefulapi server require authentication?
Yes. Teamleader Focus 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 Teamleader Focus MCP by usefulapi server still maintained?
Teamleader Focus 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.