---
title: "Accessing the Garba MCP"
description: "How to access the Garba MCP"
url: https://help.garba.ai/en/articles/10742499-accessing-the-garba-mcp
collection: "Developer Documentation"
updated: 2026-11-20
language: en
---

# Accessing the Garba MCP

How to access the Garba MCP

## Overview

The **Garba MCP** lets an AI tool such as Claude, Cursor or Windsurf read data from your Garba workspace.

The MCP reads meetings and transcripts, your calendar, users and teams, companies, deals, emails and tasks. It uses your existing access permissions. The MCP is read-only: it cannot change anything in Garba.

* * *

## Accessing the MCP

The MCP is available at:

👉 [https://mcp.garba.ai/](https://mcp.garba.ai/)

Authentication is handled via OAuth.

> Your access level in the MCP matches your access level inside Garba.  
> You will only be able to retrieve data that you have permission to view within the platform.

* * *

## Available tools

The MCP has 19 tools. Your AI tool picks the right one from your question.

### Meetings

-   `list_meetings` lists meetings, newest first, with their participants and the companies and deals each meeting is linked to. Filters: company, deal, date range, title search, the team of whoever recorded it, and a user, matching the meetings they recorded, the meetings they attended that someone else recorded, or both.
    
-   `get_meeting` returns one meeting: summary, participants, meeting type and language.
    
-   `get_transcript` returns the full transcript of one meeting, with speakers and timestamps.
    

### Calendar

-   `list_scheduled_meetings` lists meetings booked in the calendars Garba syncs, as the **Calendar** page shows them: upcoming ones by default, earliest first, with their participants and the companies and deals each is linked to. Filters: company, deal, a user whose synced calendar has the meeting, title search and a date range. It shows what your Calendar page shows, so a colleague's meeting appears only when the notetaker is set to join it; `get_deal` lists every customer meeting booked on a deal.
    

### Users and teams

-   `get_me` returns your own user ID, name, email and team.
    
-   `list_users` lists the users in your account.
    
-   `list_teams` lists the teams you have access to.
    

### Companies

-   `list_companies` lists companies, with an optional search by name or domain.
    
-   `get_company` returns the details of one company.
    
-   `get_company_summary` returns the AI summary of one company, if the summary is newer than the latest meeting or email with that company.
    

### Deals

-   `list_deals` lists deals, as the Deals table in Garba shows them, with each deal's last activity (the latest meeting, email or note), its next booked meeting and whether it is stale. Filters: outcome, pipeline, stage, company, close date, owner, team and search.
    
-   `get_deal` returns one deal, as the deal page in Garba shows it.
    
-   `list_pipelines` lists your pipelines and their stages, with deal counts and values.
    

The deal tools return nothing when Deals is not enabled for your account.

### Emails

-   `list_emails` lists emails, newest first. Filters: company, deal, subject search and date range.
    
-   `get_email` returns one email with its full body.
    
-   `get_email_thread` returns the whole thread around one email.
    

The email tools return nothing when email sync is switched off for your account.

### Tasks

-   `list_tasks` lists tasks in the states Open, Today, Upcoming and Completed. By default it lists the tasks assigned to you. Filters: meeting, company, deal, assignee, due date and search.
    
-   `get_task` returns one task.
    
-   `get_task_counts` returns how many of your own tasks are in each state.
    

* * *

## Permissions

All MCP requests respect Garba’s permission structure.  
If you cannot access certain meetings or users in the Garba app, you will not be able to access them via the MCP.

* * *

## Blocking MCP for your account

An admin can stop everyone in the account from connecting AI tools to Garba.

1.  Go to **Settings → Account → Settings**.
    
2.  Under **AI Tools**, switch **Garba MCP server** to **Blocked**.
    
3.  Click **Save**.
    

The block takes effect right away:

-   Existing connections, including ones made with an API key, stop working.
    
-   Anyone who tries to connect is shown a page saying that their admin has turned it off.
    

The block only covers the Garba MCP server. Garba's own MCP connectors to other tools keep working; who may add those is set under **AI Tools → Who can add MCP connections**.

Switch it back to **Allowed** to let people connect again. Connections made with an API key start working again on their own. People who connected by signing in may need to connect again from their AI tool.
