Insightly MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 文档、表格与办公

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://insightly.usefulapi.io/mcp

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

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

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

https://insightly.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• insightly_get_current_user

  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.

• insightly_list_users

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

• insightly_list_records

  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 / /Search; other

• insightly_get_record

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

• insightly_list_record_activity

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

• insightly_search_by_tag

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

• insightly_list_pipelines

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

• insightly_list_pipeline_stages

  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.

• insightly_list_lead_statuses

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

• insightly_list_lead_sources

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

• insightly_create_contact

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

• insightly_update_contact

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

• insightly_create_organisation

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

• insightly_update_organisation

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

• insightly_create_lead

  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.

• insightly_update_lead

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

• insightly_create_opportunity

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

• insightly_update_opportunity

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

• insightly_create_task

  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.

• insightly_update_task

  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.

• insightly_add_note

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 12 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 21 个工具描述，未发现针对 AI 的隐藏指令

与“文档、表格与办公”中的其他服务器比较i

• 星标数多于此分类中其他 2174 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 2174 个服务器的 98% 更新
• 基础检查结果等于或优于此分类中其他 2174 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{