Skip to content
toby
Free trial
Integration · Via Add any tool

Connect any marketing tool to your AI agents, via MCP, API or webhook

Toby's ready-made connectors cover the usual stack. For everything else (HubSpot, Linear, GitHub, Airtable, your own back office), you add the tool yourself in three ways: its remote MCP server, its API, read by Toby from the documentation, or a Zapier, Make or n8n webhook. Reads run right away; anything that changes data waits for your approval.

Any tool (MCP, API, webhook)Via Add any tool
Three ways in
Remote MCP server (https) · the tool's REST API · Zapier, Make or n8n webhook
Approval
Only actions marked read-only run on their own. Everything else waits for you, even on Autopilot.
Ready-made MCP servers
Stripe, Linear and GitHub, plus any other remote server by address
Setup
2 to 10 minutes, depending on the route
Agents
TobyLeoIris

What Toby does with any tool

Exactly what the connector does today. Reads happen right away; anything that changes, publishes or sends something waits for your approval.

The agents who use it

What you get, concretely

Examples on fictional businesses, in the app's exact format. Numbers are examples, not promises: yours come from your own data.

CMO

Example

Re-engage the 46 deals stuck at “Demo done” for three weeks

Why: HubSpot (connected through its API): 46 open deals have been at the “Demo done” stage for more than 21 days, worth $61,000 in pipeline. 30 of them never received an email after the demo.

Example estimate: 4 to 8 deals moved forward this month

First deliverable, ready to paste

Follow-up email, to send from your CRM to the 30 contacts without a follow-up
Subject: The two questions people ask after the demo
Body: Most teams we show Lumio to ask the same two things: how long the import takes (about an hour) and whether the accountant needs an account (no, they get a read-only link). If either was on your mind, I can set up a 20-minute session with your own data.
Tasks for the 16 others: one call each, created in HubSpot once you approve.

Toby · CMOEffort: Low
Example for a fictional invoicing app. HubSpot is connected here through the universal API connector, not a ready-made card.
LeoApproval requestExample

A pull request on GitHub, waiting for your approval

Tool: GitHub (MCP) · action: create_pull_request Repository: lumio/website · branch: seo/meta-descriptions Title: Add meta descriptions to 14 blog posts Changes: 14 files, one <meta name="description"> each, 140–155 characters, written from each post's first paragraph Why: Search Console shows 9 of these posts on page one with a click rate under 1% [Approve] [Edit] [Refuse]
Example. The pull request is only opened after you click Approve; merging it stays your developer's decision.
ZoeApproval requestExample

Send a new creator to your Make scenario

Tool: “New creator → Airtable” (Make webhook) · action: trigger Payload: { "name": "Clara M.", "platform": "Instagram", "followers": 18400, "niche": "slow living, home", "status": "to contact", "source": "Zoe shortlist, week 45" } [Approve] [Refuse]
Example. Your scenario decides what happens next (a row in Airtable, a Slack message…); Toby only sends the data you approved.

SEO & GEO

Example

Fix the 12 product pages that return a soft 404

Why: The audit found 12 discontinued product pages that show “Product unavailable” with a 200 status. Search Console still lists 9 of them as indexed, and they waste internal links.

Example estimate: cleaner crawl and a few positions back on the category pages

First deliverable, ready to paste

Linear issue, ready to file (after your approval)
Title: Redirect 12 discontinued product pages (soft 404)
Description: Return a 301 to the closest category for each URL below, and remove them from the XML sitemap.
/p/linen-throw-sand → /c/throws
/p/oak-tray-small → /c/trays
… (10 more)
Done when: each URL returns 301 and the sitemap no longer lists it.

Leo · SEO & GEOEffort: Low

Connect any tool

About 2 to 10 minutes

Depending on the route: the address of the tool's remote MCP server (https) and its token, or a link to its API documentation and an API key, or the webhook address of your Zapier, Make or n8n scenario.

  1. 1

    In Toby, open Integrations → Add any tool, then choose MCP server, Its API or Zapier / Make / n8n.

  2. 2

    MCP: pick Stripe, Linear or GitHub, or paste another server's address, then its token. Toby lists the server's tools.

  3. 3

    API: give the tool's name, the link to its API documentation and what you want to do with it. Toby proposes the actions; tick the ones to keep, then add the key (bearer token, header, query parameter or username and password).

  4. 4

    Webhook: name the scenario, paste its address (“Catch Hook” in Zapier, “Custom webhook” in Make, the Webhook node in n8n) and choose who may trigger it.

  5. 5

    Check which agents use the tool, and switch off any action you don't want them to have.

Good to know

  • Token-based MCP servers only, for now. Toby's MCP connection sends a token; remote servers that require you to sign in through a browser window (OAuth) aren't supported yet. Use the tool's API instead when it offers API keys.

  • No HubSpot card yet. HubSpot, Pipedrive, Airtable, Klaviyo and similar tools connect through their API with a key or access token, via the route above.

  • Read-only is decided strictly. An MCP tool runs alone only if its server marks it read-only; on an API, only GET requests can. When in doubt, it asks you.

  • Autopilot never applies here. Actions of a tool you added yourself always wait for your approval, whatever the agent's autonomy.

  • Public https addresses only. Calls stay on the tool's own domain and never reach a private network address. Keys are encrypted (AES-256-GCM) and never shown again.

Security and trustPricing

Frequently asked questions

What is MCP, and why does it matter here?

The Model Context Protocol is an open standard that lets AI agents use a tool's actions. When a tool publishes a remote MCP server, Toby can connect to it in two minutes and give its actions to the right agents, with no custom code.

Can I connect HubSpot to Toby?

Yes, through the API route: give Toby the name, the link to HubSpot's API documentation and an access token (for example from a HubSpot private app with only the scopes you need). Toby proposes actions such as listing deals or reading contacts; any write, like creating a task, waits for your approval. There is no ready-made HubSpot card yet.

Which MCP servers work?

Remote servers reachable over https that accept a token, or no authentication. Stripe, Linear and GitHub are in the list with their official addresses. Local servers that run on your computer, and servers that only allow a browser sign-in, are not supported.

How does Toby know which actions are safe?

For MCP, it trusts only the server's own read-only label. For an API, only GET requests can be read-only. Everything else becomes an approval card. You can also make any read action ask first, or switch it off entirely.

What if the API documentation is hard to read?

Toby reads up to a long documentation page and proposes 3 to 15 actions with the real paths. If the page can't be read, he relies on what is publicly known about that API and stays conservative. You review every action before saving, and can remove any of them later.

Does it cost extra?

No. Every integration, including tools you add yourself, is part of the single $99 a month plan per company. Your own tools may charge for their API usage, as with any integration.

Other integrations

StripeNotionSlack & DiscordMeeting notetakersAll integrations

Use cases and guides

AgenciesSaaS

Bring your whole stack to your AI marketing team

Create your account, paste your URL and get your growth audit, your Brand Brain and your first three recommendations, already prepared.

Start free trial

7-day free trial, then $99/month per company. Cancel anytime. Already have an account? Sign in