v0.2.4 — high-intent outreach

Adds a second packaged prompt: high-intent-outreach.

Instead of describing an ICP and filtering for it, you point the workflow at a post
someone in your market already published — a competitor, an adjacent tool, a practitioner
your buyers follow — and work the people who engaged with it.

The assistant proposes whose posts are worth watching, ranked by expected ICP density.
It cannot search or fetch LinkedIn and is explicitly forbidden from inventing post URLs;
you supply them. Preview is free and persists nothing, and the workflow has to give an
honest ICP-match verdict — including telling you not to import — before anything billable runs.

Existing gates are unchanged: separate approval for the billable import, recipient count
read back from the campaign rather than trusted from the import job, explicit sender choice,
revision-bound channel binding, a frozen launch card, and a literal LAUNCH.

Two additions specific to this route:

• Messaging guidance never to reference the source post. "I saw you comment on X" reads as
  surveillance; the workflow writes to the problem in the commenters' own words instead.
• A warning that LinkedIn drops the connection-request note on non-Premium senders, which
  silently removes the context-matched opener this route depends on.

Install

Download sbl-mcp-0.2.4.mcpb and open it with Claude Desktop. Use the byte-identical
sbl-mcp-0.2.4.dxt only for clients that still require the legacy filename.

Both assets are 592,578 bytes with SHA-256
2cdb7b2484d241d690c6dc7f61767c2ed94d67d89e44e012fbbe3288db08a77c. They are unsigned —
verify the hash before installing.

Create an API key at https://app.secondbrainlabs.com/mcp-server and paste it into the
extension's config, never into a chat.

Notes

• 30 tools, unchanged from 0.2.3. Only the bundled prompts differ.
• Bundle materializes reviewed public sbl-stack commit 810b499b812f3fc679a73b12924ae9f4d9e173a1.
• The remote service at https://mcp.sbl.so/mcp still serves 0.2.3. It is redeployed
  separately from these local-client assets; the tool catalog is identical in both.

v0.2.3

sbl-mcp 0.2.3

Release identity

• Private merge commit: 7baeb99e65c7f619ad13c4f734e6c7e224c4f455
• Private merge tree: b9d68f629ad9806eb1a5eedc177c319b66a0445d
• Reviewed public sbl-stack commit: a40784b7f788361a14c9bbe307b9c29a0ff5168c
• Reviewed public sbl-stack tree: 3230e0cf957004890ea51dba1c436bf150121266
• Public release target: SecondBrainLabs-SBL/sbl-stack at a40784b

Highlights

• Complete exact 30-tool sbl.so MCP catalog.
• Adds two tools over v0.2.2: sbl_list_linkedin_channels and sbl_bind_linkedin_channel.
• Canonical remote MCP endpoint: https://mcp.sbl.so/mcp.
• Canonical API-key page: https://app.secondbrainlabs.com/mcp-server.
• Current MCPB manifest and packaging, plus a byte-identical legacy .dxt
  filename for clients that still expect it.
• Exactly one reviewed sbl prompt with controlled launch, replay,
  credential-handling, and human-intervention safety guidance.
• The bundled public skill source is materialized only from the pinned public
  commit; ignored or untracked working-tree content cannot enter the archive.

Safety limits

• Executable orchestration is LinkedIn-only. WhatsApp and iMessage are deferred,
  and the workflow stops before writes for either channel.
• Each run is limited to one run-owned campaign in CREATED state, one explicitly
  chosen sender, and one approved recipient.
• Sender binding uses revision compare-and-set protection.
• Launch requires literal LAUNCH, followed by at most six read-only
  reconciliation checks over no more than two minutes.
• There is no automatic retry. A same-key replay requires unchanged state and a
  fresh literal REPLAY.
• Ending requires a separate literal END; ending cannot recall accepted or
  delivered messages.
• Human-intervention replies use durable sbl_reply_and_resolve, never a
  standalone-send fallback.
• The bearer key is secret. The non-secret idempotency key remains in protected
  state, and only its fingerprint is user-visible.

Install, upgrade, and revoke

• Install sbl-mcp-0.2.3.mcpb through Claude Desktop's extension install UI.
• Use sbl-mcp-0.2.3.dxt only for clients that require the legacy filename.
• To upgrade from v0.2.2, install the v0.2.3 asset and verify 30 tools plus the
  sole sbl prompt. Do not rename or reuse the old artifact.
• Create or revoke keys at https://app.secondbrainlabs.com/mcp-server.
• Enter keys only in sensitive client configuration; never paste them into chat
  or logs.
• Connect LinkedIn at
  https://app.secondbrainlabs.com/settings?tab=communication.
• Remote clients continue using https://mcp.sbl.so/mcp.

Artifacts

• sbl-mcp-0.2.3.mcpb
  • SHA-256: 01073bdaf2596efa1ca22e7b20aef176e641a3dbd8eea4dbb0913eba4dda514e
  • Size: 587392 bytes
• sbl-mcp-0.2.3.dxt
  • SHA-256: 01073bdaf2596efa1ca22e7b20aef176e641a3dbd8eea4dbb0913eba4dda514e
  • Size: 587392 bytes

The two files are byte-identical. Repeated clean builds from the exact private
merge and public source commits reproduced the same hash.

