Skip to main content

​
MCP v2.1.1

​
June 3, 2026

Dynamic Client Registration now accepts a partial redirect_uris array. Previously, if any single URI in the redirect_uris array failed the redirect URI policy, the entire registration was rejected with 400 invalid_redirect_uri. Now the endpoint registers only the valid subset and drops the rest — a 201 response’s redirect_uris field reflects the accepted URIs, which may be fewer than you submitted. The registration is only rejected outright when none of the supplied URIs are valid. The per-URI validation rules (loopback, allowlisted https host, approved custom scheme, reverse-DNS scheme) are unchanged. See Authentication for the full policy table.

​
v1.0.8

​
May 26, 2026

Bug fixes and behavioral improvements for custom_field_filters on List Contacts and List Events:
  • Age operators on date fields now work. age_greater_than, age_equal_to, and age_less_than were documented but incorrectly rejected with a 422 when passed a whole-number day count. The validator now accepts numeric values for these operators on date fields (profile_field_26–profile_field_30).
  • Date filter comparisons are timezone-aware. equal_to, greater_than, less_than, and between on date fields now evaluate against your space’s configured timezone. equal_to expands to a full midnight-to-midnight range for the given day; greater_than compares against end-of-day. Previously these operators compared raw strings, which would miss column values with a stored time component.
  • Numeric any / unknown semantics. For numeric fields, any matches contacts where the value is greater than 0; unknown matches contacts where the value is 0 or unset.
  • not_equal_to and not_contains no longer include unset values. Previously these operators could return contacts where the field was NULL or empty. If you need those contacts, add a separate unknown condition ANDed alongside.
  • Text filter literals. The _ and \ characters in contains, starts_with, ends_with, and contains_word filter values are now treated as literal characters instead of LIKE wildcards.

​
MCP v2.1.0

​
May 21, 2026

Removed the four export tools — request_event_export, request_contact_export, request_company_export, and get_export_status. Bulk extraction is better handled by the Public API V1 export endpoints (programmatic) or the in-app CSV export buttons (interactive). Routing the rows through an MCP turn just consumed tool slots and added a polling round-trip without giving the agent any analytical leverage. Use query_events_aggregated, query_contacts_aggregated, or the various query_ad_metrics_* tools when the agent needs to reason about large datasets — not export them. The MCP catalog is now 50 external tools across 14 toolsets (down from 54 / 15).

​
MCP v2.0.0

​
May 15, 2026

Major expansion of the Cometly MCP server — from 7 read-only tools to 54 external tools across 15 toolsets, plus the first MCP Resources and Prompts. Backwards compatible: every v1 tool kept its original input/output shape, with format: "csv" | "json" | "yaml" added as an opt-in. New toolsets (49 new tools): Resources (read-only, subscribable):
  • cometly://workspace/context
  • cometly://catalog/metrics
  • cometly://catalog/attribution-models
  • cometly://catalog/dimensions
  • cometly://catalog/custom-events
Prompts (slash-command templates):
  • analyze_performance
  • compare_attribution_models
  • weekly_review
  • find_underperformers
Cross-cutting improvements:
  • Custom event label resolution — analytics tools accept either custom_event_2 or the configured label (“Deal Created”) in their inputs. Output rewrites slot ids to labels with a # label_map: footer for round-tripping.
  • Empty-state hints — analytics tools annotate suspicious all-zero results with hints like “No facebook_ads account is connected to this space” or “Last google_ads sync was 3 days ago”.
  • Token-budget pagination — responses cap around ~6,000 tokens with a truncated_at_token_budget: true footer + opaque next_cursor.
  • CSV default for new tools — ~50% fewer tokens than JSON for tabular results. Legacy v1 tools keep JSON as default.
  • DST caveat — query_ad_metrics and resolve_date_range surface a DST advisory when the requested window crosses a transition.
  • Honest forecasting language — softened “anomaly detection” / “forecast” claims in tool descriptions to “directional reads” — we don’t run statistical models, the agent does threshold math.
  • external: false filtering — tools that only make sense in-app (chat history, file attachments) are hidden from external MCP clients via a server-level shouldRegister filter.

