NOVA MCP connector for Kommo

MCP remoto para Kommo CRM: leads, contatos, tarefas, pipelines, chats. OAuth, sem chaves de API.

Servidor MCP hospedado

npx add-mcp 'https://sp1-nova.com/api/mcp-server/mcp/'

Instala no Claude Code, Codex, Cursor e outros

Documentação

Connects Claude, ChatGPT, Cursor, Gemini, Grok and other AI to Kommo. The AI reads and updates leads, contacts, companies, tasks and notes.

Features

Read, update and delete leads, contacts and companies

Tasks, notes, custom fields, tags and catalogs

Connect Claude, ChatGPT, Cursor, Gemini and other AI

Installation and setup guide

Detailed guide for working with widget "MCP connector for Kommo"

About the widget

The widget creates a secure MCP server so that external AI clients (Claude, ChatGPT, Cursor, Gemini and others) can securely request data from your Kommo.

Important: the connector works only while Kommo is open in a browser tab. Keep at least one Kommo tab open on any computer — otherwise requests from the AI client won't be executed.

Release connection data

In the widget settings, the profile has an MCP address. It is inserted into the AI client.

Create a profile in the widget settings. The profile will have an MCP address. It is enough: the login takes place via OAuth when the client opens this address.

MCP connector settings: server address

MCP profile address

Each profile has its own address. For Kommo it is on sp1-nova.ru, for Kommo - on sp1-nova.com. Copy it from the settings, do not assemble it manually.

Setting up the AI client

Insert the MCP address into the AI client settings and go through OAuth.

Paste the MCP address into your AI client settings. The process is slightly different depending on the service:

  • Claude: Settings → Connectors → Add custom connector. Paste the server address and leave the published identity as Claude. Give permission to access Kommo data.
  • ChatGPT: in MCP settings, create a custom MCP server and paste the address.
  • Cursor: Add the server to the mcp.json file and provide the address.
  • Gemini: Insert the address as instructed by your MCP host.

After pasting the address, the client will open authorization (OAuth) and request permission to access Kommo data. For detailed steps for different clients, see the Chats, Editors, and Agents and Automation sections below.

Access check

After authorization, check that the AI client sees the available tools (functions). The widget provides a set of actions: searching for leads and contacts, uploading statistics on pipelines, reading correspondence history, generating summaries. Make sure all the necessary tools are active.

Sometimes, after widget updates, access marks may be reset - periodically check that all tools have a permission (for example, “Always allow”).

Important nuances

  • Access mode. By default, the widget provides read-only access (search, analytics, reports). AI does not automatically perform direct recording (creating, editing, deleting records in CRM). If you need recording capabilities, enable the appropriate methods in the widget settings.
  • Safety. The profile address is issued individually. Deleting a profile revokes access.
  • Data structure. If your account uses custom fields (for example, the lead source is stored not in a standard field, but in a separate one), indicate this in the widget settings. This way the AI agent will correctly understand the structure of your data.

Frequently asked questions and solutions

  • Error during authorization. Check that the entire address has been copied and that the widget is active in Kommo.
  • AI doesn't see tools. Make sure that the widget settings for these tools are set to Always allow.
  • Data is not updated. Check the expiration date of the OAuth token—if necessary, the widget should automatically renew it.

If any difficulties arise at any stage, write to support - we will help you figure it out!

Functions

The AI calls functions itself. Lists of leads, contacts, companies, customers, and the event feed can be filtered. Lists return up to 250 records per page, 50 by default. pipelines_delete removes a pipeline, and users_create invites a user. If a function is missing, the AI adds an idea to the wishlist. A bug or an error goes through bug_report.

