Name: Insightly
Author: usefulapi

Insightly MCP

Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.

not scanned Remote · Streamable HTTP No auth needed 21 tools v1.11.1

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

tools declared

—

trust score

remote

at its publisher

—

calls last 7d

What it does

Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http insightly-mcp https://insightly.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   insightly_get_current_user, insightly_list_users, insightly_list_records and 18 more

Insightly costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

usefulapi334 servers

24 categories

All 334 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Fetch the user the API key belongs to (USER_ID, name, email, admin flag). A cheap way to confirm the key and pod are right, and to get your own id for owner fields. Insightly: GET /Users/Me.

No parameter schema on file.

List the users in the Insightly instance — needed to resolve OWNER_USER_ID / RESPONSIBLE_USER_ID. Insightly: GET /Users.

Parameter	Type	Required	Notes
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.
count_total	boolean	no	true = also return the total number of matching records (response becomes {total_count, items}).

List records of one type — Contacts, Organisations, Leads, Opportunities, Projects, Tasks, Events or Notes — optionally filtered by one field value and/or last-updated time. With field_name + field_value (both required together) or updated_after_utc this uses GET /<Object>/Search; otherwise GET /<Object>. Field names are Insightly's UPPER_SNAKE names, e.g. EMAIL_ADDRESS, LAST_NAME, ORGANISATION_NA

Parameter	Type	Required	Notes
object	string	yes	Record type.
field_name	string	no	Field to filter on, e.g. EMAIL_ADDRESS.
field_value	string	no	Value the field must equal.
updated_after_utc	string	no	Only records updated after this time, yyyy-mm-ddThh:mm:ssZ (e.g. 2026-04-09T16:58:14Z).
brief	boolean	no	true = only top-level fields (no CUSTOMFIELDS, TAGS, LINKS, ...). Smaller and faster.
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.
count_total	boolean	no	true = also return the total number of matching records (response becomes {total_count, items}).

Fetch a single Contact, Organisation, Lead, Opportunity, Project, Task, Event or Note by id, with its custom fields, tags and links. Insightly: GET /<Object>/{id}.

Parameter	Type	Required	Notes
object	string	yes	Record type.
id	integer	yes	The record's numeric id.

List the Notes, Tasks or Events attached to one Contact, Organisation, Lead, Opportunity or Project — the activity history of that record. Insightly: GET /<Object>/{id}/Notes | Tasks | Events.

Parameter	Type	Required	Notes
object	string	yes	The parent record's type.
id	integer	yes	The parent record's numeric id.
kind	string	yes	Which activity to list.
updated_after_utc	string	no	Only items updated after this time, yyyy-mm-ddThh:mm:ssZ.
brief	boolean	no	true = only top-level fields (no CUSTOMFIELDS, TAGS, LINKS, ...). Smaller and faster.
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.
count_total	boolean	no	true = also return the total number of matching records (response becomes {total_count, items}).

List Contacts, Organisations, Leads, Opportunities or Projects carrying a tag. Insightly: GET /<Object>/SearchByTag?tagName=.

Parameter	Type	Required	Notes
object	string	yes	Record type.
tag	string	yes	The tag name.
brief	boolean	no	true = only top-level fields (no CUSTOMFIELDS, TAGS, LINKS, ...). Smaller and faster.
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.
count_total	boolean	no	true = also return the total number of matching records (response becomes {total_count, items}).

List the sales and project pipelines (PIPELINE_ID, name, whether for opportunities or projects). Insightly: GET /Pipelines.

Parameter	Type	Required	Notes
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.

List every pipeline stage (STAGE_ID, PIPELINE_ID, name, order) — map an opportunity's or project's STAGE_ID to a stage name. Insightly: GET /PipelineStages.

Parameter	Type	Required	Notes
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.

List the lead statuses defined in the instance (LEAD_STATUS_ID, name, type). Insightly: GET /LeadStatuses.

Parameter	Type	Required	Notes
include_converted	boolean	no	Also include statuses used for converted leads.
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.

List the lead sources defined in the instance (LEAD_SOURCE_ID, name). Insightly: GET /LeadSources.

Parameter	Type	Required	Notes
top	integer	no	Max records to return, 1-500 (API default 100).
skip	integer	no	Records to skip, for paging.

Create a contact (first_name is required). Insightly: POST /Contacts.

