amocrm

This AmoCRM MCP Server provides a minimal integration with amoCRM API v4, exposing tools to manage leads, contacts and notes, and to perform OAuth2 token exchanges. The server supports multiple transport styles (STDIO for local development, HTTP for external access, and Streamable HTTP for SSE-based clients). Available tools include: amocrm.listLeads, amocrm.createLead, amocrm.getContact, amocrm.listContacts, amocrm.createContact, amocrm.createNote, and amocrm.exchangeAuthCode. You can test and invoke these tools via the MCP client integrations or via the provided test scripts and inspector, which helps you verify endpoints, arguments and responses. To get started, configure your environment with your AmoCRM credentials, start the server, and use either the HTTP or Streamable HTTP transport to interact with amoCRM data, including creating and listing leads and contacts, or adding notes to entities.

Prerequisites:

• Node.js >= 18.17
• npm (comes with Node.js) or pnpm/yarn if you prefer
• Access to an AmoCRM account with client_id, client_secret and redirect_uri

1. Install dependencies

npm install

2. Create environment file

• In the project root, create a .env file and populate AmoCRM credentials as described in the README, e.g.:

AMO_BASE_URL=https://example.amocrm.ru
AMO_CLIENT_ID=<client_id>
AMO_CLIENT_SECRET=<client_secret>
AMO_REDIRECT_URI=https://your.app/oauth/callback
AMO_ACCESS_TOKEN=
AMO_REFRESH_TOKEN=
AMO_LONG_TERM_TOKEN=
MCP_AUTH_TOKEN=your-secure-token (optional)

3. Start the server

• For development using STDIO transport:

npm run dev

• For HTTP transport (external access):

npm run dev:http

• Build and run production (if applicable):

npm run build
npm run start

4. Validate installation

• If using the Inspector:

npm run build
npx @modelcontextprotocol/inspector node dist/index.js

• Or connect via Claude Desktop using the provided amocrm configuration example in the README.

5. Optional: testing and tokens

• Exchange an authorization code using amocrm.exchangeAuthCode and save tokens in .env as described in the README.
• After initial token exchange, the server will automatically refresh access tokens using the refresh token.

Tips and common considerations:

• Security: If you expose HTTP or SSE endpoints, consider setting MCP_AUTH_TOKEN to protect endpoints from unauthorized access.
• Long-term tokens are recommended for simpler maintenance; store them securely and rotate as needed.
• Ensure AMO_BASE_URL matches your AmoCRM domain (e.g., https://example.amocrm.ru).
• The README provides example configurations for Claude Desktop integration; adapt the node command and path to your built server index.js as needed.
• When testing with the inspector, you can explore available tools and their arguments to tailor calls to your AmoCRM data model (leads, contacts, notes, etc.).