Lists of leads, contacts, companies, customers, and the event feed can be filtered. A lead can be filtered by name, pipeline and stage, created, closed and next-task dates, source, unsorted category, owner, creator, editor, tasks, budget, labor cost, loss reason, tags, products, conversations, main contact, company, and custom fields. A contact or company can be filtered by name, created and updated dates, pipelines of linked leads, including records without leads, owner, author, tasks, tags, and fields. A customer can also be filtered by the next purchase date and amount, status, LTV, number of purchases, and average check. An event can be filtered by date, author, type, and the value before and after. A contact phone and email are still found by the search string.

These calls do nothing without confirm true: deleting a pipeline or a stage, a regular list, an invoice, a role, a source, a chat template, a loss reason, a custom task type, a customer stage or segment, a purchase, a field group, list fields, or segment fields; deactivating a user; installing or uninstalling a widget; declining an incoming lead; restoring from trash; merging duplicates. Deleting a lead, contact, company, customer, task, note, tag, custom field, file, or webhook does not need this flag. salesbot_run and export_start do not need it either.

Leads, contacts and companies

FunctionWhat it does
leads_listLead list. Can be filtered by stage, date, owner, fields, and other list conditions
leads_getOne lead by id
leads_createCreate leads
leads_updateUpdate leads
leads_deleteDelete leads by id
leads_complex_createA lead, a contact, and a company in one call, up to 50. The contact goes in _embedded.contacts, the company in _embedded.companies
contacts_listContact list. Can be filtered by date, linked leads, owner, and fields
contacts_getOne contact by id
contacts_createCreate contacts
contacts_updateUpdate contacts
contacts_deleteDelete contacts by id
companies_listCompany list. Can be filtered by date, linked leads, owner, and fields
companies_getOne company by id
companies_createCreate companies
companies_updateUpdate companies
companies_deleteDelete companies by id

Customers

FunctionWhat it does
customers_listCustomer list. Can be filtered by purchase date, status, amount, and fields
customers_getOne customer by id
customers_createCreate customers
customers_updateUpdate customers
customers_deleteDelete customers by id
customers_enableEnable the Customers section. Mode: segments or periodicity
customer_statuses_listCustomer periodicity stages. The id is used as status_id. In segments mode there are no stages
customer_statuses_createA new customer stage: name, sort, and color from the stage palette. The API does not accept entry conditions
customer_statuses_updateName, color, and order of a customer stage. The object needs an id
customer_statuses_deleteDeletes a customer stage. Needs confirm true
customer_segments_listCustomer segments. If the section is off, call customers_enable with mode segments first
customer_segments_createA new segment: name, and optional sort and color. The API does not accept entry conditions
customer_segments_updateName, color, and order of a segment. The object needs an id. The API does not accept conditions
customer_segments_deleteDeletes a segment. Needs confirm true
customer_transactions_listPurchases of one customer. customer_id is the customer id. Up to 250 per page
customer_transactions_createA customer purchase. customer_id and items, price is required, dates are unix time
customer_transactions_deleteDeletes one purchase. Needs customer_id, id, and confirm true
segment_conditions_getA segment card. amo does not return conditions, and the tool reports that limit
segment_conditions_updateTries to save segment conditions. amo rejects the conditions field
segment_custom_fields_listCustom fields of customer segments. These are not custom fields on the customer card
segment_custom_fields_createNew custom fields for segments. This does not set segment conditions
segment_custom_fields_updateUpdates segment custom fields. Each object needs an id
segment_custom_fields_deleteDeletes segment custom fields by ids. Needs confirm true

Invoices

FunctionWhat it does
invoices_enableEnable Invoices/purchases. A second list is not created
invoices_listInvoices of a lead or customer, one page
invoices_getInvoice by id, including the payment link
invoices_createCreate an invoice and attach it to a lead or customer
invoices_updateInvoice status and lines. status is created, paid, or partially_paid. items, when sent, replace the lines entirely
invoices_deleteDeletes an invoice. Needs confirm true. This does not turn the invoices section off

Webhooks

