Changelog

This page tracks Partner API and Meshi MCP changes that affect integrations.

Unreleased

get_mutual_fit on the personal connector. Ranks people across Meshi by mutual fit against your goals, optionally for one specific goal. This is the only personal tool that looks beyond your own connections; it returns the same match signal the Meshi app’s discover view shows you (scores, tier, the matched goals on both sides, name/role/company) and deliberately returns no profile prose about a non-connection.
confirm_goal on the personal connector. Records a goal the user stated. Requires the meshi:write permission — clients connected before this tool existed will not see it until they reconnect and approve it, and nothing else changes for them in the meantime. It is annotated readOnlyHint: false, so hosts should prompt before running it; the read tools are unchanged.
search_people gained timeline and raw_source dimensions and a hybrid mode, plus cursor pagination (cursor in, next_cursor out). The cursor is valid only for the exact query, scope and type it came from.
Result envelopes gained scope_status, scope_hint, truncated and next_cursor. scope_status: "network_empty" distinguishes “this user has no connections” from “nothing matched” — previously both were an empty list.

get_person_brief returns unconfirmed claims. Previously it returned only confirmed claims, which in practice meant an empty array for nearly every person. Each claim now carries a typed authority and status, and the server instructions define the provenance ladder so an agent can rank them.
authority, status and distance are now typed and documented on the wire, and the server instructions define mutual fit and provenance. Agents no longer have to guess what authority: "inferred" means relative to "user_asserted".
Oversized results are trimmed with a flag instead of rejected. Previously a result over the transport size cap returned an error and no data, which was reachable at the documented maximum limit.

Meshi Admin MCP connector (beta). A separate connector at /mcp/admin for organization owners, admins, and editors: organization discovery, multi-organization people search and exact counts, full person detail, list/event/roster management, and preview-and-confirm destructive actions. Separate OAuth grant from the personal connector; see Meshi Admin Connector.

Roster responses now expose event.side, the matching-side tag for two-sided events. The existing event.role_at_event remains descriptive only.
Identity-review queue items now include a minimal candidate comparison object (display_name, title, company, and linkedin_url when available). It intentionally omits email addresses and Meshi internal IDs.

Assigned-event keys now report event_id during auth and consistently restrict events, runs, reviews, searches, and ID mappings to that event.
Partial attendee imports expose actionable review_id values. Held reviews document accept/reject/distinct recovery, remaining candidates, conflict-safe 409 responses, and fresh idempotency keys for corrected terminal work.
Event-wide matches reject unsupported session_id instead of silently ignoring it. The event roster entity_id exception, pre-pagination exclusions, pinned runs, readiness after enrichment, and V1 matching boundary are now explicit.
Attendee side corrections reject unsupported body fields instead of silently ignoring them. Event-intent changes continue to use stable-ID re-imports with a fresh idempotency key.

Event-scoped attendee removal: DELETE /events/:event_id/attendees/:attendee_id, with dry_run=true support and retry-safe relationship cleanup.
Session filters on GET /events/:event_id/sessions: q, starts_after, and starts_before.

Event force-delete now reports relationship cleanup explicitly with event_attendees, session_participants, sessions, and retained_people counts. Event deletion does not erase org-level people or partner ID mappings.
Endpoint reference examples now show GET /auth environment/capability metadata and state that v0 webhook_url values are poll-only.

Event lifecycle endpoints: PATCH /events/:event_id and DELETE /events/:event_id.
Session lifecycle endpoints: PATCH /events/:event_id/sessions/:session_id and DELETE /events/:event_id/sessions/:session_id.
Partner API capability discovery: GET /capabilities.
Attendee intelligence endpoints for profile, event context, identity status, canonical brief, goals, traits, and readiness.
Event- and org-scoped people search endpoints.
Event-level readiness diagnostics for match/enrichment preparation.

GET /auth now includes the current environment and capability metadata.
Session responses now include updated_at.
Event and session delete operations are soft deletes. Event deletion supports dry_run=true and requires force=true when the event still contains sessions or attendees.
Collection cursors use partner-owned identifiers in their decoded payloads.

Every accepted attendee import in staging and production emits an internal Meshi engineering Slack notification for operational visibility. Notifications include debugging IDs and counts, but not attendee names or emails.