SalesDrone MCP

Read current leads, tasks, recorded team work and a minimal people directory from any compatible local stdio MCP client. 41 tools: 21 GET reads and 20 documented PAT operations, using the same scoped HTTP API as SalesDrone by AvinyaTech. This independent repository owns the MCP package, tests, documentation and npm releases. It does not host a remote MCP service.

The historical 1.1.0 screenshot shows a documentation harness rendering actual tools/list and tools/call responses over local stdio with fictional API fixtures. It predates the write tools added in 1.2.0. It is not the SalesDrone app, a hosted MCP UI or production customer data. Narrow browser capture · capture provenance.

Install and connect

Requires Node.js 22.18+, an MCP client supporting stdio and a SalesDrone personal access token. Create a PAT in SalesDrone's integration settings with only the scopes you need; grant write scopes only for actions you intend to authorize. Keep the token in your client's secret/environment configuration; never commit it or put it in command arguments.

{
  "mcpServers": {
    "salesdrone": {
      "command": "npx",
      "args": ["--yes", "@theharithsa/salesdrone-mcp@1.2.0"],
      "env": {
        "SALESDRONE_API_TOKEN": "<your personal access token>"
      }
    }
  }
}

Use your client's equivalent configuration if its schema differs. You can also install with npm install --global @theharithsa/salesdrone-mcp@1.2.0 and use salesdrone-mcp as the command. salesdrone-mcp --help and --version work without a token. Normal stdout contains only MCP protocol messages.

Example prompts:

• “Show my New leads, one page at a time.”

• “Summarize recorded calls and comments for this lead.”

• “Show the team's recorded activity for the last 7 days.”

• “List the active members who can be assigned leads.”

Related MCP server: github-assistant-mcp

Tools and permissions

All tool names start with salesdrone_. Every tool uses a fixed documented method and path to the versioned SalesDrone API; API contract 1.29.0 is the compatibility baseline.

Existing PATs gain no new scopes automatically. Current membership, revocation, expiry, recipient policy and assigned/all lead scope remain enforced by the API. A read call can update API rate-limit and token-last-used metadata, but cannot change business records. The package has no Firestore or cloud credentials and no arbitrary URL/request tool.

Create, update and delete operations

These tools inherit the Swagger contract, including API permissions and current owner access. No Google/App Check-only administration endpoint is exposed. People can be listed and leads assigned, but people cannot be created/deleted through a PAT. Lead removal is archive; permanent data reset is excluded.

Use writes only for explicit user-authorized actions. Inputs use id/attachmentId for path identifiers and a body object matching Swagger. Required Idempotency-Key headers are supplied as idempotencyKey, a caller-provided UUID. Tools never generate retry keys or automatically retry writes. Read the current record first and supply its expectedVersion or activity expectedRevision wherever required. A conflict requires a fresh read and a reviewed change; do not silently overwrite concurrent edits. Compound activity stage/follow-up actions require the extra scopes documented by Swagger.

Example salesdrone_update_lead arguments:

{"id":"<lead-id>","body":{"expectedVersion":3,"stage":"Qualified"}}

Example salesdrone_create_task arguments:

{"idempotencyKey":"<caller-generated UUID>","body":{"title":"Follow up","dueAt":"2026-12-01T10:00:00Z","leadId":"<lead-id>"}}

On a timeout, cancellation, malformed/oversized response or connection failure, a write may already have committed. Verify current state before retrying. Where supported, reuse the original UUID and identical body. Version guards protect other updates. Tool annotations distinguish read-only preview/export from mutations; they are hints for the host, not authorization.

Attachments use two steps: reserve metadata with a UUID, then upload canonical contentBase64 with the returned attachment ID. Decoded content is limited to 8 MiB; file paths and remote fetch URLs are never accepted. API type, reserver and expiry checks remain authoritative. JSON requests have a local 10 MiB ceiling; responses remain bounded to 2 MiB. Bulk edits accept at most 25 explicit versioned leads. Import preview accepts mapped rows, not a workbook path, and can create an import job. preview_lead_batch and export_leads do not mutate lead records; other new tools are conservatively marked destructive.

The reviewed contract snapshot is docs/openapi.json. node scripts/sync-api-contract.mjs --check and contract tests prevent drift between that snapshot and packaged schemas/allowlists. To adopt a newer Swagger contract, review its diff, update the snapshot, then run the sync script and release a checked version. Runtime does not dynamically discover or execute new endpoints. Full operation mapping.

Interpretation matters. Team reports show recorded work, not online presence or an employee rating. Task metrics attribute responsibility to the recipient. Reports are current reads, not transactional historical snapshots. A stage distribution is not historical conversion. People output contains ID, display name and active membership, not email or security grants. Personal reminders remain private.