Validation summary

• Locked dependency installation, typecheck, stdio build, and HTTP build passed.
• Focused LinkedIn channel contract and P0-P5 aggregate contracts passed.
• P6 harness passed 19/19 tests.
• Full package contract passed 13/13 tests, including real prompts/list and
  prompts/get, exact 30-tool identity, public-source provenance, deterministic
  rebuilding, and MCPB/DXT byte equality.
• Exact-30 offline stdio smoke passed with the sole sbl prompt.
• Official MCPB manifest validation and bundle inspection passed.

Transparency

This release is unsigned; MCPB inspection reports that state. Verify either asset
using the SHA-256 above before installation. The hosted service is already live at
https://mcp.sbl.so/mcp with version 0.2.3 and 30 tools, so publishing these
local-client assets does not redeploy it.

v0.2.2

sbl.so MCP server v0.2.2

28 tools for driving sbl.so campaigns from Claude (or any MCP client): full campaign lifecycle (create from prompt, read, update components with optimistic concurrency, launch, end), human-intervention queue resolution, retargeting, and three lead sources — CSV upload/import, LinkedIn (Sales Navigator + post-engagement), and native prompt-based lead sessions — plus conversations and analytics.

Verified against production api.sbl.so — including a real end-to-end outbound send through the durable-operations pipeline.

Install (Claude Desktop)

1. Download sbl-mcp-0.2.2.dxt below and double-click it (or Settings → Extensions → Install Extension).
2. Get an API key at sbl.so/api-integration → "Create new key".
3. Paste the key when prompted by the extension. Done — ask Claude to "list my campaigns".

Any other MCP client

Run server/index.js from the extracted bundle over stdio with SBL_API_KEY set. SBL_API_URL defaults to https://api.sbl.so.

Integrity

SHA256(sbl-mcp-0.2.2.dxt) = c1f678566d09c2b6fcddf7ef1911b4b0d221c8d97e52dbe5a98779b53b213c38

Notes: Sales Navigator tools require a Sales Nav seat on the connected account. Outbound tools (send/run/end/human-intervention resolution) require explicit approval arguments — an LLM cannot fire outreach implicitly.

v0.2.0 — zero-runtime install (Node DXT)

Highlights

Install no longer requires Python. Claude Desktop ships Node, so the bundled extension runs out of the box for everyone — paste your API key and you're in. Previously, users without Python ≥3.10 on PATH hit ModuleNotFoundError: No module named 'pydantic_core._pydantic_core' at install time.

What changed

• 🚀 TypeScript rewrite — the MCP server is now a single node binary inside the DXT (@modelcontextprotocol/sdk + zod + fetch). No native modules.
• 📦 30× smaller bundle — sbl-mcp-0.2.0.dxt is 544 KB (was ~15 MB).
• ✅ All 9 tools preserved 1:1 — sbl_list_campaigns, sbl_get_campaign, sbl_create_campaign_from_prompt, sbl_list_campaign_users, sbl_get_conversation, sbl_get_campaign_analytics, sbl_list_human_intervention, sbl_send_campaign_message, sbl_add_user_to_campaign.
• ✅ All sbl-stack skill prompts preserved (sbl, and others as SKILL_MCP.md files are added).

Install

1. Get your API key at sbl.so/api-integration.
2. Download sbl-mcp-0.2.0.dxt from the Assets section below.
3. Double-click → Claude Desktop install dialog → paste the API key → Install.

That's it. No Python. No Node. No terminal.

Upgrade notes

• From 0.1.x: uninstall the old extension in Claude Desktop's extension manager first, then install 0.2.0. Your API key carries over if you re-paste it.
• Claude Code users: the Python pip install sbl-mcp path is being replaced. We'll publish an npm/npx install in 0.3.0 — for now, Claude Desktop is the supported path.

v0.1.0 — first public release

SBL Stack v0.1.0 — your AI campaign manager for sbl.so, ready for Claude Desktop and Claude Code.

Install (Claude Desktop, ~2 min, no terminal)

1. Get your API key — sbl.so/api-integration → "Create new key" → copy the sk_live_… value.
2. Download sbl-mcp-0.1.0.dxt below (under Assets).
3. Double-click the file → Claude Desktop opens an install dialog → paste the key → Install.
4. (Optional) — On the repo page click Code → Download ZIP and upload it as a skill in Claude Desktop's Skills settings to get the /sbl orchestration on top of the raw tools.

See the README for the Claude Code (terminal) path.

What you get

• 9 MCP tools — sbl_list_campaigns, sbl_get_campaign, sbl_create_campaign_from_prompt, sbl_list_campaign_users, sbl_get_conversation, sbl_get_campaign_analytics, sbl_list_human_intervention, sbl_send_campaign_message, sbl_add_user_to_campaign.
• 6 sub-skills when you upload the zip — sbl, sbl-create, sbl-optimize, sbl-triage, sbl-playbook, sbl-retro, sbl-science.
• API-key auth — long-lived, revocable, manageable from sbl.so/api-integration. No JWT pasting, no passwords in config files.

Compatibility

• Claude Desktop ≥ 0.10
• Python ≥ 3.10 (Claude Desktop spawns the bundled MCP server)
• macOS, Linux, Windows