Appearance
Connectors Overview

Agentcy ships 26 connectors. Each one can feed data into the knowledge graph (ingestion), expose live tools to agents (tool provider), or both.
Conceptual background: Connectors & Tool Providers.
Capability matrix
| Connector | Category | Ingest | Tools | Auth |
|---|---|---|---|---|
| GitHub | Cloud & Infra | ✅ | ✅ | PAT · OAuth · GitHub App |
| AWS | Cloud & Infra | ✅ | ✅ | Keys · AssumeRole · Instance Profile |
| GCP | Cloud & Infra | ✅ | ✅ | Service account JSON · ADC |
| Vercel | Cloud & Infra | ✅ | ✅ | API token |
| Supabase | Cloud & Infra | ✅ | ✅ | Service role key |
| Kubernetes | Cloud & Infra | ✅ | ✅ | kubeconfig · in-cluster SA |
| LocalStack | Cloud & Infra | ✅ | ✅ | Dummy keys (local) |
| Jenkins | Cloud & Infra | ✅ | ✅ | API token |
| Grafana | Cloud & Infra | ✅ | ✅ | API token · service account |
| SQL | Data | ✅ | ✅ | DB user + password |
| MongoDB | Data | ✅ | ✅ | Connection string |
| Power BI | Data | ✅ | ✅ | Azure AD · service principal |
| CSV & JSON | Data | ✅ | — | File upload |
| Slack | Communication | ✅ | ✅ | OAuth · bot token |
| Google Workspace | Communication | ✅ | ✅ | OAuth |
| Read.ai | Communication | ✅ | ✅ | OAuth |
| HubSpot | Communication | ✅ | ✅ | Private app token · OAuth |
| Figma | Communication | ✅ | ✅ | PAT |
| Firecrawl | AI & Media | — | ✅ | API key |
| Web Search | AI & Media | — | ✅ | Tavily · SerpAPI key |
| ElevenLabs | AI & Media | — | ✅ | API key |
| Runway | AI & Media | — | ✅ | API key |
| Remotion | AI & Media | — | ✅ | Local (sandbox-based) |
| Coding Agents (CIAB) | AI & Media | — | ✅ | — |
| OS Sandbox | AI & Media | — | ✅ | — |
| Remote Execution | AI & Media | — | ✅ | Worker token |
| OpenAPI | Extensibility | ✅ | ✅ | Per-spec (Bearer / Basic / API key) |
| MCP | Extensibility | — | ✅ | Server-defined |
| Git | Extensibility | ✅ | — | SSH key · HTTPS token |
| Custom | Extensibility | ✅ | ✅ | User-defined |
Feature-gated availability
Connectors compile in via Cargo features. For most self-hosts, leave all features on. Slim builds:
bash
cargo build -p agentcy-api --release \
--no-default-features \
--features "connectors-cloud connectors-data"See Concept: Connectors.
Register a new connector instance
Same pattern for every connector — the UI is easier, but the API:
bash
curl -X POST http://localhost:8080/api/v1/sources \
-H "authorization: Bearer $TOKEN" -H 'content-type: application/json' \
-d '{
"name":"github-primary",
"connector":"github",
"realm":"development",
"config":{"auth":{"kind":"pat","token":"ghp_…"},"repos":["acme/monolith","acme/webapp"]}
}'Validation runs synchronously. Invalid credentials → 422 with error.code = "source_validation_failed".
First sync:
bash
curl -X POST "http://…/sources/$SOURCE_ID/sync" -H "authorization: Bearer $TOKEN"Drop into Pipelines when you need scheduled, multi-step, revertible syncs.
Tool discovery
Every connector's live tools are searchable via the agent loop's search_connector_tools. From the REST API:
bash
curl "http://…/skills?kind=connector_tool&connector=kubernetes" \
-H "authorization: Bearer $TOKEN" | jq '.items[] | {name, description}'Writing a connector
Guide: Custom Connectors. Implement one or both traits from agentcy-ingest / agentcy-core, register in state.rs, done.