Busabase for Lindy

Connect Lindy to Busabase

Lindy is an AI employee / personal executive assistant you work with over iMessage, SMS, email and Slack; it connects to 1,500+ integrations and any hosted MCP server.

Busabase MCP server

https://busabase.com/api/mcp

Read the Lindy documentation

Busabase

MCP connector

Set it up

Hosted chat has no shell and no file system, so a connector is the way in.

Add the server

Point your chat client at the Busabase MCP endpoint.

Sign in

Complete OAuth in the browser — no client id or secret to create.

Pick the smallest permission

changeRequest lets the agent propose but never merge.

Verify

Ask the agent to call auth_verify before it does any work.

Step by step

This host has no shell, so a connector is the only way in.

At a glance

Vendor: Lindy
How it connects: MCP + OAuth · MCP + API key
Transport: Streamable HTTP
Authentication: Unknown
Config file: Integrations → + Add → MCP

In Lindy go to Integrations, click + Add and choose MCP.
In Connect MCP server, paste the Server URL https://busabase.com/api/mcp and set a Display name such as Busabase.
Leave credentials empty: per Lindy's docs, "servers that run their own OAuth flow, need nothing here". If you prefer an API key, open Advanced and send it as an Authorization bearer token (create the key in Busabase Settings → API Keys with the smallest permission and a finite expiry).
Click Connect. Lindy reads the tool catalog and turns every supported tool on; switch off what you do not need under Actions.
Ask Lindy to call auth_verify on Busabase.

Lindy needs a public HTTPS streamable-HTTP endpoint; Busabase Cloud already is one.

Lindy MCP servers documentation

Known gotchas

Docs say Lindy connects to "hosted servers that expose a public HTTPS streamable-HTTP endpoint", so localhost/Personal Desktop needs Busabase's Tunnel first. Docs do not say whether Lindy's OAuth client uses dynamic registration or which scopes it requests (Busabase grants `mcp` to generic scopes). Lindy's 'Skills' are a proprietary in-app playbook feature (rolling out behind feature flags), not SKILL.md folders. Browser use is Pro and up; no documented shell. Plans are Plus/Pro/Max; docs do not restrict MCP by plan; free credits last 7 days.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	Lindy	Claude Code	Cursor
Type	Web chat	Terminal agents	AI editors
Recommended path	MCP connector	Agent Skill	Agent Skill
How it connects	MCP + OAuth · MCP + API key	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	Unknown	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Oct 21, 2026

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.

Browse every agent

Busabase MCP server

https://busabase.com/api/mcp