You can attach a Grok routine to the hook address: for example, to a new incoming message (add_message) or a new lead (add_lead). Other AI providers have the same technique - routine, automation or webhook, which accept HTTP POST. amo can't add a title. webhooks_add_bearer registers a hook on sp1-nova.ru (for Kommo - sp1-nova.com), and sp1 forwards the same POST to your address with the Authorization: Bearer header. If the address already exists, amo replaces its entire events. Deleting removes the address from all events. No more than 100 hooks per account.

Events: responsible_lead, responsible_contact, responsible_company, responsible_customer, responsible_task — change of responsible person; restore_lead, restore_contact, restore_company - restoration; add_lead, add_contact, add_company, add_customer, add_talk, add_task - adding; update_lead, update_contact, update_company, update_customer, update_talk, update_task - change; delete_lead, delete_contact, delete_company, delete_customer, delete_task - deletion; status_lead — change of lead stage; note_lead, note_contact, note_company, note_customer - note; add_message - incoming message, add_outgoing_message - outgoing message, add_chat_template_review - WhatsApp template for approval. For a list: add_catalog_{id}, update_catalog_{id}, delete_catalog_{id}.

FunctionWhat it does
webhooks_listAccount webhooks. destination keeps a single URL
webhooks_addSubscribe a URL to events. An existing URL is replaced entirely
webhooks_add_bearerWebhook via sp1-nova.ru that adds Authorization: Bearer on your URL
webhooks_deleteDelete a webhook by its exact URL. A proxied hook accepts the sp1 URL or your URL

Tasks and notes

FunctionWhat it does
tasks_listTask list
tasks_getOne task by numeric id
tasks_createCreate tasks
tasks_updateUpdate tasks
tasks_deleteDelete tasks by id
task_types_listTask types, including the built-in ones
task_types_createA custom task type. color is six hex characters without a hash, default 568FFA
task_types_updateName, color, order, or icon of a custom task type. The object needs an id
task_types_deleteDeletes a custom task type. System types 1, 2, and 3 stay. Needs confirm true
notes_listNotes on leads, contacts, companies or customers. With a card id, only that card
notes_createCreate notes
notes_updateUpdate notes. Each item needs the note id and the card entity_id
notes_deleteDelete notes by id

Pipelines, stages and loss reasons

FunctionWhat it does
pipelines_listPipelines and stages
pipelines_getOne pipeline by id
pipelines_statusesStages of a pipeline
pipelines_createCreate pipelines. name, sort, is_main and is_unsorted_on are required. Stage color must be from the amo palette
pipelines_updateName, order, the main-pipeline flag, and the incoming-leads flag. is_main true makes this pipeline the main one
pipelines_deleteDeletes one pipeline. amo may refuse the main pipeline or one that still has records. Needs confirm true
pipeline_statuses_createNew pipeline stages. items take name, sort, and color from the amo stage palette. Up to 50
pipeline_statuses_updateName, color, and order of stages. System stages 142 and 143 cannot be changed this way
pipeline_statuses_deleteDeletes one stage. Stages 142, 143, and Incoming leads cannot be deleted. Needs confirm true
loss_reasons_listLoss reasons: id and name. The id is set on a lead with loss_reason_id
loss_reasons_createNew loss reasons, up to 50
loss_reasons_updateRenames one loss reason
loss_reasons_deleteDeletes one loss reason. Needs confirm true

Digital Pipeline

FunctionWhat it does
digital_pipeline_catalogDigital Pipeline trigger types: type and a short summary. The schema is in digital_pipeline_describe
digital_pipeline_describeSchema of one trigger type: parameters, which ones are required, and an example
digital_pipeline_listTriggers of one pipeline. page starts at 1, limit defaults to 50, maximum 100
digital_pipeline_getOne trigger. settings from the response can be sent to digital_pipeline_update
digital_pipeline_createOne trigger on a stage. pipeline_id, status_id, action, and settings are required
digital_pipeline_updateUpdates one trigger. settings is replaced entirely. dry_run true does not save
digital_pipeline_deleteDeletes one trigger. If the action sits on several stages, only this id is removed. dry_run true does not save

