v2.6.1

2.6.1 (2026-06-28)

Bug Fixes

• refresh npm package metadata and README (Nubiia branding, keywords, tool table) (1ab552f)

v2.6.0

2.6.0 (2026-06-28)

Features

• complete Pipedrive API coverage (installments, lead/note/project fields) (#48) (73e6d08)

v2.5.0

2.5.0 (2026-06-28)

Features

• stages CRUD, lead labels CRUD, lead↔deal conversions (#34) (8a7860f)

v2.4.0

2.4.0 (2026-06-28)

Features

• add_time date filters for deals and leads (hardened) (#46) (3b77c4f)

v2.3.0

Features

Full custom fields support for the Pipedrive MCP server.

Writing custom values

All *_create / *_update tools for deals, persons, organizations, products and leads now accept a custom_fields object:

{
  "title": "ACME deal",
  "value": 50000,
  "custom_fields": {
    "Industria": "Tech",
    "Budget": 50000,
    "Tags": ["Enterprise", "EU"]
  }
}

• Keys can be display names (case-insensitive, trimmed) or 40-char hash keys
• enum/set labels translated to option ids automatically
• monetary accepts a number or { value, currency }
• daterange/timerange expand { start, end } to the two hash keys Pipedrive expects
• Unknown names produce a clear error with top-3 Levenshtein suggestions
• Duplicate display names raise duplicate_name with candidate hashes

Reading enriched responses

*_get, *_list and *_search now include custom_fields_resolved alongside the raw payload:

{
  "id": 123,
  "title": "ACME deal",
  "abc123def456...": 18,
  "custom_fields_resolved": { "Industria": "Tech" }
}

Read-path enrichment is opportunistic — only adds the resolved map if the field-definitions cache is warm; never adds an extra HTTP call. Search response shape (data.items[].item) is also handled.

CRUD for field definitions

Twelve new tools mirror the existing organization-field CRUD pattern:

• fields_create_deal_field, fields_update_deal_field, fields_delete_deal_field, fields_bulk_delete_deal_fields
• fields_create_person_field, fields_update_person_field, fields_delete_person_field, fields_bulk_delete_person_fields
• fields_create_product_field, fields_update_product_field, fields_delete_product_field, fields_bulk_delete_product_fields

Leads share deal field definitions (no separate /leadFields endpoint in Pipedrive).

Breaking-ish change

Create/update zod schemas for deals, persons, organizations, products and leads no longer reject unknown top-level keys (.strict() removed). Custom values should now be passed inside custom_fields instead of at the top level. Existing top-level hash keys are silently stripped by zod's default behavior.

Organization tools were also migrated to use the canonical schemas (instead of inline ones), exposing 6 additional address fields previously not accessible: label, address_subpremise, address_sublocality, address_admin_area_level_1, address_admin_area_level_2, address_formatted_address.

Docs

See docs/CUSTOM_FIELDS.md for full usage guide.

Tests

959 tests passing (33 files). Type-check, build and lint clean.

Full diff: #32

v2.2.0

2.2.0 (2026-06-09)

Features

• add job_title support to persons_create and persons_update (2ace13d), closes #29

v2.1.0

2.1.0 (2026-05-28)

Bug Fixes

• accept string-encoded numeric inputs from MCP clients (72f7ecc)
• resolve toolset filter for compound names (72fa9de)

Features

• add organizations_list_followers and OrganizationFields CRUD (732fde0)

v2.0.0

2.0.0 (2025-12-11)

• feat!: standardize tool naming convention to use underscores (2233ed6)

BREAKING CHANGES

• All tool names now use underscores instead of forward slashes to comply with MCP naming standards and align with mcp-holded pattern.

Migration guide:

• deals/create → deals_create
• persons/get → persons_get
• organizations/list → organizations_list
• activities/mark_as_done → activities_mark_as_done
• projects/activities/list → projects_activities_list
• etc.

This affects all 250+ tools across all categories:

• Deals, Persons, Organizations, Activities
• Files, Search, Pipelines, Notes, Fields, System
• Products, Leads, Users, Roles, Webhooks, Filters
• Projects, Goals, Tasks, Activity-types, Call-logs
• Mailbox, Teams, Org-relationships, Permission-sets
• Channels, Meetings, Project-templates

Rationale:

• MCP tool naming pattern requires ^[a-zA-Z0-9_-]{1,64}$
• Forward slashes in tool names caused validation errors
• Aligns with proven mcp-holded implementation
• Improves consistency across all tool categories

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

v1.1.6

1.1.6 (2025-12-11)

Bug Fixes

• add allow-deprecated-schema flag for MCP registry publish (33e248f)

v1.1.5

1.1.5 (2025-12-11)

Bug Fixes

• remove deprecated $schema field from server.json (f8e3453)