Lobstr MCP connector
The Lobstr connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client start crawlers, queue tasks, check runs, and download results from your Lobstr account through Elaichi, with each person signed in as themselves.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Which Lobstr crawlers created the most tasks this week?
Working in Lobstr with Elaichi
-
List all Lobstr plants
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Lobstr to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lobstr MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Lobstr MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Lobstr MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Lobstr MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Lobstr MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Lobstr to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Lobstr through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lobstr is logged.
-
Sales
Queue a fresh lead list before Monday
Ask for a new squid on the Google Maps or LinkedIn crawler, hand it the search URLs as tasks, and start the run so the results are waiting when the team logs in.
-
Marketing
Check whether last night's run finished
Ask how a run went, see how many results it collected and how many credits it used, and grab the download without opening Lobstr.
-
Growth
Add new targets to an existing squid
Paste a handful of URLs or search pages and have them added as tasks to the squid that is already set up, then kick off a run.
-
Operations
Keep an eye on the credit balance
Ask what the account balance is and which recent runs spent the most credits, so nobody discovers an empty balance the morning a campaign starts.
-
Research
Find the right crawler for a source
Ask which crawlers are available in Lobstr and what parameters each one takes before committing to a new squid.
-
Data
Tidy up finished squids and stale tasks
List the squids and tasks the team no longer needs and remove them, with every deletion recorded against the person who asked.
Try asking
- “Which Lobstr crawlers created the most tasks this week?”
- “Create a Lobstr squid for the pricing page crawler.”
- “Show tasks from every Lobstr squid paused since Monday.”
What connecting Lobstr gets you
6 screens from Elaichi, each doing one job for your Lobstr account.
Ask Elaichi to work across your apps.
Which Lobstr crawlers created the most tasks this week?
Create a Lobstr squid for the pricing page crawler.
Show tasks from every Lobstr squid paused since Monday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Lobstr crawlers in plain language.
Answers come from live Lobstr squids, tasks and crawler runs, not stale exports.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Lobstr here.
One org MCP endpoint over OAuth, no SDK work and no shared API key.
ElaichiToolsTool catalog
42 Lobstr tools are ready to call.
Crawlers, squids, tasks, plants and balances are covered without custom code.
ElaichiToolboxesToolboxes
Every team gets its own Lobstr toolbox.
Growth, data and support each see the Lobstr tools their work needs.
ElaichiConnectionsShared connections
Teammates run Lobstr squids without a credential.
Each Lobstr connection shows who linked it and which teams and members share it.
ElaichiAudit logAudit log
Every Lobstr call is written down.
When, who, what happened, type and resource for each Lobstr crawler or task.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Lobstr digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch crawlers
Lobstr
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Lobstr
Queued
Automations
A schedule drafts your Lobstr digest.
Fetch tasks, group them, draft a digest, get approval, post back to Lobstr.
Lobstr health
Refreshed 4 minutes ago · every 15 minutes · from the crawlers collection
Crawlers
1,284 ↓ 12%
Squids
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Crawlers created
Last 14 days
By team
Share of activity
Growth EMEA 34%
Marketing 27%
Data Team 21%
Support 18%
Collections and dashboards
Lobstr crawler health, counted every morning.
Four metrics, 14 days of squids created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lobstr
All three can connect Lobstr to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lobstr tools | Allow or restrict single Lobstr tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lobstr call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Lobstr tools for your AI agents
42 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lobstr, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Lobstr to Claude?
First connect Lobstr in Elaichi: you paste the API key from your Lobstr account settings, and that is the whole sign-in step, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs you into Elaichi, and from then on it can work with your Lobstr crawlers, squids, tasks, and runs.
Does Lobstr work with ChatGPT and Cursor as well as Claude?
Yes. Once Lobstr is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Lobstr once and every client you use picks it up.
What can an AI agent actually do with my Lobstr data?
It can list the crawlers available in Lobstr and their parameters, create or update squids, add tasks such as URLs or search pages, start runs, and report on how a run went, including results collected, credits spent, and the download. It can also check your account balance and remove squids, tasks, or runs you no longer need. Because Lobstr exposes a long list of actions, short concrete asks like "start a run on the Paris restaurants squid" work better than long paragraphs.
Does connecting Lobstr give the AI everything in my account?
No. Every call runs inside the access of the person who signed in, so the agent only sees the Lobstr squids, runs, and balance that person can already see in Lobstr. Elaichi can narrow that further with restrictions, and it can never widen it beyond what the Lobstr account allows.
Can I stop an agent from deleting or changing things in Lobstr?
Yes. Restrictions in Elaichi apply per action, so you can allow reading crawlers and runs while restricting the deletion of squids, tasks, or runs in Lobstr. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Lobstr connection when someone leaves?
Offboarding a person in Elaichi ends their access to Lobstr through every client at once. If they connected Lobstr and shared it with a team, the shared connection keeps working for everyone else. When you do want Lobstr gone, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.
Does the Lobstr MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lobstr is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Lobstr?
Yes. Both let Claude, ChatGPT or Cursor use Lobstr. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lobstr call.
How is Elaichi different from Composio for Lobstr?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lobstr: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lobstr in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot