NOVA amoCRM / Kommo

ru.nova-amocrmPublished by nova-amocrm.ruv1.0.0Updated Nov 1, 2026

Remote MCP for amoCRM and Kommo: leads, contacts, tasks, pipelines, chats, Salesbot. OAuth.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for amoCRM and Kommo that lets an assistant work with leads, contacts, tasks, pipelines, chats and Salesbot via OAuth.

What you can do
  • Work with leads and contacts in amoCRM/Kommo
  • Manage tasks and sales pipelines
  • Access chats and Salesbot scenarios
  • Connect through a remote OAuth-authenticated endpoint
When to use it
Useful when a team runs its sales and customer pipeline in amoCRM or Kommo and wants an assistant to read or act on that CRM data directly, instead of copying records by hand.
Requirements
A remote MCP endpoint (streamable HTTP) at the provider's host; no local package or runtime is needed. OAuth authentication is required, so an amoCRM/Kommo account with permission to authorize the integration is needed. No environment variables or headers are declared.
Before you install
The server works on live CRM records such as leads, contacts, tasks and chats, so assistant actions may change or send data in your account. Access is granted through OAuth to your amoCRM/Kommo account; review the scopes requested and the provider's handling of your customer data before connecting. No tool list is published, so the exact read and write capabilities are not documented here.

Installation

In SourceWeft

  1. Open NOVA amoCRM / Kommo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ru.nova-amocrm%2Famocrm/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nova-amocrm-kommo": {
      "type": "http",
      "url": "https://sp1-nova.ru/api/mcp-server/mcp/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.