> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What They Are

> Organize your integrations and tools under the Model Context Protocol (MCP) standard to connect agents and assistants with external or internal services.

## Overview

The **Model Context Protocol (MCP)** extends the capabilities of language models by enabling them to execute actions on external or internal systems.
In Devic, MCPs act as **integration interfaces** that connect agents and assistants with APIs, services, or custom functions.

<img src="https://mintcdn.com/devic/TaMbtKJRXl9eU5LD/my-mcps-import-third-party-built-in-tools.png?fit=max&auto=format&n=TaMbtKJRXl9eU5LD&q=85&s=4799b345dcf3dcddcab0161c3758ee94" alt="The MCP section" width="1613" height="469" data-path="my-mcps-import-third-party-built-in-tools.png" />

The **MCP** tab holds two sections, depending on who runs the server:

<Columns cols={2}>
  <Card title="My MCPs" icon="wrench">
    Servers you build. Point Devic at your own API — an OpenAPI definition is enough — and it becomes an MCP server whose tools the models can call. Devic hosts it.
  </Card>

  <Card title="Connected" icon="plug">
    Servers somebody else runs. Give Devic the URL of a remote MCP server, authenticate once, and its tools join the catalogue as if they were local.
  </Card>
</Columns>

***

## The rest of the tabs

Beside MCP, the same section carries everything else an agent can be given:

| Tab                | What it holds                                                                                                                                                                              |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **CLIs**           | Command-line tools made available inside an [environment's sandbox](/devic/environments/clis).                                                                                             |
| **Built-in Tools** | Native tools that need no server at all — sending email, generating a PDF from HTML, reading a spreadsheet. See [Built-in Tools](/devic/mcps/built-in-tools/index).                        |
| **Integrations**   | A catalogue of over a thousand ready-made apps — Google Calendar, HubSpot, Jira, Slack — connected by OAuth rather than configured by hand. See [Integrations](/devic/integrations/index). |
| **Code Snippets**  | Small pieces of code exposed as tools. Available in Developer Mode.                                                                                                                        |

<Note>
  **MCP Gateways** used to live here and now sit under [AI Governance](/devic/ai-governance), which is where the sessions and tool calls they record are reviewed. See [MCP Gateway](/devic/mcps/mcp-gateway).
</Note>

***

## Using MCPs

Once created, connected or imported, MCPs become available to the agents and assistants you attach them to.
They can be invoked through natural language or integrated into automated workflows.

<Columns cols={2}>
  <Card title="Internal use" icon="link">
    Agents execute MCP tools autonomously within their business logic.
  </Card>

  <Card title="External use" icon="globe">
    MCPs can be published and shared with other environments —for example, ChatGPT or third-party services— through an access URL.
  </Card>
</Columns>

***

<Card title="Next step" icon="wrench" href="/devic/mcps/my-mcps/what-it-is">
  Learn how to create your MCP automatically from an OpenAPI definition.
</Card>