MCP server for Kylas CRM: create, search, and manage leads. Requires KYLAS_API_KEY.
Model Context Protocol server for Kylas CRM lead operations. Use it from Cursor, Claude Desktop, or any MCP client to create leads, search and filter leads, and look up users, products, and pipelines. getleadfieldinstructions – Get lead schema (standard + custom fields, picklist IDs) createlead – Create a lead with dynamic fields from user context searchleads – Search/filter leads by multiple…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Model Context Protocol server for Kylas CRM lead operations. Use it from Cursor, Claude Desktop, or any MCP client to create leads, search and filter leads, and look up users, products, and pipelines. getleadfieldinstructions – Get lead schema (standard + custom fields, picklist IDs) createlead – Create a lead with dynamic fields from user context searchleads – Search/filter leads by multiple criteria lookupusers – Resolve user names to IDs (for owner, created by, etc.) lookupproducts – Resolve…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.