Tags and custom fields

A lead tag color in tags_create is six hex characters. A leading hash is optional. Only these 23 colors work: EBEBEB, D0D0D0, F2DDF7, D1A4DC, FF8F92, FFC8C8, C7DB8C, DDEBB5, 8699DA, AABDFF, FFCE5A, FFE193, 90CDB0, C6F4DE, A9A5D7, D8D5FF, 86C0FC, 832161, 6A0F49, 0C7C59, 10599D, 9D2B32, 247BA0. amo does not accept pipeline stage colors.

FunctionWhat it does
tags_listTags of an entity, one page. page starts at 1, up to 250. Continue while _links.next is present
tags_createA tag in the tag list. color is only for leads and only one of 23 amo tag colors, for example DDEBB5. The pipeline stage palette does not work. Put the tag on a card with tags_to_add
tags_deleteDelete tags by id
custom_fields_listCustom fields
custom_fields_createCreate custom fields
custom_fields_updateUpdate custom fields
custom_fields_deleteDelete custom fields by id
custom_field_groups_listField groups on a card. entity_type is leads, contacts, companies, or customers
custom_field_groups_createNew field groups. items take name and an optional sort
custom_field_groups_updateName and order of groups. The object needs an id
custom_field_groups_deleteDeletes one group. The custom fields stay on the card. Needs confirm true

Lists and links

links_link attaches another card to a lead, contact, company, or customer. The same call attaches a list item, including a product. For it, to_entity_type is catalog_elements, and to_entity_id is the element id from catalog_elements_list. The same list searches with query by name and filled fields. metadata needs catalog_id from catalogs_list and quantity, how many units to attach. price_id is optional. links_unlink removes this link: metadata still needs catalog_id.

FunctionWhat it does
catalogs_listLists in the account. query filters by name, ignoring letter case. Up to 250 per page. There are no other filters
catalogs_getOne list by id from catalogs_list
catalogs_createA new regular list. type is always regular. invoices_enable creates invoices, and products are already in the account
catalogs_updateThe list name. The object needs an id and name or sort. sort alone is not enough: the current name is kept. This method does not change the order
catalogs_deleteDeletes a regular list together with its elements. Invoices and products stay. Needs confirm true
catalog_elements_listCatalog elements, one page. query searches by name and filled fields. page starts at 1, up to 250. Continue while _links.next is present
catalog_elements_getOne list element. Needs catalog_id and the element id
catalog_elements_createCreate catalog elements
catalog_elements_updateUpdate catalog elements
catalog_elements_deleteDelete catalog elements
catalog_custom_fields_listCustom fields of a list, of products, or of invoices. catalog_id comes from catalogs_list. custom_fields_list does not accept a list
catalog_custom_fields_createNew custom fields for a list. catalog_id is required. items take name, type, and enums
catalog_custom_fields_updateUpdates list custom fields. Each object needs the field id
catalog_custom_fields_deleteDeletes list custom fields by ids. Needs confirm true
products_listProducts from the system list. query searches by name. Attach one to a lead with links_link. Up to 250 per page
links_listLinks of a card, one page. page starts at 1, up to 250. Continue while _links.next is present
links_linkLink records to a card. List item and product: to_entity_type catalog_elements, metadata with catalog_id and quantity
links_unlinkUnlink records. List item and product: to_entity_type catalog_elements and metadata.catalog_id
entity_subscribers_listWho follows the card. This call cannot subscribe a user

Users and roles

