[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_116":117},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_56":-5,"_57":49,"_58":59,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":79,"_80":-5,"_81":-5,"_82":-5,"_83":49,"_84":-5,"_85":59,"_86":87,"_88":89,"_90":91,"_92":93,"_94":95,"_96":97},"apiUrl","https://odel.app/api","creator","leadbay","moduleId","mcp","@leadbay/mcp","displayName","Leadbay","tagline","AI lead discovery, qualification, and outreach prep on your Leadbay account.","iconKey","https://leadbay.ai/icon-192.png","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://mcp.leadbay.app/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1783340615000,"updatedAt",1788410758000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.leadbay%2Fleadbay-mcp","sourceVerified",true,"sourceMissingSince","importedAt","upstreamStars",0,"upstreamUpdatedAt",1788394779000,"detectedTransport","streamable-http","detectedAuthType","oauth","probeStatus","ok","lastProbedAt",1788068557000,"githubRepoUrl","https://github.com/leadbay/mcp","githubRepoFullName","leadbay/mcp","releaseId","ext-leadbay-mcp","version","0.34.0","descriptionMarkdown","

\n $\"Leadbay$ \n

\n\n

Leadbay MCP

Leadbay MCP connects your AI assistant to your Leadbay account, so you can work your leads by simply asking.

Pull leads, qualify them, draft outreach, and log activity — in plain language. Your assistant acts on your real Leadbay data, with your permissions, just as you would in the app.

Everything is personalized — nothing to configure. Leadbay runs advanced AI on your website and market data to source and score leads against your target profile, so outreach becomes meaningful connection instead of senseless spamming.

Tell your assistant which leads to prospect, connect your channels, and it sources contacts from Leadbay and handles outreach on your behalf. Enjoy the outreach you no longer have to do.\n

\n\n> **MCP** stands for *Model Context Protocol* — an open standard that lets AI assistants like Claude securely connect to external tools and data. This server is open source and lives at [github.com/leadbay/mcp](https://github.com/leadbay/mcp).\n\n---\n\n## How Leadbay thinks (mental model for your agent)\n\n- **Inbox, not a database.** Each day your user logs back in, a fresh batch of leads is delivered. Batch size is paced by how many leads the user has actually acted on recently — some workflows produce a big stream of smaller prospects, others a narrow stream of bigger ones. Pulling more won't produce more; acting on leads does.\n- **Two scoring layers.** Every lead ships with a basic `score` (firmographic — already decent, usually correlates with AI). Roughly the top 10 of each batch are also AI-qualified (targeted web research + qualification questions → `ai_agent_lead_score`). Leads below the top 10 aren't worse — the system is saving resources. The agent can request deeper qualification (`leadbay_bulk_qualify_leads`) or contact enrichment (`leadbay_enrich_titles`) on any lead that looks worth it.\n- **Daily rhythm.** The agent works best as a daily check-in: pull fresh leads, skim the auto-qualified top, deepen 1-3 promising ones, propose outreach, then log what actually got sent via `leadbay_report_outreach`. If your host supports scheduling, set up a daily run.\n\n---\n\n# For users\n\nGet Leadbay MCP running inside your AI assistant in a couple of minutes. No coding required.\n\n> **New to Leadbay?** The friendly, screenshot-driven walkthrough — what a lens is, how scoring works, and the full MCP setup for every assistant — lives in the **[Leadbay user guide](https://docs.leadbay.ai/leadbay-mcp/what-is-leadbay-mcp)**. This README is the technical companion.\n\n> **No Leadbay account yet?** [Create one here](https://wow.leadbay.ai/?register=true) first — you'll need it to sign in during setup.\n\n## Connect on the web (no install)\n\nIf you use Claude on the web, Claude Desktop, or ChatGPT, the fastest path is a **custom connector** — no terminal, no tokens to copy. Add one URL and sign in with your browser:\n\n- **Name:** `Leadbay`\n- **URL:** `https://mcp.leadbay.app/mcp` — one URL for every region (`/fr/mcp` remains a compatibility alias)\n- **On ChatGPT, use `https://mcp.leadbay.app/chatgpt/mcp` instead.** Same server, same sign-in, same leads — but the assistant cannot generate a top-up link or open your billing page there, because the OpenAI app directory does not allow an app to sell credits. Buy credits or change your plan in your Leadbay account instead.\n\nIn Claude: **Settings → Connectors → + → Add custom connector**, paste the URL, then open the connector and **Connect**. Sign in with Leadbay, click **Approve**, and you're linked. The server handles OAuth in-app; updates are automatic — you never touch a config file.\n\n## Install in Claude Desktop (one-click bundle)\n\nPrefer a bundled desktop extension? Grab the one-click file.\n\n**1. Download the extension**\n\n👉 **[Download the latest Leadbay MCP for Claude (.dxt)](https://github.com/leadbay/mcp/releases/latest)**\n\nOn the releases page, click the file ending in **`.dxt`** to download it.\n\n**2. Install it**\n\nDouble-click the downloaded `.dxt` file. Claude opens and shows an install dialog — click **Install**, and you're done.\n\n**If the double-click doesn't open Claude**, install it manually:\n\n1. Open Claude and go to your **profile → Settings → Extensions**.\n2. Open **Advanced settings**.\n3. Choose **Install extension…** and select the `.dxt` file you downloaded.\n\n**3. Sign in**\n\nClaude will prompt you to connect Leadbay. Sign in with your Leadbay account and you're ready — just ask your agent for leads.\n\n## Using a local assistant?\n\nLeadbay MCP also works with Claude Code, Claude Desktop, Cursor, and Codex. The **universal installer** sets everything up for you and lets you sign in with Leadbay.\n\nRequires [Node.js 22+](https://nodejs.org). Then run:\n\n```bash\nnpx -y -p @leadbay/mcp@latest installer\n```\n\nIt opens in your browser where you click **Sign in with Leadbay**, then pick which assistants to connect. Works on macOS, Windows, and Linux.\n\n**To uninstall**, run the same installer with `--uninstall`:\n\n```bash\nnpx -y -p @leadbay/mcp@latest installer --uninstall\n```\n\nIt opens an uninstall window showing only the assistants that have Leadbay connected — pick the ones to remove and click **Remove selected**. It only removes Leadbay; your other settings and connections are left untouched.\n\n## Ask for your first leads\n\nOpen a new conversation and describe the outcome — you never name a tool, just say what you want, the way you'd ask a colleague:\n\n> *Show me today's leads and tell me which two are worth opening first.*\n\nA successful first reply is a **ranked table of prospects**, not a wall of text: each row has a fit score, a one-line why-it-fits, and the best contact to reach. Then keep going:\n\n> *Research the top one — is it a fit for us?*\n\n> *Draft me an outreach email to them.*\n\n> *I just emailed them. Log it as outreach.*\n\n---\n\n# For developers\n\nEverything below is for contributors and anyone running Leadbay MCP from source or wiring it into automation.\n\n## Install a local version with the custom installer\n\nTo run your local checkout (instead of the published package), first build it from source:\n\n```bash\npnpm install\npnpm prompts:build\npnpm -r build\n```\n\nThen point the installer at your freshly built version with `--local`:\n\n```bash\npnpm --filter @leadbay/mcp installer -- --local\n```\n\n`--local` registers the MCP client(s) against the build in your working tree rather than `@leadbay/mcp@latest`. OAuth is handled automatically — you don't need to pass `--oauth`. The installer asks per-target before writing anything.\n\n## All install methods\n\nEvery supported way to connect Leadbay MCP:\n\n| Method | Command / action | Platforms | Notes |\n|--------|------------------|-----------|-------|\n| **Hosted connector (no install)** | Add custom connector → `https://mcp.leadbay.app/mcp` (all regions) | Claude web / Desktop | Browser OAuth in-app. Nothing to install; auto-updates. |\n| **Hosted connector — ChatGPT** | Add custom connector → `https://mcp.leadbay.app/chatgpt/mcp` | ChatGPT | Same server; the top-up and billing tools are not registered (OpenAI directory rule). |\n| **`.dxt` / `.mcpb` bundle** | Download from [Releases](https://github.com/leadbay/mcp/releases/latest), double-click → **Install** | Claude Desktop | One-click desktop extension. |\n| **Guided installer (GUI)** | `npx -y -p @leadbay/mcp@latest installer` | macOS, Windows, Linux | Browser wizard: sign in with Leadbay, pick clients. Works for everyone. |\n| **Local dev build** | `pnpm --filter @leadbay/mcp installer -- --local` | macOS, Windows, Linux | Registers clients against your local build. OAuth automatic. Build from source first (above). |\n| **Claude Code plugin marketplace** | `/plugin marketplace add leadbay/mcp` then `/plugin install leadbay@leadbay-mcp` | Claude Code | Registers the MCP server **and** installs auto-triggering skills. |\n\n### What each installer writes per client\n\nThe GUI/CLI installers only touch clients that are actually installed on the machine:\n\n| Client | Installer behavior |\n|--------|--------------------|\n| Claude Code | Registers/removes `leadbay` with `claude mcp add/remove --scope user` |\n| Claude Desktop | Writes/removes only the `mcpServers.leadbay` entry in `claude_desktop_config.json` |\n| Cursor | Writes/removes only the `mcpServers.leadbay` entry in Cursor's MCP config |\n| Codex | Writes/removes only the `[mcp_servers.leadbay]` block in `~/.codex/config.toml` and the Leadbay-managed shell export block |\n\n### Claude Code plugin marketplace\n\n```bash\n/plugin marketplace add leadbay/mcp\n```\n\n```bash\n/plugin install leadbay@leadbay-mcp\n```\n\nClaude Code prompts for Leadbay auth/config. Registers the MCP server **and** installs a set of skills that auto-trigger on natural-language asks — including `leadbay_daily_check_in` (\"get my leads today\"), `leadbay_research_a_domain` (\"research acme.com\"), `leadbay_followup_check_in`, `leadbay_qualify_top_n`, `leadbay_refine_audience`, `leadbay_log_outreach`, `leadbay_import_file`, `leadbay_plan_tour_in_city`, `leadbay_prospecting_overview`, `leadbay_extend_my_lens`, `leadbay_setup_team_prospecting`, `leadbay_build_campaign`, and `leadbay_work_campaign`. Each `SKILL.md` is generated by `@leadbay/promptforge` from the same source as the MCP prompts, so the two surfaces never drift.\n\n### Uninstall\n\n```bash\nnpx -y -p @leadbay/mcp@latest installer --uninstall\n```\n\nOpens the uninstall wizard — only shows clients that already have Leadbay MCP configured. De-registers Claude Code, strips the JSON stanza from Claude Desktop / Cursor configs, removes the `[mcp_servers.leadbay]` TOML block from Codex, and strips the managed `export LEADBAY_*` block from `~/.zshrc` / `~/.bashrc`. Uninstall is scoped to Leadbay — it never rewrites unrelated client settings or removes other MCP servers.\n\n## Tools\n\nYour assistant calls these on your behalf — you never call them directly. You ask in plain language (\"show me today's leads\", \"research acme.com\", \"log that I emailed Jane\") and the agent picks the right tool. The default surface below is always exposed; the [full per-tool reference](https://docs.leadbay.ai/leadbay-mcp/tools-reference) lives in the user guide.\n\n### Read-only (always on)\n\nThese never modify your account, so they're always safe to allow.\n\n**Discover & follow up**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_pull_leads` | Pull today's fresh batch of scored, ranked leads |\n| `leadbay_pull_followups` | Pull the leads that need a follow-up action |\n| `leadbay_account_status` | Check quota, credits, and account state |\n| `leadbay_scan_portfolio_signals` | Scan your existing leads for a web signal in one pass (\"which of my leads acquired a company since 2025?\") — no quota burn |\n\n**Research a company**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_research_lead_by_id` | Deep-dive research card for a known lead — details + AI qualification + contacts in one response |\n| `leadbay_research_lead_by_name_fuzzy` | Look up a lead by company name or domain when you don't have its ID |\n| `leadbay_account_history` | Full history on one account — current AI signals + all notes + interaction timeline, in one call (\"why has this account resurfaced?\") |\n| `leadbay_prepare_outreach` | Build a personalized outreach brief for a lead |\n\n**Travel & field sales**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_followups_map` | Geo-cluster your follow-ups on a map for travel planning |\n| `leadbay_tour_plan` | Build a visit itinerary for an upcoming trip to a city |\n\n**Campaigns**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_list_campaigns` | List your existing campaigns |\n| `leadbay_campaign_progression` | Show a campaign's funnel metrics |\n| `leadbay_campaign_call_sheet` | Pull the call sheet for a campaign |\n\n**Lenses, audience & qualification**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_list_sectors` | List the real sector taxonomy labels — so you (and the agent) name sectors correctly, no guessing |\n| `leadbay_recall_ordered_titles` | Recall the job titles previously enriched by the org (use before `leadbay_enrich_titles`) |\n| `leadbay_seed_candidates` | Read-only discovery surface for building a bigger lens |\n| `leadbay_get_qualification_questions` | Retrieve the org's AI-agent qualification questions (how leads are scored) |\n| `leadbay_get_lead_custom_fields` | Retrieve the custom-field values stored on one lead |\n| `leadbay_list_mappable_fields` | List the CRM fields you can map an import onto |\n\n**Imports & jobs**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_import_status` | Status of a running import job |\n| `leadbay_qualify_status` | Status of a running qualification job |\n| `leadbay_bulk_enrich_status` | Status of a running enrichment job |\n| `leadbay_resolve_import_rows` | Map imported rows back to their lead IDs |\n\n**Team, billing & product signals**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_team_activity` | Manager-facing per-rep leaderboard + activity trend (non-admins are scoped to themselves) |\n| `leadbay_create_topup_link` | Generate a Stripe top-up link (you pay in your browser — nothing is charged automatically) |\n| `leadbay_open_billing_portal` | Open the billing portal |\n| `leadbay_acknowledge_notification` | Clear a terminal bulk-job notification so it stops resurfacing |\n| `leadbay_report_friction` | Report a problem to the Leadbay team — asks you first, and shows you what was sent (no account change) |\n| `leadbay_artifact_kit` | Fetch the headless view-models the agent uses to build an interactive HTML artifact |\n\n### Write actions (on by default since 0.3.0; set `LEADBAY_MCP_WRITE=0` to disable)\n\nThese take action on your account. Every action is one you could take yourself in the app — there's nothing destructive at the platform level, and deletes are confirm-gated.\n\n**Qualify & enrich**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_bulk_qualify_leads` | Trigger AI qualification on a batch of leads |\n| `leadbay_enrich_titles` | Enrich contacts by job title |\n| `leadbay_enrich_contacts` | Enrich one specific person (email / phone) — the contact you name, not a job title |\n\n**Outreach & activity**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_report_outreach` | Log an outreach action (call, email, meeting) — required after every contact |\n| `leadbay_add_note` | Add a note to a lead |\n| `leadbay_like_lead` | Mark a lead as liked — teaches your taste profile |\n| `leadbay_dislike_lead` | Mark a lead as disliked — teaches your taste profile |\n\n**Contacts**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_add_contact` | Add a person to a company (name + optional LinkedIn / title / email / phone) |\n| `leadbay_remove_contact` | Remove a contact you added |\n| `leadbay_pin_contact` | Pin a contact as the priority on a company |\n| `leadbay_unpin_contact` | Unpin a contact |\n| `leadbay_update_contact` | Edit a contact's details (title, email, LinkedIn…) |\n\n**Lenses & audience**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_my_lenses` | List, switch, rename/describe, or delete your lenses (delete is confirm-gated) |\n| `leadbay_new_lens` | Create a named lens with sector / company-size (and optional location) criteria |\n| `leadbay_adjust_audience` | Edit a lens's audience (\"stop showing me companies over 50 employees\"); pass `lensName` to edit a lens by name |\n| `leadbay_extend_lens` | Fill your current lens with more leads on demand (subject to a daily refill quota) |\n| `leadbay_refine_prompt` | Refine the qualification prompt that scores your leads |\n| `leadbay_answer_clarification` | Answer a clarification question Leadbay asked about your audience |\n\n**Imports & campaigns**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_import_leads` | Import a list of company domains |\n| `leadbay_import_and_qualify` | Import a list and immediately qualify it |\n| `leadbay_create_campaign` | Create a new campaign |\n| `leadbay_add_leads_to_campaign` | Add leads to a campaign |\n| `leadbay_remove_leads_from_campaign` | Remove leads from a campaign |\n\n**Custom fields & qualification questions**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_create_custom_field` | Create a custom CRM field (e.g. to preserve a source-system ID) |\n| `leadbay_update_custom_field` | Rename or retype a custom field |\n| `leadbay_delete_custom_field` | Delete a custom field (confirm-gated) |\n| `leadbay_set_qualification_questions` | Modify the org's AI-agent qualification questions (max 5; removals confirm-gated) |\n\n**Feedback**\n\n| Tool | Description |\n|------|-------------|\n| `leadbay_send_feedback` | Send a message to the Leadbay team (same inbox as the in-app feedback form) |\n\n### Advanced granular tools (gated by `LEADBAY_MCP_ADVANCED=1`)\n\nLow-level, single-API-call tools for power users and integrations (`leadbay_discover_leads`, `leadbay_get_lead_profile`, `leadbay_get_contacts`, `leadbay_list_lenses`, …). Off by default; enable by setting `LEADBAY_MCP_ADVANCED=1` in the MCP server's env. See [`packages/mcp/README.md`](https://github.com/leadbay/mcp/blob/main/packages/mcp/README.md#8-advanced) for the full list.\n\n## How it works\n\nThe MCP server automatically uses your **active lens** (the last lens you used in Leadbay). Just call `leadbay_pull_leads` and it works — no lens configuration needed.\n\nYou can also manage lenses directly from chat: `leadbay_my_lenses` lists them and switches/renames/deletes; `leadbay_new_lens` creates a named one with sector/size criteria; and `leadbay_adjust_audience` edits an existing lens (the active one, or any lens by name via `lensName`). Sector names resolve against the live taxonomy — `leadbay_list_sectors` surfaces the real labels.\n\n`leadbay_research_lead_by_id` bundles multiple API calls (lead details + AI qualification + contacts) into a single response. If some data isn't available yet, it returns partial results instead of failing.\n\n## Configuration\n\n| Env var | Required | Description |\n|---------|----------|-------------|\n| `LEADBAY_TOKEN` | Yes | Local OAuth bearer credential (set by the installer) |\n| `LEADBAY_REGION` | Yes | `us` or `fr` |\n| `LEADBAY_MCP_WRITE` | No | Set to `0` to disable write tools (default: on since 0.3.0) |\n| `LEADBAY_MCP_ADVANCED` | No | Set to `1` to expose granular tools (default: off) |\n| `LEADBAY_BASE_URL` | No | Override API URL (for staging/dev) |\n| `LEADBAY_TIMEOUT_MS` | No | Backstop deadline for one outbound request, in ms (default: 600000) |\n\nThe full environment-variable reference (telemetry, mock mode, logging, timeouts) is in [`packages/mcp/README.md`](https://github.com/leadbay/mcp/blob/main/packages/mcp/README.md#environment-variables).\n\n## Workflows\n\nThe canonical inventory of what the MCP supports — supported / partial / planned / blocked-on-backend — is **[WORKFLOWS.md](https://github.com/leadbay/mcp/blob/main/WORKFLOWS.md)**. Use it to triage incoming asks: find the row that matches, or add a new one. A small audit asserts every cited tool/prompt and test path is real, so the table can't silently drift.\n\nQuick taste:\n\n```\nleadbay_pull_leads → leadbay_research_lead_by_id → leadbay_prepare_outreach # discover & research\nleadbay_pull_followups → leadbay_followups_map → leadbay_prepare_outreach # travel/geo follow-ups\nleadbay_import_leads → leadbay_bulk_qualify_leads # import & qualify\n```\n\n## Requirements\n\n- Node.js 22+\n- A [Leadbay account](https://wow.leadbay.ai/?register=true)\n\n## Privacy Policy\n\nThe Leadbay MCP server accesses your Leadbay account data (leads, contacts,\ncampaigns, notes) on your behalf through the Leadbay API, using a token you\nauthorize via OAuth. It does not read your conversation history, Claude memory,\nor local files. Data handling is governed by the Leadbay\n[privacy policy](https://www.leadbay.ai/privacy-policy) and\n[terms of use](https://www.leadbay.ai/terms-of-use).\n\n## Building from source\n\n```bash\npnpm install\n```\n\n```bash\npnpm prompts:build\n```\n\n```bash\npnpm -r build\n```\n\n```bash\npnpm -r test\n```\n\n```bash\npnpm -r typecheck\n```\n\n### Test tiers\n\n- **Unit tests** (`packages/core/test/unit/`) — error-code mapping, tool branches. Use `mockHttp` from `test/harness.ts` to stub `node:https`. No network required.\n- **Integration tests** (`packages/core/test/integration/`) — opt-in. Set `LEADBAY_TEST_TOKEN` and run `pnpm test:smoke`.\n- **Audit tests** (`packages/mcp/test/audit/`) — assert tool descriptions, routing blocks, and WORKFLOWS.md consistency at build time. Always run on CI.\n- **Eval tests** (`packages/mcp/test/eval/`) — LLM-graded scenarios. Gated by `EVAL=1`.\n\nSee [`CLAUDE.md`](https://github.com/leadbay/mcp/blob/main/CLAUDE.md) for the full contributor guide: tool structure, test conventions, build pipeline, and how to add a new tool.\n\n## Publishing\n\nAll releases are tag-driven — **never run `npm publish` locally.** GitHub Actions owns publishing.\n\n1. Bump `packages/mcp/package.json#version` + add CHANGELOG entry, land PR.\n\n```bash\ngit checkout main && git pull\n```\n\n```bash\ngit tag mcp-v0.x.0\n```\n\n```bash\ngit push origin mcp-v0.x.0\n```\n\n2. Watch the release workflow: `preflight-npm → publish-mcp`.\n\nFor dry runs: Actions → `release` → \"Run workflow\" → `package: mcp`, `dry_run: true`.\n\nFull runbook (auth setup, failure modes, manual re-runs): [`RELEASE.md`](https://github.com/leadbay/mcp/blob/main/RELEASE.md).\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays","iconType","image","upstream",{"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":111},"requiredSecrets",[],"tags",[],"assets",[],"stats",{"_98":59,"_99":59},"ratingAvg","reviewCount","topics",[],"license","MIT","language","TypeScript","registryName","io.github.leadbay/leadbay-mcp","homepage","https://leadbay.ai","packages",[112],{"_113":114,"_115":22,"_76":77},"registryType","npm","identifier","ENV",{"_118":119,"_120":121,"_122":123},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]