Backlot plugin
Backlot serves local copies of the Slack, Gmail, GitHub, Jira and S3 APIs with vendor-shaped responses: no accounts or network.
- 224 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The local server listens on a port while it runs and sends anonymous call counts until telemetry is turned off
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/backlotDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The local server listens on a port while it runs and sends anonymous call counts until telemetry is turned off
This is third-party code. Review the repository files before installing.
What it does
Backlot is a local emulator of enterprise APIs: Slack, Microsoft Teams, Gmail, Google Drive, GitHub, Jira, Confluence, Notion, Linear, HubSpot, Fireflies and Amazon S3. One server at `http://127.0.0.1:8000` returns real-API-shaped responses: pagination, errors, authentication and per-document access control. Data comes from a user-supplied JSONL corpus. An agent gets a skill from the repository's plugin, or MCP tools through `backlot mcp`. It can start the server, fill the corpus and see what an official SDK returns, with no vendor accounts.
Who it is for. Integration and RAG-pipeline developers and agent authors who need reproducible test data instead of live Slack, Gmail or Jira accounts.
Good fit when
- An integration is built or upgraded and the OAuth app has not been approved yet.
- CI runs connector tests with no secrets and no network.
- A RAG pipeline or agent is scored on one corpus and runs are compared.
- Tokens from the corpus verify that one user's documents never reach another.
Not a fit when
- You need endpoints outside the supported table: only a documented subset is emulated.
- The test checks real-service behaviour: limits, outages, production quirks.
- The agent needs live company data: Backlot answers only from the loaded corpus.
Example request
Start Backlot, mock a Slack #incidents channel with three messages and show what `conversations.history` returns for it.Limitations
A documented subset of each API is emulated; the endpoint list is in `docs/supported-sources.md`. The authors treat any divergence from the real API as a bug. A running server sends anonymous call counts to `telemetry.brekkylab.com` once a minute; turn it off with `--disable-telemetry`, `BACKLOT_TELEMETRY=false` or `DO_NOT_TRACK=1`. Writes to the corpus are supported for only some vendors. User tokens are deterministic and suitable only for tests.
How to disable. Remove the plugin with the agent's plugin manager and the `backlot` MCP entry, and stop `backlot serve`. Uninstall the package with `pip uninstall backlot`; the corpus lives in SQLite and is deleted separately.
FAQ
Do I need a vendor account?
No. Backlot supplies data and credentials itself and keeps the official SDK's request and response contract. Only the base URL changes in your code.
How do I connect Backlot to an agent?
Install the skill with `claude plugin marketplace add brekkylab/backlot` and `claude plugin install backlot@brekkylab`; Codex has the same `codex plugin` commands. MCP tools come from `claude mcp add backlot -- backlot mcp`.
How do I load my own data?
Prepare a JSONL file with one document per line and run `backlot import my-corpus.jsonl`. The `--dry-run` flag validates the schema and changes nothing.
How do I turn telemetry off?
Run `backlot serve --disable-telemetry` or set `BACKLOT_TELEMETRY=false`. For the MCP bridge `backlot mcp` has the same flag.
Which services does Backlot emulate?
Slack, Microsoft Teams, Gmail, Google Drive with Docs, Sheets and Slides, GitHub, Jira, Confluence, Notion, Linear, HubSpot, Fireflies and Amazon S3. Each service answers under its own path prefix.
Discussion
No questions or reviews yet.
Related
PluginsMCP server: an agent sends GET, POST, PUT, DELETE and PATCH to your REST API and gets back status, headers and body
aimock is a test-API CLI that validates local fixture files before starting a server or exercising the application.
A skill helps an agent configure Dev Proxy to test API errors, rate limiting and delayed responses in an application.
An MCP server that checks whether the agent is really done: drives the real app and returns pass, fail or couldn't tell with the file and line
The terminal client stores API requests as YAML and lets agents send them through an open interface while users watch.
Postman's official MCP server: workspaces, collections, specs and environments straight from your agent
README in short
A table of services with base paths, official-SDK examples, a bring-your-own JSONL corpus and sections on auth, writes and telemetry. Plugins for Claude Code and Codex live in the repository itself.
README badge
Original SKILL.md
--- name: backlot description: Emulate enterprise SaaS knowledge APIs — Slack, Microsoft Teams (msteams), Gmail, Google Drive, GitHub, Jira, Confluence, Notion, Amazon S3, HubSpot, Linear, Fireflies — over a corpus you supply. ---