Parameter	Type	Required	Notes
salutation	string	no	e.g. Mr, Ms, Dr.
first_name	string	yes	First name (required).
last_name	string	no	Last name.
title	string	no	Job title.
email_address	string	no	Primary email.
phone	string	no	Business phone.
phone_mobile	string	no	Mobile phone.
organisation_id	integer	no	Id of the contact's organisation.
owner_user_id	integer	no	Owning user's id.
background	string	no	Background / description text.
address_mail_street	string	no	—
address_mail_city	string	no	—
address_mail_state	string	no	—
address_mail_postcode	string	no	—
address_mail_country	string	no	—
social_linkedin	string	no	LinkedIn URL.
email_opted_out	boolean	no	Opted out of email.
custom_fields	array	no	Custom field values to set.

Update a contact. Only the fields you pass are changed (v3.1 partial update). Insightly: PUT /Contacts with CONTACT_ID.

Parameter	Type	Required	Notes
contact_id	integer	yes	The contact's numeric id.
salutation	string	no	e.g. Mr, Ms, Dr.
first_name	string	no	First name.
last_name	string	no	Last name.
title	string	no	Job title.
email_address	string	no	Primary email.
phone	string	no	Business phone.
phone_mobile	string	no	Mobile phone.
organisation_id	integer	no	Id of the contact's organisation.
owner_user_id	integer	no	Owning user's id.
background	string	no	Background / description text.
address_mail_street	string	no	—
address_mail_city	string	no	—
address_mail_state	string	no	—
address_mail_postcode	string	no	—
address_mail_country	string	no	—
social_linkedin	string	no	LinkedIn URL.
email_opted_out	boolean	no	Opted out of email.
custom_fields	array	no	Custom field values to set.

Create an organisation (company). Insightly: POST /Organisations.

Parameter	Type	Required	Notes
organisation_name	string	yes	Organisation name (required).
website	string	no	—
phone	string	no	—
background	string	no	Background / description text.
owner_user_id	integer	no	Owning user's id.
address_billing_street	string	no	—
address_billing_city	string	no	—
address_billing_state	string	no	—
address_billing_postcode	string	no	—
address_billing_country	string	no	—
social_linkedin	string	no	LinkedIn URL.
custom_fields	array	no	Custom field values to set.

Update an organisation. Only the fields you pass are changed. Insightly: PUT /Organisations with ORGANISATION_ID.

Parameter	Type	Required	Notes
organisation_id	integer	yes	The organisation's numeric id.
organisation_name	string	no	Organisation name.
website	string	no	—
phone	string	no	—
background	string	no	Background / description text.
owner_user_id	integer	no	Owning user's id.
address_billing_street	string	no	—
address_billing_city	string	no	—
address_billing_state	string	no	—
address_billing_postcode	string	no	—
address_billing_country	string	no	—
social_linkedin	string	no	LinkedIn URL.
custom_fields	array	no	Custom field values to set.

Create a lead (last_name is required). Insightly's schema also marks lead_status_id and lead_source_id as required — get valid ids from insightly_list_lead_statuses / insightly_list_lead_sources. Insightly: POST /Leads.

Parameter	Type	Required	Notes
salutation	string	no	—
first_name	string	no	—
last_name	string	yes	Last name (required).
title	string	no	Job title.
email	string	no	Email address.
phone	string	no	—
mobile	string	no	—
organisation_name	string	no	Company name (free text — leads are not linked to organisations).
industry	string	no	—
website	string	no	—
employee_count	integer	no	—
lead_rating	integer	no	Rating, e.g. 1-5.
lead_description	string	no	Description / notes on the lead.
lead_status_id	integer	no	Status id — see insightly_list_lead_statuses.
lead_source_id	integer	no	Source id — see insightly_list_lead_sources.
owner_user_id	integer	no	—
responsible_user_id	integer	no	—
address_street	string	no	—
address_city	string	no	—
address_state	string	no	—

Update a lead. Only the fields you pass are changed. Insightly: PUT /Leads with LEAD_ID.

Parameter	Type	Required	Notes
lead_id	integer	yes	The lead's numeric id.
salutation	string	no	—
first_name	string	no	—
last_name	string	no	Last name.
title	string	no	Job title.
email	string	no	Email address.
phone	string	no	—
mobile	string	no	—
organisation_name	string	no	Company name (free text — leads are not linked to organisations).
industry	string	no	—
website	string	no	—
employee_count	integer	no	—
lead_rating	integer	no	Rating, e.g. 1-5.
lead_description	string	no	Description / notes on the lead.
lead_status_id	integer	no	Status id — see insightly_list_lead_statuses.
lead_source_id	integer	no	Source id — see insightly_list_lead_sources.
owner_user_id	integer	no	—
responsible_user_id	integer	no	—
address_street	string	no	—
address_city	string	no	—