FunctionWhat it does
users_listAccount users
users_getOne user by id
users_createInvites users, up to 10. Needs name, email, and password: at least 6 characters, a digit, a lowercase letter, and an uppercase letter. lang is ru, en, or es. The password is not returned. confirm is not required
users_activateActivates users by ids, up to 10. Administrator and the Enterprise plan only. An administrator cannot be activated this way
users_deactivateDeactivates users by ids, up to 10. Needs confirm true. Administrator and the Enterprise plan only. An administrator cannot be deactivated this way
roles_listRoles and their rights. Administrator rights are required. Up to 250 per page
roles_getOne role by id: name and rights, including stage rights
roles_createNew roles. amo refuses a role without rights for leads, contacts, companies, and tasks. Up to 50
roles_updateUpdates roles. Each object needs an id
roles_deleteDeletes one role. Users stay in the account without that role. Needs confirm true

Events

FunctionWhat it does
events_listEvent feed: calls, stage and owner changes. Can be filtered by date, author, and type. Up to 100 per page
events_getOne event by id

Mail

FunctionWhat it does
mail_mailboxesConnected mailboxes
mail_threadsMail threads. Folders: inbox, sent, drafts, spam, trash. Up to 50
mail_messagesMessages of one thread
mail_sendSend a message from an account mailbox, without attachments. If there are no mailboxes, connect one in amo mail
mail_replyReplies in a thread. thread_id comes from mail_threads. There are no attachments. Without a mailbox, mail says the mailbox was not found
mail_connectConnects a mailbox. The password is not returned. Without a working IMAP server the mailbox is not created

Messages in a lead

FunctionWhat it does
lead_messages_listClient chat messages in a lead. The reply includes channel, for example telegram. Several chats require chat_id
lead_messages_sendSend text to the client in the chat channel, for example telegram. This is not mail and not a note

Files

FunctionWhat it does
files_listAccount files, one page. An empty drive is an empty list. page starts at 1, up to 250
files_uploadUpload a file, up to 100 MB. Can be linked to a lead, contact, company or customer
files_deleteDelete a file by uuid

Bots

FunctionWhat it does
salesbot_catalogSalesbot step types. salesbot_describe returns the schema
salesbot_describeSchema of one Salesbot step: parameters, which ones are required, and an example
bots_listBot list: id, name and type. Needed to run a bot
bots_getOne bot with its scenario. On Kommo an open tab with the NOVA MCP widget reads the scenario. Without that tab the response has no scenario
bots_createA new bot is created switched off. name and scenario are required. active true is not accepted
bots_updateName, active, and other bot fields. The whole scenario is replaced only with replace_scenario true
bots_deleteDeletes a bot by id. A read-only bot is not deleted. dry_run true does not delete it
salesbot_step_addOne new step. handler comes from salesbot_catalog. dry_run true does not save
salesbot_step_updateReplaces one step by its step number. dry_run true does not save
salesbot_step_deleteDeletes one step. The other step numbers stay. dry_run true does not delete it
salesbot_runRun a bot. Take bot_id from the bot list

Statistics

FunctionWhat it does
stats_consolidated_getThe summary report: total count, sum, and open stages
stats_pipeline_getSales analysis: pipelines and stage names. Stage numbers come from the summary report
stats_employees_getThe report by user. If the columns have no numbers, the response states that limit
stats_calls_getThe calls dashboard. This is not calls_add and not call notes. Up to 50 rows
stats_customers_getThe customers report. If the section is missing, amo returns an empty placeholder
stats_goals_getGoals for leads. If the plan has no goals, the tool reports that limit

Import, export, trash and duplicates

FunctionWhat it does
import_listThe import queue in the amo interface
export_startExports leads, contacts, or companies to csv or xlsx. Returns the job uuid, not the file. confirm is not required
export_status_getExport status and a link to the file inside the account. The file is not downloaded outside
trash_listTrash: only deleted leads, contacts, or companies. entity is leads, contacts, or companies. Live cards are not included
trash_restoreRestores cards from trash. Companies use the same route as contacts. Needs confirm true
duplicates_mergeMerges two leads, contacts, or companies. master_id stays, duplicate_id is absorbed. Needs confirm true

Incoming leads and conversations

