What Agentmatica connects to today.
We're honest about what ships today versus what you can wire up via Model Context Protocol (MCP). Anything not below isn't a native connector — if it has an MCP server, you can plug it in.
connects to
01 · Ingestion
Point the agent at a URL — we crawl, embed, and keep the index in sync.
Any website
Marketing sites, docs sites, help centers, blogs.
Sitemap-aware crawl
Respects robots.txt and sitemap.xml. Configurable depth.
Auto re-sync
Trigger fresh crawls anytime. Source URLs stay attached to every cited passage.
02 · Live tools via MCP
Model Context Protocol turns any compatible API into agent tools at chat time. Paste the URL in the bot's Connections panel.
Shopify
Built-inBuilt-in support for Shopify's Storefront MCP — search catalog, build carts, drop visitors at checkout.
WordPress
Custom MCPUse the official wordpress/mcp-adapter plugin. Reads posts, taxonomies, custom post types.
WooCommerce
Custom MCPConnect via an MCP server (e.g. the WordPress adapter with WooCommerce hooks).
Any internal API
Custom MCPExpose an MCP server in front of your CRM, helpdesk, or internal app and the agent uses it.
03 · Notifications
Where alerts land.
Slack
Per-bot incoming webhook. Pick whether leads and escalations push to that channel.
Email
Lead-capture emails to the bot owner. Subscription + usage emails to the workspace owner.
04 · Developer surface
Programmable agent for teams that ship their own UX.
REST API
Per-bot bearer tokens. Stream tokens back, persist conversations across sessions.
Embed widget
Single script tag. Async, ~6 KB gzipped. Bubble or full-screen spotlight mode.
Webhooks (planned)
Push lead, escalation, and quota events to your endpoint. Currently only Slack notifications ship.
Don't see your tool?
We build native connectors based on what teams ask for. If your tool doesn't have an MCP server yet, tell us — we'll prioritize the requests we hear most.