# Personal Connectors Overview

div
strong
🔨 In Development
 — This section is still being developed and may change.


Personal Connectors enable your Freddy AI assistants to interact with external services like GitHub, ClickUp, Jira, and more. This guide provides an overview of what personal connectors are and how they work.

## What are Personal Connectors?

Personal Connectors are integrations that connect Freddy AI to external services using the Model Context Protocol (MCP). They allow your AI assistants to:

- **Read data** from external services (e.g., list GitHub issues)
- **Write data** to external services (e.g., create ClickUp tasks)
- **Execute actions** on your behalf (e.g., send Teams messages)
- **Access custom tools** from any MCP-compliant server


## How It Works


```
┌─────────────────┐
│  You configure  │
│   a connector   │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│ Freddy validates│
│  & stores your  │
│   credentials   │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│  AI Assistant   │
│  discovers      │
│  available      │
│  tools          │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│  You chat with  │
│  assistant      │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│  Assistant uses │
│  connector to   │
│  perform action │
└─────────────────┘
```

## Connector Types

### Official Connectors

Externally hosted connectors integrated by Aitronos:

- **GitHub** - Repository management, issues, pull requests
- **Figma Local** - Design file access (requires local installation)


### Aitronos-Built Connectors

Hosted and maintained by Aitronos:

- **ClickUp** - Task and project management
- **Jira** - Issue tracking and project management
- **Microsoft Teams** - Messaging and collaboration


### Custom Connectors

Your own MCP servers:

- Connect to any MCP-compliant server
- Build custom integrations
- Host on your infrastructure


## Key Features

### 🔐 Secure by Default

- **Encrypted credentials** - All credentials encrypted at rest
- **Automatic validation** - Credentials tested before storage
- **Access control** - Only you can access your configurations
- **Audit logging** - All operations logged for security


### ⚡ Easy to Use

- **Simple API** - RESTful API for all operations
- **Automatic discovery** - Tools discovered automatically
- **Smart caching** - Tool definitions cached for performance
- **Health monitoring** - Connection status tracked


### 💰 Transparent Billing

- **Per-use pricing** - Only pay for what you use
- **Configurable costs** - Base fee + time-based pricing
- **Usage tracking** - Detailed logs of all executions
- **Cost breakdown** - See exactly what you're paying for


### 🎯 Flexible Configuration

- **Per-user scope** - Each user has their own configurations
- **API key support** - Use with user accounts or API keys
- **Enable/disable** - Turn connectors on/off as needed
- **Multiple configs** - Configure the same connector multiple times


## Use Cases

### Development Workflow

**Scenario:** Manage GitHub repositories through chat


```
You: Create a new issue titled "Fix login bug" in my repo
```