Connector SDK: Build Your Own Integration

Status: private preview — public SDK on the roadmap. Intended's connector toolkit is real and tested, but it ships internal today (@intended/connector-sdk, marked private) and is built around a BaseAdapter model — not the @intended/connector-sdk BaseConnector/registerConnector API the earlier version of this post showed. That package and API were not published, so we removed the non-runnable code. Track the public connector SDK in the capability build roadmap and the Capability Truth Matrix (row: *Connector SDK → Private*).

Why Custom Connectors

Intended ships connectors for several platforms — GitHub, ServiceNow, Stripe, Jira, Slack, and the MCP gateway — but every organization has custom systems too: an internal deployment tool, a homegrown ticketing system, a bespoke data pipeline. A connector SDK is what lets those systems become authority-bound without waiting for a first-party integration.

The model (what a connector does)

A connector's job is narrow and security-critical: it sits at the execution boundary and verifies the authority token before it acts. Concretely, the real BaseAdapter validates the Ed25519 signature, the kid, the tenant/adapter/target binding, the decision, the expiry, and the single-use nonce — and refuses to execute if any check fails. It maps a normalized intent onto a target-system action, executes only on a valid ALLOW token, and links the result back to the audit chain. It fails closed.

That toolkit exists and is exercised in-tree today. What's not yet available is a published, documented, build-your-own package on the public npm scope (@intended-inc) with a stable API and a test harness — that's the roadmap item.

What you can do today

• First-party connectors — the shipped connectors (GitHub, ServiceNow, Stripe, Jira, Slack, MCP) cover common systems; see integrations.
• The gateway path — route tool calls through the MCP gateway or the LLM gateway to get authority enforcement without writing a connector.
• Talk to us — if you need a custom connector before the public SDK ships, the internal toolkit can be applied with our help.

When the public connector SDK is published, this post will carry a complete, runnable walkthrough against the real BaseAdapter API.