{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_aminetwiti-mcpgrowcrm1","slug":"aminetwiti-mcpgrowcrm1","name":"mcpgrowcrm1","type":"mcp","url":"https://github.com/Aminetwiti/mcpgrowcrm","page_url":"https://unfragile.ai/aminetwiti-mcpgrowcrm1","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:Aminetwiti/mcpgrowcrm1"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_aminetwiti-mcpgrowcrm1__cap_0","uri":"capability://tool.use.integration.crm.data.synchronization.via.mcp.protocol","name":"crm data synchronization via mcp protocol","description":"Exposes CRM operations (contacts, deals, activities) through the Model Context Protocol, allowing Claude and other MCP-compatible clients to read and write CRM data by translating natural language requests into structured API calls. Implements MCP's resource and tool abstractions to map CRM entities to discoverable, type-safe endpoints that clients can introspect and invoke.","intents":["I want Claude to query my CRM data and summarize pipeline status without leaving the chat","I need to automate CRM updates triggered by Claude's analysis of customer interactions","I want to build an AI agent that can create leads and update deal stages based on email content"],"best_for":["Sales teams integrating Claude with their CRM workflow","Developers building AI agents that need bidirectional CRM access","Non-technical users wanting Claude to manage CRM tasks via natural language"],"limitations":["Requires MCP client support — not all CRM tools or AI interfaces expose MCP yet","No built-in authentication abstraction — must handle CRM API credentials securely at server level","Limited to CRM operations exposed by the server implementation — custom fields or non-standard objects may not be supported","Synchronization is request-response only — no real-time event streaming or webhook support"],"requires":["MCP-compatible client (Claude Desktop, Cline, or custom MCP host)","CRM API credentials (GrowCRM or compatible system)","Node.js runtime for MCP server execution","Network connectivity between MCP server and CRM API"],"input_types":["natural language queries from MCP client","structured tool invocation parameters (contact IDs, deal stages, activity types)"],"output_types":["structured JSON responses (contact records, deal pipelines, activity logs)","confirmation messages for write operations","error responses with diagnostic context"],"categories":["tool-use-integration","mcp-servers"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aminetwiti-mcpgrowcrm1__cap_1","uri":"capability://tool.use.integration.contact.and.lead.management.via.natural.language","name":"contact and lead management via natural language","description":"Enables Claude to create, retrieve, update, and search contacts/leads in the CRM by translating conversational requests into structured contact operations. Implements MCP tools that map contact fields (name, email, phone, company, tags) to callable functions, with built-in validation and error handling for malformed or incomplete contact data.","intents":["I want Claude to create a new lead from an email signature or LinkedIn profile","I need Claude to find all contacts matching a company name or industry tag","I want to update contact details (phone, email, company) based on a conversation with the customer"],"best_for":["Sales development reps using Claude to manage lead intake","Customer success teams automating contact updates from support interactions","Developers building lead enrichment agents"],"limitations":["No bulk import/export — operations are single-contact or filtered-list only","Field validation is server-side only — no client-side schema hints for complex custom fields","Search is limited to exact match or simple filters — no full-text search or fuzzy matching","No deduplication logic — creating duplicate contacts requires manual cleanup"],"requires":["MCP server running with CRM API credentials","Contact schema defined in CRM (standard fields: name, email, phone, company, tags)","MCP client with tool-calling capability"],"input_types":["natural language descriptions of contacts","structured contact field values (email, phone, company name)","filter parameters (company, tag, date range)"],"output_types":["contact records (JSON with id, name, email, phone, company, tags, created_at)","contact lists with pagination metadata","operation confirmations (created, updated, deleted)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aminetwiti-mcpgrowcrm1__cap_2","uri":"capability://tool.use.integration.deal.and.pipeline.stage.management","name":"deal and pipeline stage management","description":"Allows Claude to view, create, and advance deals through CRM pipeline stages by exposing deal operations as MCP tools. Implements stage transitions with validation (e.g., preventing moves to invalid stages) and supports deal metadata (amount, close date, probability) to enable Claude to reason about pipeline health and forecast revenue.","intents":["I want Claude to move a deal to the next stage based on a customer email or call summary","I need Claude to create a new deal with estimated close date and amount","I want Claude to analyze my pipeline and flag deals at risk of slipping"],"best_for":["Sales managers using Claude to manage pipeline updates in real-time","Revenue operations teams automating deal stage transitions","Developers building sales forecasting agents"],"limitations":["No support for custom deal fields beyond standard metadata (amount, close_date, probability, stage)","Stage transitions are not validated against CRM workflow rules — invalid moves may succeed silently","No historical tracking of stage changes — audit trail requires external logging","Deal probability is read-only — cannot be updated via MCP tools"],"requires":["MCP server with CRM API credentials","Deal schema and pipeline stages defined in CRM","Contact/account context for deal creation (foreign key relationships)"],"input_types":["natural language deal descriptions and stage transitions","structured deal parameters (contact_id, amount, close_date, stage)","filter parameters (stage, owner, date range)"],"output_types":["deal records (JSON with id, contact_id, amount, close_date, stage, probability, created_at)","deal lists grouped by stage","pipeline summary (total value by stage, deal count)"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aminetwiti-mcpgrowcrm1__cap_3","uri":"capability://tool.use.integration.activity.logging.and.timeline.management","name":"activity logging and timeline management","description":"Enables Claude to log activities (calls, emails, meetings, notes) against contacts and deals, creating an audit trail and timeline of customer interactions. Implements MCP tools that map activity types to structured logging functions, with automatic timestamps and optional association with deals or contacts.","intents":["I want Claude to log a call summary as an activity after analyzing a customer conversation","I need Claude to create a meeting note and attach it to a specific deal","I want to see a timeline of all activities for a contact to understand engagement history"],"best_for":["Sales teams maintaining detailed customer interaction records","Customer success teams documenting support interactions","Developers building activity-based CRM automation"],"limitations":["Activity types are predefined — no custom activity type creation via MCP","No attachment support — activities are text-only, cannot store files or media","Timeline retrieval is contact-centric — no cross-contact activity search or filtering","No activity templates or auto-population of common fields (e.g., meeting duration)"],"requires":["MCP server with CRM API credentials","Activity types defined in CRM (call, email, meeting, note, etc.)","Contact or deal ID for activity association"],"input_types":["natural language activity descriptions","structured activity parameters (type, description, contact_id, deal_id, date)","activity type enumeration"],"output_types":["activity records (JSON with id, type, description, contact_id, deal_id, created_at, created_by)","activity timelines (sorted list of activities for a contact/deal)","activity summaries (count by type, date range)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aminetwiti-mcpgrowcrm1__cap_4","uri":"capability://tool.use.integration.mcp.resource.discovery.and.schema.introspection","name":"mcp resource discovery and schema introspection","description":"Exposes CRM data structures (contacts, deals, activities, custom fields) as MCP resources with JSON schema definitions, allowing MCP clients to discover available operations and understand field requirements without external documentation. Implements MCP's resource listing and schema endpoints to provide runtime introspection of CRM capabilities.","intents":["I want my MCP client to automatically discover what CRM operations are available","I need to understand the schema of contact and deal fields before building an agent","I want to validate that my CRM has the required fields before deploying an automation"],"best_for":["Developers building MCP clients that need to adapt to different CRM configurations","Teams deploying MCP servers across multiple CRM instances with varying schemas","Non-technical users wanting to understand what Claude can do with their CRM"],"limitations":["Schema introspection is static — does not reflect runtime CRM configuration changes without server restart","No support for conditional field requirements (e.g., fields required only for certain deal types)","Custom field discovery may be incomplete if CRM API does not expose all field metadata","Schema validation is informational only — does not prevent invalid operations at the MCP level"],"requires":["MCP server with CRM API credentials","CRM API support for schema/metadata endpoints","MCP client with resource discovery capability"],"input_types":["MCP resource list requests","MCP schema introspection requests"],"output_types":["MCP resource definitions (JSON with resource URIs, descriptions, MIME types)","JSON schema documents (field definitions, types, constraints, required fields)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aminetwiti-mcpgrowcrm1__cap_5","uri":"capability://tool.use.integration.error.handling.and.operation.validation","name":"error handling and operation validation","description":"Provides structured error responses and pre-operation validation for CRM operations, catching common mistakes (missing required fields, invalid stage transitions, non-existent contacts) before they reach the CRM API. Implements validation logic at the MCP tool layer with detailed error messages that Claude can use to correct operations.","intents":["I want Claude to understand why an operation failed and retry with corrected parameters","I need validation to prevent invalid data from being written to the CRM","I want detailed error messages that help debug automation failures"],"best_for":["Teams building production CRM automations that require high reliability","Developers debugging MCP integration issues","Non-technical users wanting clear feedback when operations fail"],"limitations":["Validation is local to MCP server — does not catch CRM-side business rule violations","Error messages are generic — may not reflect CRM-specific validation rules","No retry logic — failed operations require explicit client retry","Validation overhead adds latency (~50-100ms per operation) for complex schemas"],"requires":["MCP server with validation logic implemented","CRM schema definitions for field validation","MCP client capable of handling structured error responses"],"input_types":["operation parameters (contact fields, deal data, activity details)","validation rules (required fields, field types, constraints)"],"output_types":["validation error responses (JSON with error code, message, field path)","operation success confirmations","detailed error context for debugging"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["MCP-compatible client (Claude Desktop, Cline, or custom MCP host)","CRM API credentials (GrowCRM or compatible system)","Node.js runtime for MCP server execution","Network connectivity between MCP server and CRM API","MCP server running with CRM API credentials","Contact schema defined in CRM (standard fields: name, email, phone, company, tags)","MCP client with tool-calling capability","MCP server with CRM API credentials","Deal schema and pipeline stages defined in CRM","Contact/account context for deal creation (foreign key relationships)"],"failure_modes":["Requires MCP client support — not all CRM tools or AI interfaces expose MCP yet","No built-in authentication abstraction — must handle CRM API credentials securely at server level","Limited to CRM operations exposed by the server implementation — custom fields or non-standard objects may not be supported","Synchronization is request-response only — no real-time event streaming or webhook support","No bulk import/export — operations are single-contact or filtered-list only","Field validation is server-side only — no client-side schema hints for complex custom fields","Search is limited to exact match or simple filters — no full-text search or fuzzy matching","No deduplication logic — creating duplicate contacts requires manual cleanup","No support for custom deal fields beyond standard metadata (amount, close_date, probability, stage)","Stage transitions are not validated against CRM workflow rules — invalid moves may succeed silently","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.48999999999999994,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.635Z","last_scraped_at":"2026-05-03T15:19:24.054Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=aminetwiti-mcpgrowcrm1","compare_url":"https://unfragile.ai/compare?artifact=aminetwiti-mcpgrowcrm1"}},"signature":"//o9321jwE5GMQOO42rlPOUmTbDwAPQFswF6g52rG+IyHmQ4GHEoRkVNQgWJI3VgT6CHzgAxttvVWi/szP8HBw==","signedAt":"2026-06-22T17:30:57.203Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/aminetwiti-mcpgrowcrm1","artifact":"https://unfragile.ai/aminetwiti-mcpgrowcrm1","verify":"https://unfragile.ai/api/v1/verify?slug=aminetwiti-mcpgrowcrm1","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}