namakan-mcp-crm
Provides CRM integration with HubSpot as a backend, allowing AI agents to search contacts and accounts, list and retrieve deals, create deals, and log activities through unified MCP tools.
Provides CRM integration with Salesforce as a backend, allowing AI agents to search contacts and accounts, list and retrieve deals, create deals, and log activities through unified MCP tools.
Provides CRM integration with Zoho as a backend, allowing AI agents to search contacts and accounts, list and retrieve deals, create deals, and log activities through unified MCP tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@namakan-mcp-crmfind contact named Alex"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
namakan-mcp-crm
Internal MCP server: one CRM tool surface for Namakan agents. They call crm_find_contact whether the plant runs HubSpot, Salesforce, Dynamics, Pipedrive, or Zoho.
The client never configures MCP. integration-engineer (and delivery-manager, solution-architect, data-engineer, agent-systems-engineer) get this server from bootstrap. Writes stay off until ciso approves.
How agents connect
mcp_servers:
namakan-mcp-crm:
command: uvx
args:
- --from
- git+https://github.com/cfollette18/namakan-mcp-crm.git
- namakan-mcp-crm
- serve
env:
NAMAKAN_CRM_BACKEND: mock
trust: fullSwap NAMAKAN_CRM_BACKEND per engagement in clients/<slug>/ config — never by teaching the agent a vendor API.
Related MCP server: Bitrix24 MCP Server
Architecture
Full AI workflow
Playbook path (playbooks/phase-2-erp-crm-automation.md):
integration-engineeris assigned the connector card.Agent calls
crm_run_workflow(or the individualcrm_*tools).The last step is a blocked write. That is the demo, not a failure.
Production writes require
NAMAKAN_MCP_ALLOW_WRITES=1, dry-run, andciso.
Demo without an agent process:
namakan-mcp-crm workflowExpected: four JSON steps. Last step "error": "writes_disabled".
Tools
Tool | Read/write | Arguments |
| read |
|
| read |
|
| read |
|
| read |
|
| write |
|
| write |
|
| read + blocked write |
|
Potential use cases
Use case | Which agent | Why it matters |
Who owns this account? |
| Same tool on HubSpot today and Salesforce after a migration. |
Open Phase 2 pipeline |
| Mock data ships; no token needed to rehearse the call. |
Log the plant visit |
| Stays blocked until writes are enabled and |
use_case: who-owns-account (default), open-pipeline, log-plant-visit.
Tests
pip install -e ".[dev]"
pytestLicense
MIT. Copyright (c) 2026 Namakan AI Engineering.
This server cannot be deployed
Maintenance
Related MCP Connectors
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
A CRM powered by your agent: contacts, deals, email, ads, and reports over MCP.
Let AI agents query data and act across all your business apps via MCP.
AI agent platform: manage leads, conversations, bots, calendar and CRM via MCP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform CRM operations like creating contacts, managing deals, and updating leads through natural language using the Model Context Protocol.4-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Bitrix24 CRM through standardized MCP tools, including searching and managing contacts, deals, leads, tasks, and replying in chats.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage CRM data including companies, contacts, prospects, pipelines, forecasts, and tasks via typed MCP tools, with local SQLite storage and a JSON CLI.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP-native CRM backend for AI agents, enabling customer, opportunity, note, follow-up, and pipeline health management through 15 MCP tools.-