ConnectKit 0.1.6 — credentials that don't expire on you, tools the models can actually read
The v0.1.x series as one story: from a spec that could be read to a runtime where OAuth tokens refresh themselves and tool descriptions are JSON Schema.
Ask any agent developer what actually breaks in production integrations, and past “the API changed” you’ll get two answers: expired tokens and tool descriptions the model couldn’t parse. The v0.1.x series of ConnectKit is the story of fixing both, in four milestones.
P0.1 — a spec that one file can carry
meta_tools was coupled to the Executive Assistant — a tool layer that only worked inside one app. The first milestone broke that coupling: ToolSpec became the adapter boundary, with an sdk_adapter and shared utils. One YAML file describing a connector’s tools is only useful if any runtime can consume it — this is where that becomes a promise instead of an accident.
P0.2 — a runtime that means it (v0.1.1)
ToolSpec without a runtime is documentation. P0.2 gave connectors a real MCP tool lifecycle: registration, dispatch, state — owned end to end by the runtime. Connectors stopped being “metadata that could become tools” and started being tools.
P0.3 — the tokens refresh themselves
The most unglamorous feature an integration platform ships, and the one that decides whether agents work on Friday afternoon. The vault now tracks expiry, and a background refresh task keeps tokens alive — agents never see expired credentials, and nobody writes a “token refresh” cron job ever again.
P0.4 — JSON Schema, not prose
You can describe a parameter in a sentence and a human will nod. A model doesn’t read — it parses. parameter_descriptions got deprecated in favor of real JSON Schema tool descriptions: typed parameters, constraints the model can consume, fewer calls that fail because the tool shape was ambiguous.
0.1.6 — the hardening
Google compatibility: strip the service query param from redirect_uri — Google’s OAuth rejects it. Plus PyPI badges and project URLs, because a library that can’t be found is a library that doesn’t exist.
The through-line: ConnectKit isn’t building connector catalogs (anyone can mirror Nango’s spec list) — it’s building the part where your agent gets a working, current, typed tool. Expired tokens are a silent failure; this series made them rare. Ambiguous tool shapes are an invisible tax on every call; JSON Schema made them illegal.
ConnectKit sits between the user’s SaaS accounts and the agent — local OAuth vault, YAML specs, CLI/MCP execution, zero cloud in the path. See the product page for how that lands against the hosted platforms.