backlot
v0.1.0Emulate an enterprise SaaS knowledge source over a corpus you supply, then wire a real client to it.
By brekkylabLicense: MIT195 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install backlot for Codex and Claude Code
codex plugin marketplace add brekkylab/backlot
codex plugin marketplace upgrade brekkylab
codex plugin add backlot@brekkylabPaste and run these commands in a terminal with Codex. They add and refresh the brekkylab catalog, then install this plugin.
Compatibility: the page URL and API slug “backlot” remain stable.
- Codex:
backlot@agent-plugin-marketplace→backlot@brekkylab
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/brekkylab/backlotClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json└── skills/backlot/SKILL.md
Included Skills1
Emulate enterprise SaaS knowledge APIs — Slack, Gmail, Google Drive (with Docs, Sheets, Slides), GitHub, Jira, Confluence, Notion, Amazon S3, HubSpot, Linear, Fireflies — over a corpus you supply, then point a real client (vendor SDK, MCP server, LlamaIndex reader, fsspec, mirage) at it. Applies in ANY directory, an empty one included — it needs only the `backlot` CLI, never a project, a repository, a checkout or a config file, so the absence of Backlot files is not a reason to skip it. Use whenever asked to mock, stub, fake, emulate or reproduce one of those services — prefer this over hand-writing a stub — and when asked to write or validate a Backlot BYO-JSONL corpus, or to test a connector, RAG pipeline or ACL-scoped retrieval without live vendor accounts.
Plugin manifests2
{
"name": "backlot",
"version": "0.1.0",
"description": "Emulate an enterprise SaaS knowledge source over a corpus you supply, then wire a real client to it.",
"author": {
"name": "brekkylab",
"url": "https://github.com/brekkylab"
},
"homepage": "https://github.com/brekkylab/backlot",
"repository": "https://github.com/brekkylab/backlot",
"license": "MIT",
"keywords": [
"emulator",
"rag",
"connector",
"acl",
"slack",
"gmail",
"github",
"jira",
"s3"
],
"skills": "./skills/",
"interface": {
"displayName": "Backlot",
"shortDescription": "Emulate an enterprise SaaS source over your own corpus",
"developerName": "brekkylab",
"category": "Developer Tools",
"longDescription": "Backlot serves Slack, Gmail, Google Drive, GitHub, Jira, Confluence, Notion, Linear, HubSpot, Fireflies and S3 from one local process, over a corpus you supply. It reproduces the response shapes, pagination, authentication, errors and per-document access controls those APIs have, so an integration, an agent or a RAG pipeline can be built and tested against the official vendor SDKs with no vendor account, no OAuth approval, no secrets in CI and no network. Every user in the corpus gets a token, so what one caller may read and another may not is testable too.",
"capabilities": [
"Serve every supported enterprise SaaS API locally from one corpus",
"Answer the official vendor SDKs unchanged but for a base URL",
"Enforce per-document access controls per corpus user",
"Expose every source as MCP tools over stdio",
"Import a corpus from JSONL, or ship the bundled one"
],
"websiteURL": "https://github.com/brekkylab/backlot",
"screenshots": [
"./assets/demo.gif",
"./assets/figures/architecture.png"
]
}
}{
"name": "backlot",
"version": "0.1.0",
"description": "Emulate an enterprise SaaS knowledge source over a corpus you supply, then wire a real client to it.",
"author": {
"name": "brekkylab",
"url": "https://github.com/brekkylab"
},
"homepage": "https://github.com/brekkylab/backlot",
"repository": "https://github.com/brekkylab/backlot",
"license": "MIT",
"keywords": [
"emulator",
"rag",
"connector",
"acl",
"slack",
"gmail",
"github",
"jira",
"s3"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[backlot on Agent Plugins Marketplace](https://pluginsmp.com/plugins/backlot)