Skip to main content

Knowledge Base

Back to support overview

Integrate TeamViewer with AI systems using MCP

Last Modified: 6 авг. 2026 г.

Model Context Protocol (MCP) enables AI systems to connect to TeamViewer ONE and interact with your IT environment. It provides a standardized way to access data, trigger actions, and automate workflows using natural language. This allows you to reduce manual steps and work more efficiently across systems.

MCP acts as a shared interface between AI tools and enterprise platforms. Instead of creating multiple integrations, it provides a single, consistent connection layer.

This article applies to all TeamViewer paid license holders with access to TeamViewer WebAPI.

Prerequisites

  • Access to an AI system (E.g., Claude or Copilot)
  • Access to a TeamViewer account

Available resources

Note: For additional details, see the ReadMe section in the GitHub repository.

Download

Model Context Protocol overview

Model Context Protocol (MCP) is an open standard that connects AI models with enterprise tools and APIs.

It enables:

  • Access to real-time data

  • Execution of actions across systems

  • Reusable workflows using structured prompts

MCP provides a consistent interface that allows AI systems to interact with tools without requiring individual integrations.

What the connector can do

After connecting your TeamViewer account, AI systems can help with:

  • Devices: View, add, edit, or remove managed devices and device groups

  • Remote sessions: Start and manage remote control sessions

  • Users and access: View and manage users, roles, and permissions in your TeamViewer company

  • Contacts: View, add, edit, or remove contacts

  • Policies: View and manage TeamViewer, monitoring, and patch management policies

  • Monitoring: View monitoring information for devices

  • Reports and logs: Access connection reports, device reports, and event logs

  • Account and company information: View and update account and company details

  • API tokens: Manage TeamViewer API tokens

The AI systems only perform these actions when you request them. Connecting the app does not allow them to act independently.

How your data is protected

TeamViewer uses OAuth authentication to protect your account information.

  • Your TeamViewer password is never shared with or stored by any of the AI systems

  • You always sign in directly through TeamViewer

  • Claude does not receive your TeamViewer credentials

  • Claude uses a separate authorization token with limited permissions

  • Access tokens are stored securely and only used to complete requested actions

Additional information for prompts

After connecting TeamViewer to an AI system through MCP, you can interact with your TeamViewer environment using natural language. The AI systems can help you retrieve information, manage users, update devices, review sessions, and perform administrative tasks.

The following example prompts show some of the actions available through the integration.

Account management

  • Show me the details of my current TeamViewer account

  • Update my TeamViewer account name to "[New Name]" and email to "[new.email@example.com]"

Company information

  • Show me the details of my TeamViewer company

  • What licenses does our company currently have?

Users

  • Create a new user named "[Jane Doe]" with email "[jane@example.com]"

  • Show me the details for user "[user_name]"

  • Update user "[user_name]" and change their name to "[New Name]"

  • Delete the user with ID "[user_id]"

  • List all users in our company

Roles and permissions

  • List all user roles in our company

  • Create a new role called "[Support Agent]" with permissions to view sessions and manage devices

  • Assign the role "[role_id]" to user "[user_id]"

  • Remove the role "[role_id]" from user "[user_id]"

  • What permissions does user "[user_id]" have?

Devices

  • Show me the details for device "[device_id]"

  • Delete device "[device_id]"

  • List all devices I directly manage

  • Update managed device "[device_id]" and rename it to "[New Name]" and assign policy "[policy_id]"

  • Which managed groups does device "[device_id]" belong to?

Sessions

  • Show me the details of session "[session_id]"

  • List all sessions from the last 7 days

  • List the connection reports for the last 5 connections

  • Get session insights for connections with microphone issues

  • Show me the last connection made to device ID "[device_id]"

Connection reports

  • List connection reports for device "[device_id]"

  • Give me the AI-generated summary of connection "[connection_id]"

  • Get the chat transcript for connection "[connection_id]"

  • List all screenshots available for connection "[connection_id]"

Device groups

  • Create a new device group called "[Sales Devices]"

  • List all device groups

  • Share device group "[group_id]" with user "[user_id]"

  • Delete device group "[group_id]"