• Use Cases
  • Pricing
  • Security
  • Docs
Sign InStart free

The outbound integration layer for SaaS products: emit once, then let Meshes handle routing, retries, fan-out, and delivery history.

  • Terms of Service
  • Privacy Policy
  • Acceptable Use Policy
  • Cookie Policy

© Copyright 2026 Meshes, Inc. All Rights Reserved.

  • Getting Started
    • What is Meshes?
    • Quickstart
    • Core Concepts
    • API Overview
  • AI Tools
    • Cursor Rules
    • MCP Server
    • LLMs Docs
  • API Documentation
    • API Reference
    • Authentication
    • Results
    • Rate Limiting
    • SDKs
    • Integrations & Rules
  • Events
    • Publishable Keys
    • Send Events
    • Bulk Event Ingestion
  • Embed & Sessions
    • Quickstart
    • Session API Overview
    • Launch URL and Iframe Bootstrap
    • Iframe Message Contract
    • Session Roles and Scopes
    • Workspace Pages Available in Embed
    • Session Refresh Lifecycle
    • Iframe Sizing and Resize Handling
    • OAuth and Connection Setup Behavior
    • Security Model
    • Troubleshooting
  • Integrations
    • ActiveCampaign
    • AWeber
    • Customer.io
    • Discord
    • HubSpot
    • Intercom
    • Mailchimp
    • MailerLite
    • Pipedrive
    • Resend
    • Salesforce
    • SendGrid
    • Slack
    • Webhooks
    • Zoom

AI Tools

Use Meshes with AI coding agents like Cursor, Claude Code, and Windsurf. Cursor rules, MCP server, and integration guides for AI-assisted development.

Meshes provides first-class support for AI-assisted development. Whether you're using Cursor, Claude Code, Windsurf, or another AI coding tool, these resources help your agent understand the Meshes API and write correct integration code on the first try.

Available tools

  1. Cursor Rules: Drop-in rules file that teaches Cursor (and compatible editors) how to work with the Meshes API — correct endpoints, auth patterns, payload schemas, and best practices.
  2. MCP Server: A Model Context Protocol server that gives AI agents direct access to Meshes — emit events, manage workspaces, create rules, and debug deliveries from within your coding environment.
  3. LLMs Docs: Quick access page for both llms.txt and llms-full.txt.

Why AI-native?

Most integration platforms require developers to context-switch between docs, dashboards, and code. With Meshes AI tools, your coding agent already knows:

  • How to authenticate (Bearer JWT for management, publishable key for events)
  • The exact shape of every endpoint, request body, and response
  • Which payload fields matter for CRM contact matching (always include email)
  • How field mappings work (path vs. literal sources, transforms like trim, lower, to_date)
  • Multi-tenant patterns (one workspace per customer)
  • What NOT to do (don't build retry logic, don't fan out manually, don't hardcode workspace IDs)

The result: you describe what you want in natural language, and the agent writes correct Meshes integration code without you needing to look anything up.

  1. Available tools
    1. Why AI-native?