# sellinger-mcp

MCP server exposing Sellinger CRM operations as tools

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** Unknown
- **License:** MIT
- **npm:** sellinger-mcp
- **Source:** https://github.com/asenlevov/sellinger.ai
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-10T13:36:35.387Z
- **Version scanned:** 0.1.0
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_leads` — List leads from the CRM with optional filters. Returns a paginated array of leads.
- `get_lead` — Retrieve a single lead by its UUID. Returns the full lead record with all fields.
- `create_lead` — Create a new lead in the CRM. Returns the newly created lead record.
- `update_lead` — Update fields on an existing lead. Only provided fields will be changed. Do NOT update the updated_at field.
- `opt_out_lead` — Record that a person asked us to stop contacting them. This is the SUPPORTED way to honour
- `send_message` — Send a message to a lead via a specified channel (email, linkedin, whatsapp).
- `list_segments` — List all segments (saved lead filters/groups) in the CRM.
- `get_analytics` — Retrieve a KPI summary including total leads, conversion rate, response rate, and pipeline distribution.
- `search_leads` — Full-text search across all lead fields. More powerful than list_leads search parameter.
- `list_agents` — List all Sellinger agents for the team.
- `get_agent` — Get a single agent by UUID including configs and channels.
- `list_approvals` — List pending approvals (messages, actions, suggestions).
- `get_pipeline_counts` — Get lead counts per pipeline stage.
- `list_companies` — List companies in the CRM.
- `get_hot_leads` — Get high-intent leads from intent signals.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"sellinger\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"sellinger-mcp\"\n      ],\n      \"env\": {\n        \"SELLINGER_API_KEY\": \"<YOUR_SELLINGER_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `SELLINGER_API_KEY` — Sellinger API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/sellinger-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/sellinger-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/sellinger-mcp
- HTML page: https://forgeregistry.com/registry/sellinger-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.