Create a sales opportunity (opportunity_name is required). Insightly: POST /Opportunities.

Parameter	Type	Required	Notes
opportunity_name	string	yes	Opportunity name (required).
opportunity_details	string	no	Description.
organisation_id	integer	no	Id of the linked organisation.
bid_amount	number	no	Bid value.
bid_currency	string	no	ISO currency code, e.g. USD.
bid_type	string	no	BID_TYPE — how the bid is priced, using a value your Insightly instance accepts.
bid_duration	integer	no	Number of bid periods (for non-fixed bid types).
probability	integer	no	Win probability, 0-100.
forecast_close_date	string	no	Forecast close date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00).
category_id	integer	no	Opportunity category id.
owner_user_id	integer	no	—
responsible_user_id	integer	no	—
custom_fields	array	no	Custom field values to set.

Update an opportunity's value, probability, dates, owner or details. Only the fields you pass are changed. Insightly: PUT /Opportunities with OPPORTUNITY_ID.

Parameter	Type	Required	Notes
opportunity_id	integer	yes	The opportunity's numeric id.
opportunity_name	string	no	Opportunity name.
opportunity_details	string	no	Description.
organisation_id	integer	no	Id of the linked organisation.
bid_amount	number	no	Bid value.
bid_currency	string	no	ISO currency code, e.g. USD.
bid_type	string	no	BID_TYPE — how the bid is priced, using a value your Insightly instance accepts.
bid_duration	integer	no	Number of bid periods (for non-fixed bid types).
probability	integer	no	Win probability, 0-100.
forecast_close_date	string	no	Forecast close date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00).
category_id	integer	no	Opportunity category id.
owner_user_id	integer	no	—
responsible_user_id	integer	no	—
custom_fields	array	no	Custom field values to set.

Create a task (title is required). Insightly requires OWNER_USER_ID and COMPLETED on a task: if owner_user_id is omitted it is filled with the API key's own user (via GET /Users/Me), and completed defaults to false. Insightly: POST /Tasks.

Parameter	Type	Required	Notes
title	string	yes	Task title (required).
details	string	no	Task description.
due_date	string	no	Due date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00).
start_date	string	no	Start date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00).
status	string	no	Task STATUS text, using a value your Insightly instance accepts (read an existing task to see them).
priority	integer	no	Priority number.
percent_complete	integer	no	—
completed	boolean	no	Whether the task is done.
category_id	integer	no	Task category id.
responsible_user_id	integer	no	Assignee's user id.
owner_user_id	integer	no	Owner's user id.
project_id	integer	no	Link the task to this project.
opportunity_id	integer	no	Link the task to this opportunity.
custom_fields	array	no	Custom field values to set.

Update a task — mark it completed, change due date, status, assignee or details. Only the fields you pass are changed. Insightly: PUT /Tasks with TASK_ID.

Parameter	Type	Required	Notes
task_id	integer	yes	The task's numeric id.
title	string	no	Task title.
details	string	no	Task description.
due_date	string	no	Due date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00).
start_date	string	no	Start date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00).
status	string	no	Task STATUS text, using a value your Insightly instance accepts (read an existing task to see them).
priority	integer	no	Priority number.
percent_complete	integer	no	—
completed	boolean	no	Whether the task is done.
category_id	integer	no	Task category id.
responsible_user_id	integer	no	Assignee's user id.
owner_user_id	integer	no	Owner's user id.
project_id	integer	no	Link the task to this project.
opportunity_id	integer	no	Link the task to this opportunity.
custom_fields	array	no	Custom field values to set.

Add a note (title + body) to a Contact, Organisation, Lead, Opportunity or Project. Insightly: POST /<Object>/{id}/Notes.

Parameter	Type	Required	Notes
object	string	yes	The record type to attach the note to.
id	integer	yes	The record's numeric id.
title	string	yes	Note title (required).
body	string	no	Note body (may contain HTML).

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Insightly or to call it, at any volume.

Where are you running it?

Tool surface

Release history

Insightly MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

Release history

See also