Plugins
Connect bots to GitHub, Jira, Notion, Stripe, a browser, and dozens more services.
A plugin gives bots tools for a service or an app. Under the hood a plugin is one or more MCP servers.
The marketplace
Click the marketplace icon (four circles) at the bottom right of the sidebar, or choose File › Marketplace… (⌘⇧M). It lists Featured Plugins and Featured Bots first, then everything by category. View all under a featured section lists every plugin or every bot. Search finds plugins and bots together.
Lorca ships with these plugins:
| Category | Plugins |
|---|---|
| Productivity | Linear, Notion, Atlassian (Jira and Confluence), Zapier, Todoist, ClickUp, Airtable |
| Communication | Granola, Fireflies, Resend |
| Design | Canva, Miro, Webflow |
| Code | GitHub, Sentry, Cloudflare, GitLab, Netlify, Railway, Expo |
| Data | Supabase, Neon, PostHog, Mixpanel, Amplitude |
| Sales | Attio, Close, Apollo.io |
| Finance | Stripe, PayPal, Mercury |
| Research | Context7 (library documentation), Browser (a headless browser the bot drives), Exa (web search), DeepWiki, Hugging Face |
| Support | Intercom |
Browser, Context7, DeepWiki, Exa, and Hugging Face work without an account. Zapier reaches the apps that have no plugin here, such as Gmail, Google Calendar, and Slack. The bots in the marketplace are ready-made teammates; see Bots.
Plugins are installed per Runner. Every bot on that computer can use every plugin installed there. Secrets and sign-ins stay on that Runner; your other devices only see the plugin's name and state.
On-demand tools
A bot starts a turn with only a small catalog of the plugins installed on its Runner. Lorca connects an MCP server and gives the model matching tool schemas only when the task needs that capability. The selected tools remain available for the rest of that turn, while unrelated plugin catalogs stay out of the model's context.
Install a plugin
- From a chat: ask the bot. "Install the GitHub plugin." It finds the plugin and posts a card asking your permission before it installs anything.
- From the app: open the marketplace and click Add beside a plugin. It installs on the Runner shown at the top of the marketplace; pick another one there if you have more. Add from Plugins… in a bot's inspector opens the marketplace on that bot's Runner, and Settings › Plugins on the Runner picked in the toolbar.
You can install a plugin on any Runner from your phone. The request travels to that computer encrypted.
Sign in
A plugin that needs an account posts a sign-in card in the chat: Sign in or Not now.
- GitHub shows a short code and a link (on the plugin's sheet too, when you sign in there). Enter the code on github.com from any device.
- Other services open a sign-in page in the browser on the Runner. If you are on another device, the card tells you to finish there.
Some plugins take a pasted token instead, which also suits a Runner with no browser: a GitHub personal access token, or an API key or token for Airtable, Cloudflare, Fireflies, Neon, PostHog, Resend, Stripe, Supabase, or Zapier. Context7 and Exa take an optional API key that raises their free limits, and Hugging Face a token that brings your own account. Fill it in on the plugin's sheet. Secret fields are write-only: once saved they are never shown again.
What a plugin may do
Reading runs right away. Anything that changes something, such as creating an issue, posting a comment, or deleting a page, goes through Auto-review, and asks you first when it should.
Manage a plugin
A plugin's sheet shows its state, its sign-in, its settings, the actions you have always allowed (with Reset), and Remove. Marketplace plugins update themselves and keep your settings and sign-ins.