​
v1.0.7

​
May 14, 2026

  • Update Contact endpoint — Added PUT /contacts/ for updating an existing contact’s emails, phones, names, locations, and custom_fields. Uses sparse PUT semantics: any field you include replaces the existing collection in full; any field you omit is left untouched. Empty arrays ([]) wipe a collection; providing custom_fields clears every key not in the object.
  • Update Company endpoint — Added PUT /companies/ for updating a company’s domain and name. Uses sparse PUT semantics — only the fields you include are modified.
  • name field on Get Company — The Get Company response now includes name alongside id and domain. This is an additive change; existing fields are unchanged.
  • custom_field_filters parameter on List Contacts — Added custom_field_filters to the List Contacts endpoint. Accepts an array of AND-joined conditions (max 10) for filtering contacts by their custom profile field values. Each condition takes { field, operator, value } (or { field, operator, start, end } for the between operator). The field must reference a profile_field_N slot configured with a label in your space; operator vocabulary depends on the field’s type (text / number / date).
  • custom_field_filters parameter on List Events — Same parameter added to the List Events endpoint, narrowing results to events whose owning contact matches the conditions. Same shape and operator vocabulary as List Contacts.

​
v1.0.6

​
April 20, 2026

  • include_browsing_session_data parameter on Get Contact — Added include_browsing_session_data to the Get Contact endpoint. When set to 1, the response includes a browsing_session_hits array with up to the last 1000 raw browsing hits (page views) for the contact, ordered by most recent first. Each hit includes event_url (full URL), referrer_host, source, country, device_type, browser, os, event_name, and event_time_utc.

​
v1.0.5

​
April 7, 2026

  • include_events parameter on Get Contact — Added include_events to the Get Contact endpoint. When set to 1, the response includes an events array containing the contact’s full journey — all conversions and touchpoints sorted by most recent first. Conversion events include event_name, amount, event_url, order_id, order_name, channel (browser/server), and integration. Touchpoint events include source, touchpoint_url, referrer_url, and the full ad hierarchy (ad_name, adset_name, campaign_name, account_name).
  • hide_direct_touchpoints parameter on Get Contact — Added hide_direct_touchpoints (default 1) to the Get Contact endpoint. When include_events=1, direct touchpoints are excluded by default. Set to 0 to include them.

​
v1.0.4

​
March 19, 2026

  • use_custom_field_labels parameter — Added use_custom_field_labels to the List Contacts and Get Contact endpoints. When set to 1, custom field keys use user-defined labels (e.g. "Customer Age") instead of raw column names (e.g. "profile_field_1"). Fields without a configured label retain their raw column name.

​
v1.0.3

​
February 27, 2026

  • Ad hierarchy fields on List Events — Added ad_name, adset_id, adset_name, campaign_id, campaign_name, account_id, and account_name as requestable fields on the List Events endpoint. These fields require sources to be provided and return the ad, ad set, campaign, and account data from the attributed touchpoint.

​
v1.0.2

​
February 19, 2026

  • include_all_emails parameter — Added include_all_emails to the List Contacts and Create Contact Export endpoints. When set to 1, returns all email addresses associated with a contact, including emails from merged profiles.

​
v1.0.1

​
February 17, 2026

  • Custom fields on Create Event — The Create Event endpoint now accepts custom profile fields (profile_field_1 through profile_field_30) as root-level properties. Fields 1-15 accept text, 16-25 accept numbers (string or number), 26-30 accept dates.
  • event_url field — Added event_url as a requestable field on the List Events and Create Event Export endpoints. Returns the full URL where the event occurred.

​
v1.0.0

​
Initial release