@mesheshq/mcp-server
MCP server for Meshes — emit events, manage workspaces, create rules, and inspect deliveries from any MCP-compatible client.
Versions
1.0.10latest1.0.91.0.81.0.71.0.6+ show 4 moreshow less
1.0.51.0.41.0.31.0.0Tools 33
meshes_create_session Mint a new embedded session with an access token and launch URL. Sessions can target full workspaces, dashboard-only views, or resource-scoped embeds.
meshes_list_sessions List embedded sessions for a workspace with optional pagination, status, and resource filters.
meshes_refresh_session Refresh the access token for an existing session without minting a new session record.
meshes_revoke_session Revoke an active embedded session.
meshes_get_workspace_events List events for a workspace with optional filters. Useful for checking delivery status, debugging, or monitoring event flow.
meshes_list_events List events across the organization with pagination.
meshes_get_event Get event details including delivery status and per-rule results (rule_events). Each rule_event shows connection, integration_type, status, attempt_count, and last_error.
meshes_get_event_payload Get event details including the full event payload. Useful for debugging what data was sent.
meshes_retry_event_rule Manually retry a failed rule delivery for a specific event. Use after investigating and fixing the underlying issue (e.g., expired credentials, misconfigured mapping).
meshes_emit_event Emit a product event to Meshes for routing and delivery. Because this MCP server uses organization-level machine credentials, workspace is required for each emitted event. Always include 'email' in the payload for person-related events.
meshes_emit_bulk_events Emit up to 100 events in a single request. Because this MCP server uses organization-level machine credentials, each event must include workspace. Returns 201 on full success, 207 on partial success with per-event error details.
meshes_list_workspaces List all workspaces in the Meshes organization. Workspaces are tenant-scoped containers holding connections, rules, and event logs. In multi-tenant apps, each customer typically has one workspace.
meshes_get_workspace Get details of a specific workspace by UUID, including its publishable key for client-side event ingestion.
meshes_create_workspace Create a new workspace. Typically used when onboarding a new tenant in a multi-tenant SaaS app.
meshes_update_workspace Update a workspace's name and description.
meshes_get_workspace_connections List all connections scoped to a specific workspace.
meshes_get_workspace_event_types List the event types configured for a workspace, including each key, label, description, and active state.
meshes_get_workspace_resources List the resource types configured for a workspace, including each key, label, description, and active state.
meshes_get_workspace_rules List routing rules scoped to a specific workspace, with optional event and resource filters.
meshes_list_rules List all routing rules across the organization. Rules bind event types to connections with action metadata. Supports filtering by event, resource, and resource_id.
meshes_get_rule Get details of a specific routing rule by UUID.
meshes_create_rule Create a routing rule that binds an event type to a connection. The metadata.action field is required and determines what the destination does (e.g., 'create_or_update_contact'). Use meshes_get_connection_actions to discover available actions.
meshes_delete_rule Delete a routing rule. Events matching this rule will no longer be routed to its connection.
meshes_list_connections List all connections across the organization. Connections are configured destinations (HubSpot, Salesforce, Resend, webhooks, etc.) holding credentials and config.
meshes_get_connection Get details of a specific connection. Does not expose raw credentials.
meshes_create_connection Create a new connection (destination) in a workspace. The metadata object contains connector-specific configuration (API keys, OAuth tokens, webhook URLs, etc.).
meshes_update_connection Update a connection's name, metadata, or visibility.
meshes_delete_connection Delete a connection. Returns 409 if it has active rules unless force_delete is true.
meshes_get_connection_actions Get available actions for a connection (e.g., create_or_update_contact, add_to_list). Use this to discover what actions to put in rule metadata.
meshes_get_connection_fields Get the destination field catalog for a connection. Returns field keys, types, constraints, and allowed values. Useful for building field mappings.
meshes_get_connection_default_mappings Get the default field mapping for a connection. Mappings define how event payload fields map to destination fields with optional transforms (trim, lower, upper, to_string, etc.).
meshes_update_connection_default_mappings Store or replace the default field mapping for a connection. Supply a schema with destination fields, payload sources, and optional transforms like trim, lower, default, or type conversion.
meshes_list_integrations Get metadata about all supported integration types. Returns each type's authentication method (oauth, api_key, basic, none), available actions, and field definitions. Useful for discovering what integrations are possible and what actions they support.
Permissions 1
env_vars low