FunctionWhat it does
unsorted_listIncoming leads. pipeline_id keeps one pipeline. uid is needed to accept, decline, or link. Up to 250 per page
unsorted_getOne incoming lead by uid from unsorted_list
unsorted_acceptAccepts an incoming lead into a stage. Needs user_id and status_id
unsorted_declineDeclines an incoming lead. Needs confirm true and user_id
unsorted_linkLinks an incoming lead to a lead or a customer. entity_type is leads or customers
unsorted_createCreates an incoming lead from a call or a form. kind is sip or form. This method does not create chat or mail
talks_listAccount conversations. This is not the lead chat: lead_messages_list returns that history. Up to 250 per page
talks_getOne conversation by id from talks_list
talks_closeCloses a conversation. force_close true closes it even when the customer message has no reply

Account, widgets, sources and calls

FunctionWhat it does
account_getAccount settings, read only: name, country, customers mode, time zone, task types, and chat rights
widgets_listWidgets. is_active_in_account true returns those installed in the account. Passwords in the response are hidden
widgets_getA widget by code. settings_template shows the fields needed to install it. Passwords are hidden
widgets_installInstalls a widget. settings are the fields from settings_template. Needs confirm true
widgets_uninstallUninstalls a widget. Its settings are removed. Needs confirm true
sources_listSources of this integration. Other lead sources are not included. Up to 250 per page
sources_getOne integration source by id
sources_createA new integration source. items take name, external_id, pipeline_id, and default
sources_updateUpdates an integration source. The object needs an id
sources_deleteDeletes an integration source. Needs confirm true
calls_addAdds a call to a card by phone number. direction is inbound or outbound. uniq is the call id, duration is seconds. This is not the calls dashboard
chat_templates_listChat templates of this integration. Other templates are not included. Administrator rights are required
chat_templates_createA new chat template for the integration. items take name, content, and external_id
chat_templates_updateUpdates a chat template. The object needs an id
chat_templates_deleteDeletes a chat template. Needs confirm true
short_links_createA short amo link to a url. entity_id is the contact id. Without a contact, amo rejects the link

Notifications

FunctionWhat it does
inbox_notifyNotification in the bell. Type: error or call

Wishlist

FunctionWhat it does
wishlist_listIdeas for the MCP connector. Search by text, filter by status
wishlist_addA new idea when the function does not exist. The text is moderated
wishlist_voteA vote for an existing idea. One account, one vote
bug_reportA widget bug or error: link, steps, expected and actual result

Chats

The MCP address is taken from the widget settings. Next, the client opens the OAuth login.

Claude

  1. Open claude.ai and go to Customize → Connectors.
  2. Click Add custom connector.
  3. Paste the MCP address from the widget settings.
  4. Confirm your login when the login window opens.
  5. On Free you can connect one connector. Claude Code with the same account will pick it up himself.

ChatGPT

  1. Open chatgpt.com/plugins.
  2. Click Add, then Create custom MCP server. On some accounts the button is also called Create MCP App.
  3. This is your connection. There is no need to publish the application to the market.
  4. Paste the MCP address from the widget settings.
  5. Confirm access to Kommo.
  6. Reading available on Plus, Pro, Business, Enterprise and Edu. Recording in Kommo - for Business, Enterprise and Edu.

Gemini

  1. Open gemini.google.com → Connected Apps → Custom apps.
  2. Add your server.
  3. Paste the MCP address from the widget settings.
  4. Confirm your entry.
  5. You need a personal Google account in the USA, over 18 years of age and an English interface.

Grok

  1. Open grok.com/connectors and select Custom.
  2. Paste the MCP address from the widget settings.
  3. Confirm your entry.
  4. Available on all plans. An administrator adds a connector to a team.

Perplexity

  1. Open Connectors → Custom connector and select Remote.
  2. Paste the MCP address from the widget settings.
  3. Confirm your entry.
  4. You need a Pro, Max or Enterprise plan.

Mistral

  1. In Mistral Work, open Connectors → Add Connector.
  2. Paste the MCP address from the widget settings.
  3. The server is added by the account administrator.
  4. Confirm your entry.

