Labs · ConnectorStack · personal CRM · MCP

ConnectorStack

A browser-side proxy that hands your own LinkedIn, Luma, and Partiful data to Claude, so you never lose touch with the people who matter.

● live/ connectorstack.fly.dev ↗/ designed & built by Wolf Works /Python · FastMCP · Chrome extension
connectorstack.fly.dev
ConnectorStack interface
01

The problem

Your relationships live locked inside other companies' apps.

The people you should reconnect with do not vanish all at once. They just stop showing up in the feeds you check. LinkedIn, Luma, and Partiful each hold a slice of who you know, none of it searchable together, none of it yours to query. So the follow-up you meant to send six weeks ago quietly never happens.

02

What it does

31 tools, one login
01 · your session

Your browser does the reading, not our server.

Every fetch runs inside your own logged-in tab. A Manifest V3 extension reads through chrome.cookies, throttled with jittered delays; your credentials never leave the browser and nothing is scraped server-side.

02 · the tools

Thirty-one tools your agent can call.

Search every message, find your last conversation with someone, draft a follow-up, surface who you have not spoken to in months. Read tools hit a local SQLite cache; write and sync tools route back through your session.

03 · voyager

We read LinkedIn the way LinkedIn's own site does.

ConnectorStack reverse-engineered LinkedIn's undocumented Voyager API from live traffic, then parses every response defensively, so a markup change loses one field instead of taking the connector down.

04 · export

Your graph, in your warehouse.

An optional read-only export streams approved connector data into BigQuery, incremental and keyset-paginated. The same relationships feed a real data pipeline, and the connector tables stay untouched sources.

03

One question in, four people out

you say
"who haven't I talked to in 3 months that I should?"
connectorstack
↳ searched: LinkedIn · Luma · Partiful
↳ last contact older than: 90 days
↳ ranked by: past reply rate · shared events
✓ found 4 people worth a message. draft one?
04

How it's built

The hard part is reading someone else's app without breaking their rules, or yours.

A FastAPI server holds a persistent WebSocket to the Chrome extension. The extension does every read inside your logged-in session with two-to-six-second jittered delays, and the server caches results in aiosqlite for fast MCP reads. A Node .mcpb relay wires it into Claude Desktop. Every platform response is parsed defensively, so the connectors degrade one field at a time instead of falling over. It is in early beta, live, and deployed on Fly.

RuntimePython 3.11 · FastAPI · FastMCP
Dataaiosqlite on a Fly volume
AuthAuthentik OIDC · API tokens
ClientsMV3 Chrome ext · Node .mcpb relay
ConnectorsLinkedIn · Luma · Partiful · 31 tools
DeployDocker → Fly.io · 196 tests

This is what six weeks looks like

We built ConnectorStack for ourselves. We can build yours.

Every product in our labs was designed and shipped by the same two-person team that would build your MVP. If you have an idea worth building, that's the whole pitch.

Start a build →