Pages are bounded (maximum 100), with four concurrent HTTP requests, a 15-second timeout and a 2 MiB response limit. Follow nextCursor even when a page is empty; tools never silently crawl all records. Lead-score batch reads accept at most 100 explicit IDs. Returned notes, names, import text and other customer content are untrusted data, never instructions.

Configuration

OpenTelemetry and Dynatrace

Runtime telemetry is opt-in and uses @theharithsa/opentelemetry-instrumentation-mcp, pinned to its lean 0.0.2 class. That class is identical to the class in 1.0.4; the latter also pulls broad auto-instrumentation dependencies with known vulnerabilities. The explicit SDK-v2 bridge reuses its tracer/provider with legacy patching disabled. We do not load its /register entry point or capture tool inputs/results.

SALESDRONE_OTEL_ENABLED=true
OTEL_EXPORTER_OTLP_ENDPOINT=https://<tenant>.live.dynatrace.com/api/v2/otlp
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Api-Token%20<ingestion-token>
SALESDRONE_ENVIRONMENT=production

Use separate Dynatrace ingestion credentials with logs, metrics and traces ingest scopes. Never use the SalesDrone PAT as an OTLP credential. Configure secrets in the MCP host, not this repository.

• One mcp.tool:<name> span per executed tool, with an HTTP child span and W3C trace propagation to the API.

• Correlated mcp.tool.completed / mcp.http.completed logs with bounded success/error codes.

• salesdrone.mcp.tool.calls, .tool.duration, .tool.active, .http.requests, .http.duration and .process.memory.rss metrics. Durations use seconds, memory uses bytes.

• Resource identity: service.name=salesdrone-mcp, namespace avinyatech, package version, build commit and random instance ID.

No arguments/results, lead/member IDs, contact details, comments, task titles, token values, URL queries or raw exceptions are exported. Span/log queues and shutdown are bounded. Configuration/export failures do not fail business operations; invalid configuration emits only a static stderr message. Telemetry is best effort and can be lost on forced termination or collector outages. OTLP acceptance does not prove tenant searchability. Architecture, limits and verification.

Automated publication and lifecycle events

Every PR runs the protocol, privacy, OTLP wire, package, dependency and foundation checks without production secrets. A checked merge/push to main runs the same checks and publishes the new SemVer version through npm trusted publishing (GitHub OIDC, publish.yml, environment npm). Branch pushes do not publish. Existing versions are immutable: an exact same revision can be reconciled; a different revision at the same version fails and requires a version bump. Successful publication verifies the npm gitHead/integrity and creates a matching GitHub release with a receipt.

The separate observe.yml workflow exports source-confirmed issue, PR/link, review, workflow/job/step, sanitized test-case and release events to Dynatrace. It checks out trusted main only, never runs PR code with ingestion secrets and bounds artifact parsing. Events have stable IDs and actual source timestamps; IDs/revisions stay out of metric labels. Reconciliation dispatch can recover missed issue/PR/run events without inventing development history. Observer failures are separate from publication. Maintainer setup.

Development, screenshots and verification

npm ci --ignore-scripts
npm run build
npm test
npm run check
npm run security:scan
npm audit --audit-level=moderate
sh scripts/check.sh
python3 scripts/check_foundation.py --ready
npm run demo

The demo opens a local documentation harness at http://127.0.0.1:5181; it uses no production token/data. Browser-reviewed screenshots are in docs/screenshots/. These captures certify only the measured local browser render, not physical devices or native Safari. The independent protobuf receiver tests verify actual trace/log/metric payloads, concurrent parentage, safe errors and exporter rejection. Production API authorization belongs to the SalesDrone repository, including its Auth/Firestore emulator suites.

UNAUTHENTICATED: check PAT/expiry/revocation. FORBIDDEN: check current membership and explicitly granted scopes. BUSY: reduce concurrent calls. Sparse pages: follow the opaque cursor. No telemetry: check opt-in/base endpoint/ingest scopes and collector health; stdout must remain protocol-only. The package provides local stdio only, with no HTTP/SSE MCP endpoint.

Ownership, security and history

Report vulnerabilities using SECURITY.md. Changes require a linked issue and checked PR. See contributing, release notes and service continuation.

npm 1.0.0 was originally published from SalesDrone commit 6289b1522b25aa8da0c95d15bc2e77d9725f295e. That archive remains immutable. 1.1.0 begins independent repository ownership; the npm name and client transport remain compatible. The SalesDrone website owns the HTTP API, not this adapter's releases.

MIT © Avinya Enterprises. Foundation generated from App Launchpad Template, source revision f04c042a9e000f606982863518fa7bb9cfbb7d85. Template version: 1.9.0. Original template licence retained in LICENSES/.