connectkit 0.1.0__tar.gz

connectkit-0.1.0/.env

@@ -0,0 +1 @@
+PYPI_TOKEN=pypi-AgEIcHlwaS5vcmcCJDEyNDliNWIwLTllMDYtNDhlOS04ZjI5LTZlMmYwODBlNzg1ZgACKlszLCIwMDVlMmRlOC03ZDM3LTRhNDYtYjkyZi03Nzg0YmM3MzgwMTgiXQAABiBiyMQbu2oeVt0dJrvlLqCkNJZuZjE7dTnCGLkuMuv-dw

connectkit-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+*/*.pyc
+__pycache__/
+*.egg-info/
+dist/
+.venv/
+.pytest_cache/
+*.db

connectkit-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Eddy Vinck
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

connectkit-0.1.0/PKG-INFO

@@ -0,0 +1,197 @@
+Metadata-Version: 2.4
+Name: connectkit
+Version: 0.1.0
+Summary: Connect AI agents to SaaS — one YAML file per service. OAuth, token vault, tool discovery.
+Author: Eddy Xu
+License: MIT
+License-File: LICENSE
+Keywords: agent,ai,connector,mcp,oauth,saas,tools
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Internet :: WWW/HTTP
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Requires-Dist: cryptography>=41.0
+Requires-Dist: fastapi>=0.129
+Requires-Dist: httpx>=0.28
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# ConnectKit
+
+> **Purposefully built for AI Agents.** ConnectKit gives agents access to user SaaS accounts — Gmail, Calendar, Drive, GitHub, Slack, and 520+ more — through one YAML file per service. OAuth, API keys, token vault, and tool discovery handled automatically. Used in production by the [Executive Assistant](https://github.com/open-assistants-lab) agent system.
+
+> **Embedded. Local. Open source.** No cloud APIs, no hosted auth services. Runs entirely on-device with an encrypted SQLite credential vault + local YAML specs. Ships as a single Python package with zero external infrastructure dependencies.
+
+**Connect AI agents to SaaS.** One YAML file per service. OAuth, token vault, tool discovery — handled automatically.
+
+```python
+from connectkit import ConnectKitBridge
+
+bridge = ConnectKitBridge(user_id="alice")
+await bridge.discover()
+
+# Agent gets tools for all connected services
+tools = bridge.get_tool_definitions()
+# → [google-workspace__gmail_list, github__issue_list, salesforce__soql_query, ...]
+
+# Show the connector catalog
+catalog = bridge.list_available()
+# → [{name: "google-workspace", connected: true, setup_guide_url: "..."}, ...]
+```
+
+## Why ConnectKit?
+
+Every AI agent that needs access to user SaaS accounts ends up wiring three things together: OAuth flows, credential storage, and CLI/MCP tool wrappers. You build `/auth/google/login`, `/auth/google/callback`, token refresh logic, subprocess calls for `gws gmail list`... then you do it again for GitHub, again for Outlook.
+
+ConnectKit does all of that once, done right. One YAML file per service. No Python code per connector.
+
+| Feature | Status |
+|---------|--------|
+| 524 SaaS connectors (from Nango's 779-provider baseline) | ✅ |
+| YAML-based connector spec (no Python code per service) | ✅ |
+| Encrypted SQLite credential vault (Fernet) | ✅ |
+| Universal OAuth 2.0 router (one endpoint, all services) | ✅ |
+| CLI adapter backend (wraps any SaaS CLI) | ✅ |
+| MCP adapter backend (connects to MCP servers) | ✅ |
+| Dual CLI + MCP support per connector (53+ connectors) | ✅ |
+| Connector catalog (list available services + status) | ✅ |
+| Agent meta-tools (list, connect, disconnect, health) | ✅ |
+| Per-user credential isolation | ✅ |
+| Self-hosted support (base_url for self-hosted instances) | ✅ |
+| No external API dependencies (works offline) | ✅ |
+
+## Installation
+
+```bash
+pip install connectkit
+```
+
+## Core Concepts
+
+### One YAML file per service
+
+```yaml
+# connectors/google-workspace.yaml
+name: google-workspace
+display: "Google Workspace"
+setup_guide_url: "https://developers.google.com/workspace/guides/create-credentials"
+auth:
+  type: oauth2
+  oauth2:
+    authorize_url: https://accounts.google.com/o/oauth2/v2/auth
+    token_url: https://oauth2.googleapis.com/token
+    scopes:
+      - https://www.googleapis.com/auth/gmail.readonly
+      - https://www.googleapis.com/auth/calendar.readonly
+  required_fields:
+    - name: client_id
+      label: "Client ID"
+      input_type: text
+    - name: client_secret
+      label: "Client Secret"
+      input_type: password
+tool_sources:
+  - type: cli
+    command: gws
+    install: npm install -g @googleworkspace/cli
+  - type: mcp
+    server_name: google-workspace
+    command: gws mcp
+```
+
+### Auth types
+
+| Type | Use for | Example |
+|------|---------|---------|
+| `oauth2` | OAuth 2.0 (Google, Microsoft, GitHub, Slack, 234+ services) | Browser authorization → tokens vaulted |
+| `api_key` | API keys (Firecrawl, Stripe, Twilio, 288+ services) | Paste key into form → vaulted |
+| `none` | No auth needed (local tools) | Auto-connected |
+
+### Tool source backends
+
+| Backend | Count | Best for |
+|---------|-------|----------|
+| **CLI** | 63 | SaaS with official CLIs (gws, gh, glab, m365, stripe, sf, vercel, etc.) |
+| **MCP** | 514 | SaaS with MCP servers (first-party or community) |
+| **Dual** (CLI + MCP) | 53 | Best available backend picked at runtime |
+
+### CredentialVault
+
+All tokens are stored in an encrypted SQLite database (Fernet encryption). One vault per user. Master key from `CONNECTKIT_VAULT_KEY` env var.
+
+```python
+from connectkit import CredentialVault
+
+vault = CredentialVault("./data/users/alice")
+vault.store_token("google-workspace", "oauth2", {
+    "access_token": "ya29...", "refresh_token": "1//..."
+})
+token = vault.get_token("google-workspace")
+```
+
+### OAuth flow
+
+```python
+# 1. User fills in client_id + client_secret → stored in vault via POST /connectors/connect
+# 2. Flutter renders "Connect" button → opens:
+#    GET /auth/login?service=google-workspace&user_id=alice
+# 3. Browser redirects to Google OAuth → user authorizes
+# 4. Google redirects to:
+#    GET /auth/callback?code=...&state=...
+# 5. Gateway exchanges code for tokens → stores in vault
+# 6. Google Workspace: ✅ Connected
+```
+
+OAuth states are Fernet-encrypted and self-contained — any vault with the same key can validate them (10-minute TTL).
+
+### Self-Hosted Support
+
+Services like Firecrawl, Sentry, GitLab offer self-hosted deployments. ConnectKit supports them with an optional `base_url` field:
+
+```yaml
+required_fields:
+  - name: base_url
+    label: "Self-Hosted URL"
+    placeholder: "https://firecrawl.example.com"
+    input_type: url
+    help_text: "Leave empty for cloud version"
+    optional: true
+```
+
+## Connector Catalog
+
+| Category | Count | Services |
+|----------|-------|----------|
+| dev-tools | 120+ | GitHub, GitLab, Jira, Bitbucket, GitLab, Sentry, Datadog, PagerDuty, Snowflake, Vercel, Netlify, Postman, Figma |
+| productivity | 80+ | Google Workspace, Microsoft 365, Notion, Airtable, Monday, ClickUp, Trello, Asana, Evernote |
+| crm | 50+ | HubSpot, Salesforce, Pipedrive, Zoho CRM, Close, Copper |
+| communication | 40+ | Slack, Discord, Zoom, Twilio, WhatsApp, Intercom, Zendesk |
+| payment | 30+ | Stripe, Square, PayPal, Braintree, Adyen, Checkout.com |
+| marketing | 30+ | Mailchimp, Klaviyo, SendGrid, Apollo, Brevo, Constant Contact |
+| e-commerce | 25+ | Shopify, WooCommerce, Amazon Selling Partner, BigCommerce |
+| analytics | 20+ | Mixpanel, Amplitude, PostHog, Tableau, Looker, Heap |
+| hr | 20+ | BambooHR, Workday, Gusto, Personio, Greenhouse, Lever |
+| storage | 15+ | Dropbox, Box, Google Drive, OneDrive, Egnyte |
+| other | 90+ | Everything else |
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Author
+
+Eddy Xu
+
+## Status
+
+Alpha — actively developed. Core spec model, vault, OAuth router, and adapter backends are stable with full test coverage (152+ tests). 524 connectors shipped. Currently used in production in the Executive Assistant agent system.

connectkit-0.1.0/README.md

@@ -0,0 +1,169 @@
+# ConnectKit
+
+> **Purposefully built for AI Agents.** ConnectKit gives agents access to user SaaS accounts — Gmail, Calendar, Drive, GitHub, Slack, and 520+ more — through one YAML file per service. OAuth, API keys, token vault, and tool discovery handled automatically. Used in production by the [Executive Assistant](https://github.com/open-assistants-lab) agent system.
+
+> **Embedded. Local. Open source.** No cloud APIs, no hosted auth services. Runs entirely on-device with an encrypted SQLite credential vault + local YAML specs. Ships as a single Python package with zero external infrastructure dependencies.
+
+**Connect AI agents to SaaS.** One YAML file per service. OAuth, token vault, tool discovery — handled automatically.
+
+```python
+from connectkit import ConnectKitBridge
+
+bridge = ConnectKitBridge(user_id="alice")
+await bridge.discover()
+
+# Agent gets tools for all connected services
+tools = bridge.get_tool_definitions()
+# → [google-workspace__gmail_list, github__issue_list, salesforce__soql_query, ...]
+
+# Show the connector catalog
+catalog = bridge.list_available()
+# → [{name: "google-workspace", connected: true, setup_guide_url: "..."}, ...]
+```
+
+## Why ConnectKit?
+
+Every AI agent that needs access to user SaaS accounts ends up wiring three things together: OAuth flows, credential storage, and CLI/MCP tool wrappers. You build `/auth/google/login`, `/auth/google/callback`, token refresh logic, subprocess calls for `gws gmail list`... then you do it again for GitHub, again for Outlook.
+
+ConnectKit does all of that once, done right. One YAML file per service. No Python code per connector.
+
+| Feature | Status |
+|---------|--------|
+| 524 SaaS connectors (from Nango's 779-provider baseline) | ✅ |
+| YAML-based connector spec (no Python code per service) | ✅ |
+| Encrypted SQLite credential vault (Fernet) | ✅ |
+| Universal OAuth 2.0 router (one endpoint, all services) | ✅ |
+| CLI adapter backend (wraps any SaaS CLI) | ✅ |
+| MCP adapter backend (connects to MCP servers) | ✅ |
+| Dual CLI + MCP support per connector (53+ connectors) | ✅ |
+| Connector catalog (list available services + status) | ✅ |
+| Agent meta-tools (list, connect, disconnect, health) | ✅ |
+| Per-user credential isolation | ✅ |
+| Self-hosted support (base_url for self-hosted instances) | ✅ |
+| No external API dependencies (works offline) | ✅ |
+
+## Installation
+
+```bash
+pip install connectkit
+```
+
+## Core Concepts
+
+### One YAML file per service
+
+```yaml
+# connectors/google-workspace.yaml
+name: google-workspace
+display: "Google Workspace"
+setup_guide_url: "https://developers.google.com/workspace/guides/create-credentials"
+auth:
+  type: oauth2
+  oauth2:
+    authorize_url: https://accounts.google.com/o/oauth2/v2/auth
+    token_url: https://oauth2.googleapis.com/token
+    scopes:
+      - https://www.googleapis.com/auth/gmail.readonly
+      - https://www.googleapis.com/auth/calendar.readonly
+  required_fields:
+    - name: client_id
+      label: "Client ID"
+      input_type: text
+    - name: client_secret
+      label: "Client Secret"
+      input_type: password
+tool_sources:
+  - type: cli
+    command: gws
+    install: npm install -g @googleworkspace/cli
+  - type: mcp
+    server_name: google-workspace
+    command: gws mcp
+```
+
+### Auth types
+
+| Type | Use for | Example |
+|------|---------|---------|
+| `oauth2` | OAuth 2.0 (Google, Microsoft, GitHub, Slack, 234+ services) | Browser authorization → tokens vaulted |
+| `api_key` | API keys (Firecrawl, Stripe, Twilio, 288+ services) | Paste key into form → vaulted |
+| `none` | No auth needed (local tools) | Auto-connected |
+
+### Tool source backends
+
+| Backend | Count | Best for |
+|---------|-------|----------|
+| **CLI** | 63 | SaaS with official CLIs (gws, gh, glab, m365, stripe, sf, vercel, etc.) |
+| **MCP** | 514 | SaaS with MCP servers (first-party or community) |
+| **Dual** (CLI + MCP) | 53 | Best available backend picked at runtime |
+
+### CredentialVault
+
+All tokens are stored in an encrypted SQLite database (Fernet encryption). One vault per user. Master key from `CONNECTKIT_VAULT_KEY` env var.
+
+```python
+from connectkit import CredentialVault
+
+vault = CredentialVault("./data/users/alice")
+vault.store_token("google-workspace", "oauth2", {
+    "access_token": "ya29...", "refresh_token": "1//..."
+})
+token = vault.get_token("google-workspace")
+```
+
+### OAuth flow
+
+```python
+# 1. User fills in client_id + client_secret → stored in vault via POST /connectors/connect
+# 2. Flutter renders "Connect" button → opens:
+#    GET /auth/login?service=google-workspace&user_id=alice
+# 3. Browser redirects to Google OAuth → user authorizes
+# 4. Google redirects to:
+#    GET /auth/callback?code=...&state=...
+# 5. Gateway exchanges code for tokens → stores in vault
+# 6. Google Workspace: ✅ Connected
+```
+
+OAuth states are Fernet-encrypted and self-contained — any vault with the same key can validate them (10-minute TTL).
+
+### Self-Hosted Support
+
+Services like Firecrawl, Sentry, GitLab offer self-hosted deployments. ConnectKit supports them with an optional `base_url` field:
+
+```yaml
+required_fields:
+  - name: base_url
+    label: "Self-Hosted URL"
+    placeholder: "https://firecrawl.example.com"
+    input_type: url
+    help_text: "Leave empty for cloud version"
+    optional: true
+```
+
+## Connector Catalog
+
+| Category | Count | Services |
+|----------|-------|----------|
+| dev-tools | 120+ | GitHub, GitLab, Jira, Bitbucket, GitLab, Sentry, Datadog, PagerDuty, Snowflake, Vercel, Netlify, Postman, Figma |
+| productivity | 80+ | Google Workspace, Microsoft 365, Notion, Airtable, Monday, ClickUp, Trello, Asana, Evernote |
+| crm | 50+ | HubSpot, Salesforce, Pipedrive, Zoho CRM, Close, Copper |
+| communication | 40+ | Slack, Discord, Zoom, Twilio, WhatsApp, Intercom, Zendesk |
+| payment | 30+ | Stripe, Square, PayPal, Braintree, Adyen, Checkout.com |
+| marketing | 30+ | Mailchimp, Klaviyo, SendGrid, Apollo, Brevo, Constant Contact |
+| e-commerce | 25+ | Shopify, WooCommerce, Amazon Selling Partner, BigCommerce |
+| analytics | 20+ | Mixpanel, Amplitude, PostHog, Tableau, Looker, Heap |
+| hr | 20+ | BambooHR, Workday, Gusto, Personio, Greenhouse, Lever |
+| storage | 15+ | Dropbox, Box, Google Drive, OneDrive, Egnyte |
+| other | 90+ | Everything else |
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Author
+
+Eddy Xu
+
+## Status
+
+Alpha — actively developed. Core spec model, vault, OAuth router, and adapter backends are stable with full test coverage (152+ tests). 524 connectors shipped. Currently used in production in the Executive Assistant agent system.

connectkit-0.1.0/STRATEGY.md

@@ -0,0 +1,111 @@
+# ConnectKit Strategy
+
+## The Core Insight
+
+**Nango = integration platform that added agent tooling on top.**
+**ConnectKit = agent tool runtime that uses connectors as the means, not the end.**
+
+| Dimension | Nango | ConnectKit |
+|-----------|-------|------------|
+| Core abstraction | TypeScript functions that call APIs | Tools as first-class agent primitives |
+| Who writes the integration | Human or AI → TypeScript, deployed to Nango | Agent discovers, connects, and invokes — zero human boilerplate |
+| Tool model | Function with Zod schema → exposed via MEP | Tool = (auth + backend) discovered at runtime by the agent |
+| Meta-tools | None | Agents manage their own tool belt |
+
+## Positioning
+
+> **ConnectKit: The agent-native tool runtime.**
+>
+> *Connectors aren't integrations. They're tools your agent discovers, connects, and composes — autonomously.*
+
+| Old message | New message |
+|---|---|
+| "544+ YAML connector specs" | "Tools your agent can install without human help" |
+| "Local OAuth router and encrypted vault" | "Durable, self-healing auth for unattended agents" |
+| "CLI and MCP adapters" | "Pluggable backends: CLI, MCP, HTTP, and composed tools" |
+| "Own the connector runtime" | "Own your agent's tool belt" |
+
+## Where Nango cannot follow
+
+Nango's architecture is a server with TypeScript functions. This creates structural gaps:
+
+1. **Every new tool requires a deploy** — ConnectKit's YAML-only model means an agent can connect to a new SaaS service by just downloading a spec file. No CI/CD, no deployment.
+2. **No local subprocess model** — Nango runs functions server-side. ConnectKit inherits the user's CLI environment: `gws`, `gh`, `aws`, `docker`, etc. are automatically tools.
+3. **No local-first** — Nango free self-host is feature-gated. ConnectKit is fully local by design.
+4. **No meta-tools** — Nango cannot let agents list, connect, disconnect, or compose tools dynamically because its model is "deploy TypeScript to our runtime." ConnectKit's model is "load a YAML, inject auth, spawn a process."
+
+**The killer slide:** "Nango makes you deploy TypeScript. ConnectKit makes you write five lines of YAML. One requires a DevOps pipeline. The other requires a text editor."
+
+## What to build
+
+### P0 (quick wins, existing code)
+
+1. **Decouple `meta_tools.py` from EA**
+   - Currently imports `src.sdk.tools`, `src.config`, `src.app_logging` — EA-internal modules
+   - Refactor into `connectkit/meta/` — return generic Pydantic models, not EA-specific ToolDefinition
+   - Provide adapters: one dict output for EA, one for LangChain, one for OpenAI SDK
+   - **Why:** Meta-tools are the strongest differentiator. They need to work anywhere.
+
+2. **Implement real MCP lifecycle management**
+   - Replace `_is_mcp_placeholder` stubs in `runtime.py` with a `MCPServerManager` that:
+     - Spawns the MCP server subprocess with injected credentials
+     - Calls `tools/list` at runtime to discover real tools
+     - Proxies `tools/call` requests with per-user env isolation
+     - Handles restart on crash and graceful shutdown
+   - **Why:** MCP is the fastest-growing tool protocol. Placeholder stubs undercut credibility.
+
+3. **Add token refresh**
+   - OAuth tokens with `refresh_token` are stored but never used
+   - Add `refresh_expired_tokens()` to vault, background check in runtime
+   - **Why:** "Agent-native" means durable unattended operation. Stale tokens kill that promise.
+
+4. **Switch `tool_descriptions` to JSON Schema**
+   - Replace free-text `ToolDescription` with full JSON Schema for params and return types
+   - Every connector spec produces an OpenAI-compatible `functions` array
+   - **Why:** Agents need structured schemas to reason about tool calls, not free-text help strings.
+
+### P1 (medium-term)
+
+5. **Implement the HTTP backend**
+   - `HTTPToolSource` is modeled in `spec.py` but `runtime.py` has no handling for `ToolSourceType.HTTP`
+   - Build it: proxy calls through injected auth headers
+   - **Why:** Many SaaS APIs are HTTP-native. CLI and MCP are not always available.
+
+6. **Add credential validation on connect**
+   - After storing a token, make a test call (e.g., `GET /user` or equivalent)
+   - Report connection status as "connected" or "broken" immediately
+   - **Why:** Silent failures erode trust in unattended agents.
+
+7. **Add tool deduplication**
+   - If a connector has both CLI and MCP sources, pick the best one (MCP > CLI > HTTP) instead of returning duplicate tools
+   - **Why:** Agents shouldn't see the same capability twice.
+
+### P2 (moonshot differentiator)
+
+8. **Dynamic tool composition**
+   - Build a `compose` meta-tool that lets an agent create new tools at runtime
+   - Example: "Create a tool that searches Gmail for invoices, extracts amounts, and writes them to a Google Sheet"
+   - ConnectKit chains `gmail.search` → `sheets.append` and registers the result as a named tool
+   - **Why:** This is where you leapfrog Nango entirely. They require a human to write a TypeScript function. ConnectKit lets the agent do it.
+   - **Message:** "Agents don't just *use* tools. They *compose* them."
+
+## Competitor comparison
+
+| Feature | ConnectKit | Nango (OSS) | Nango (Cloud) | Composio | Arcade |
+|---------|-----------|-------------|---------------|----------|--------|
+| OSS license | MIT | MIT | Proprietary | Partial | No |
+| Self-hosted with full features | Yes | No (feature-gated) | N/A | N/A | No |
+| YAML-only connector model | Yes | No (TypeScript) | No (TypeScript) | No | No |
+| Local CLI subprocess tools | Yes | No | No | No | No |
+| Per-user encrypted vault | Yes | Server-side | Server-side | Server-side | Server-side |
+| Meta-tools for agents | Partial (EA-coupled) | No | No | No | No |
+| MCP lifecycle management | No (placeholder) | No | Yes (hosted) | Yes | Yes |
+| Token refresh | No | Yes | Yes | Yes | Yes |
+| Dynamic tool composition | No | No | No | No | No |
+| Structured LLM tool schemas | Partial (free-text) | Yes (Zod) | Yes (Zod) | Yes | Yes |
+
+## The narrative
+
+When someone asks "why not just use Nango?":
+
+"Nango connects your app to APIs. ConnectKit connects your agent to tools. That sounds similar but it's a different model: Nango runs TypeScript functions on their server; ConnectKit loads a YAML spec, injects local credentials, and spawns CLI or MCP processes on your machine. One requires a deployment pipeline. The other requires a text editor. One treats tools as API wrappers. The other treats tools as capabilities an agent discovers, connects, and composes autonomously."

connectkit-0.1.0/connectkit/__init__.py

@@ -0,0 +1,26 @@
+"""ConnectKit — connect AI agents to SaaS accounts.
+
+One YAML file per service. OAuth, token vault, and tool discovery handled automatically.
+"""
+
+__version__ = "0.1.0"
+
+from connectkit.bridge import ConnectKitBridge
+from connectkit.meta_tools import TOOL_SPECS
+from connectkit.sdk_adapter import ToolSpec
+from connectkit.spec import AuthType, ConnectorSpec, RequiredField, ToolSourceType, CLIToolSource
+from connectkit.utils import ensure_cli_installed
+from connectkit.vault import CredentialVault
+
+__all__ = [
+    "ConnectorSpec",
+    "AuthType",
+    "ToolSourceType",
+    "RequiredField",
+    "CredentialVault",
+    "ConnectKitBridge",
+    "ToolSpec",
+    "TOOL_SPECS",
+    "CLIToolSource",
+    "ensure_cli_installed",
+]