---
title: "Overview"
description: "Overview of connectors in meinGPT"
canonical_url: "https://meingpt.com/en/docs/integrations/connectors"
language: en
---

# Overview

Connectors extend the capabilities of your chats and AI assistants by enabling them to interact with external systems and data sources.

## What are connectors?

Connectors are standardized interfaces that allow AI models to:

- **Retrieve external data** - Real-time information from various sources
- **Execute actions** - Perform tasks in connected systems
- **Extend context** - Relevant information for better responses
- **Automate workflows** - Orchestrate complex processes

## Available connectors

### Highlighted connectors

**[Microsoft 365](/en/docs/integrations/connectors/microsoft365)**
- Combines internal Microsoft 365 tools (Outlook, Calendar, Teams, SharePoint)
- Runs in user context with user-level permissions
- Best for email, meeting, chat, and document workflows

**[Google Workspace](/en/docs/integrations/connectors/google-workspace)**
- Gmail, Calendar, and Drive as standalone connectors
- Executes with the permissions of the authenticated user
- Best for personal inbox, scheduling, and file workflows

**[Atlassian](/en/docs/integrations/connectors/atlassian)**
- Access Jira issues and Confluence knowledge via the Atlassian Rovo MCP server
- Native mode runs in user context with user-level permissions
- Optional data-pool mode for large-scale knowledge search

### Native connector vs. data pool

The same architecture pattern applies to Microsoft 365, Google Workspace, and Atlassian:

- **Native connector**: executes in user context with user-level permissions
- **Data pool (RAG)**: scalable retrieval on indexed datasets

Important: in data-pool setups, native user-level permissions from the source platform do not carry over automatically.

### Database Tools

**[MCP Database](/en/docs/integrations/connectors/mcp-database)**
- Direct SQL queries
- Data analysis and manipulation
- Supports PostgreSQL, MySQL, Microsoft SQL Server
- Secure connection management

### Documentation Tools

**[Context7](/en/docs/integrations/integrated-databases/context7)**
- Retrieve technical documentation
- API references
- Code examples
- Version-specific information

### Built-in tools in Chats

Core built-in tools are now documented in the **Chats** section:

- [Web Research](/en/docs/platform/web-search)
- [Charts](/en/docs/platform/charts)
- [Code Sandbox](/en/docs/platform/code-sandbox)
- [Memory](/en/docs/platform/memory)
- [Calculator](/en/docs/platform/calculator)

### Business Tools

**[HubSpot](/en/docs/integrations/connectors/hubspot)**
- Retrieve CRM data
- Manage contacts and companies
- Deals and tickets
- Browse files in HubSpot

**[Salesforce](/en/docs/integrations/connectors/salesforce)**
- Query CRM data (leads, opportunities, accounts)
- Create and update records
- Run SOQL and SOSL queries
- View file attachments

**[Stripe](/en/docs/integrations/connectors/stripe)**
- Retrieve payment data
- Transaction history
- Customer information
- Subscription management

## Enabling connectors

### From the chat

As soon as the AI needs a connector in a conversation that your account isn't connected to yet, you can **connect it right in the chat** – no detour through the settings.

The AI shows a prompt with a **Connect** button (e.g. "Connect to Gmail", "Connect to Google Calendar", Asana, Confluence).

You authorize your account via OAuth in the window that opens.

After connecting, the AI continues the task automatically – without leaving the chat.

Connected services remain centrally manageable under **Settings → Connections** (disconnect, reconnect).

### In the chat via the @ menu

Already-connected connectors can be called up directly in the chat input by typing **@** — same pattern as assistants and data sources.

Type **@** in the chat input. A picker opens showing your connected connectors (e.g. Google Calendar, Microsoft Teams, custom MCP servers).

Select the connector you want. It is inserted as an **@-mention** in the message and activated for this chat.

Active connectors appear as chips below the input field — click the **×** on a chip to remove the connector again.

The connector must already be connected under **Settings → Connections** or via the **"+" menu → Connectors** in the chat. Otherwise it won't appear in the @ picker. Per-function permissions (e.g. "read-only" on Outlook or Teams) are honored whether the connector is activated via the @ menu or the "+" menu.

### In the Assistant Editor

Open the [Assistant Editor](/en/docs/platform/assistants)

Navigate to the "Tools" section

Select desired connectors

Configure required parameters

Save the assistant

### Tool Configuration

```yaml
tools:
  - type: mcp
    name: database
    config:
      connection_string: ${DATABASE_URL}
      allowed_operations: ["SELECT"]

  - type: mcp
    name: web
    config:
      max_pages: 5
      timeout: 30
```

## Custom MCP Servers

You can also integrate your own MCP servers:

### Requirements

- Publicly accessible URL
- MCP protocol implementation
- HTTPS encryption
- Authentication (optional)

### Setup

Create it via the "Add a custom MCP server" tile (name + URL)

OAuth (if the server supports it) or an API key/token as a header

In the assistant editor

Details incl. troubleshooting: [Custom MCP Server Integration](/en/docs/integrations/custom-mcp-server)

## Security

### Permission Model

- **Tool-Level** - Which tools can the assistant use?
- **Operation-Level** - Which actions are allowed?
- **Data-Level** - Which data can be accessed?
- **User-Level** - Who can use which tools?

### Best Practices

Grant only necessary rights

Log all tool usage

Always use HTTPS/TLS

Store API keys securely

Prevent abuse

## Use Cases

### Data Analysis
```
Assistant with Database + Charts Tools:
- Retrieve data from database
- Perform analysis
- Create visualization
- Present insights
```

### Research Assistant
```
Assistant with Web Research + Context7 + Memory:
- Search web for information
- Retrieve technical documentation
- Save important findings
- Create summary
```

### Business Intelligence
```
Assistant with HubSpot + Stripe + Database:
- Aggregate customer data
- Perform revenue analysis
- Identify trends
- Generate reports
```

## Performance

### Optimization

- **Caching** - Cache frequent requests
- **Batching** - Bundle multiple operations
- **Timeouts** - Set appropriate time limits
- **Parallelization** - Use independent tools in parallel

### Monitoring

- Tool usage statistics
- Response times
- Error rates
- Cost monitoring

## Troubleshooting

### Common Issues

**Tool not responding:**
- Check connection
- Increase timeouts
- Analyze logs

**Tool works once, then stops working:**
- Send your next message in the same chat and try the tool call again – every new message rebuilds the tool connection, which often picks up a fresh authorization automatically if the previous one had expired.
- If the call keeps failing, open the tool picker (**@** in the message box) or go to **Settings → Connections** and reconnect the affected tool – its stored authorization (especially for OAuth) couldn't be refreshed automatically.
- If the problem persists, contact support with the affected chat link.

**Unexpected results:**
- Verify tool configuration
- Validate permissions
- Check input format

**Performance issues:**
- Enable caching
- Optimize requests
- Use parallelization

## Further Information

- [Custom MCP Server Guide](/en/docs/integrations/custom-mcp-server)
- [API Documentation](/en/docs/integrations/building-mcp-tooling)
- [Security Guidelines](/en/trust-center)