Cursor

  1. Open Customize → MCPs or add the server to the mcp.json file.
  2. Specify the MCP address from the widget settings.
  3. When you connect for the first time, Cursor will open an input. Confirm it.

VS Code

  1. Run the MCP:Add Server command.
  2. Specify the remote server: MCP address from the widget settings.
  3. Login via OAuth takes place in Local harness.
  4. Tools appear in agent mode.

JetBrains

  1. Open Junie → Authorize or MCP Settings.
  2. Paste the MCP address from the widget settings.
  3. Confirm your entry.
  4. AI Assistant does not have OAuth login; it will not connect to this server.

Zed

  1. Open Settings → AI → MCP Servers and add Remote.
  2. Paste the MCP address from the widget settings.
  3. Click Authenticate and confirm your login.

Windsurf

  1. In Devin, add the server to mcp_config.json or with the devin mcp add command.
  2. Specify the MCP address from the widget settings.
  3. When you launch it for the first time, the login will open. Confirm it.

Cline

  1. Open MCP Servers → Remote Servers.
  2. Server type select streamableHttp.
  3. Paste the MCP address from the widget settings.
  4. Confirm your entry.

Agents and automation

MCP address from widget settings. Transport - Streamable HTTP.

Claude Code

  1. Run claude mcp add and specify the MCP address, or use the connector already added to claude.ai.
  2. Confirm your entry.
  3. The connector from the site is picked up if the login is not via an API key.

Codex

  1. Run codex mcp add.
  2. Specify the MCP address from the widget settings.
  3. Confirm your login upon first launch.
  4. One config works in the CLI, in the editor extension and in the ChatGPT application.

Gemini CLI

  1. Run gemini mcp add.
  2. Specify the MCP address from the widget settings.
  3. Confirm your entry.
  4. A regular Google account is not suitable: you need Code Assist or an API key.

Qwen Code

  1. Open settings.json.
  2. Write the MCP address into the httpUrl key. The url key means old SSE and will not work here.
  3. Confirm your entry.

OpenCode

  1. Open opencode.json.
  2. Add a server with a type field and a remote value. Without type, the server will not boot.
  3. Paste the MCP address from the widget settings.
  4. Confirm your entry.

Kiro

  1. Add the server to mcp.json: MCP address from widget settings.
  2. Confirm your entry.
  3. There is no MCP in the mobile application.

GitHub Copilot CLI

  1. In chat, run the /mcp add command.
  2. Specify the MCP address from the widget settings.
  3. This is a user config, not a repository file.
  4. Confirm your entry.

Warp

  1. Open Settings → Agents → MCP servers.
  2. Add server: MCP address from widget settings.
  3. Confirm your entry.
  4. The cloud agent does not pass this OAuth. Connect a local agent.

Goose

  1. Open Extensions → Add custom extension and select Remote.
  2. Specify the type streamable_http.
  3. Paste the MCP address from the widget settings.
  4. Confirm your entry.

LM Studio

  1. Open Program → mcp.json.
  2. Add remote server: MCP address from widget settings.
  3. Choose a model that can call tools.
  4. Confirm your login on the first call.

Raycast

  1. Run the Install MCP Server command.
  2. Paste the MCP address from the widget settings.
  3. Confirm your entry.
  4. You need a Pro, Pro+ or Max plan.

Copilot Studio

  1. In the agent, open Tools → Model Context Protocol.
  2. In the wizard, specify the MCP address.
  3. Author's license required. Confirm your entry.

n8n

  1. Add an MCP Client node to the AI agent.
  2. Transport select Streamable HTTP, authorization – OAuth2.
  3. Paste the MCP address from the widget settings.
  4. Pass OAuth2 login.

Open WebUI

  1. The administrator opens Admin → Integrations → External Tool Servers.
  2. Adds server: MCP address from widget settings.
  3. Login takes place separately for each user.