import { CardGrid, LinkCard } from '@astrojs/starlight/components';

An **MCP server** is the bridge that connects a system — your CRM, your calendar, your catalog, a
payments or documentation tool — with your AI agent, so it can use it as a tool while chatting: looking
up data, creating records, searching for information. There are two routes to having one connected:

<CardGrid>
  <LinkCard
    title="What an MCP server is, in one sentence"
    description="An MCP server is the bridge that connects a system — your CRM, your calendar, your catalog, a payments or documentation tool — with your AI agent, so it can use it lik…"
    href="/en/integrations/servidores-mcp/01-que-es-un-servidor-mcp-en-una-frase/"
  />
  <LinkCard
    title="The screen: Settings → MCP servers"
    description="Requirements: Admin role."
    href="/en/integrations/servidores-mcp/02-la-pantalla-ajustes-servidores-mcp/"
  />
  <LinkCard
    title="The catalog by level"
    description="Every template in the catalog carries a level badge, which sums up how much we've reviewed it before offering it to you and how you connect to it."
    href="/en/integrations/servidores-mcp/03-el-catalogo-por-niveles/"
  />
  <LinkCard
    title="Procedure: viewing the &quot;What you're enabling&quot; sheet"
    description="Before connecting any template, review its info sheet — it tells you exactly what you're about to enable, in plain language."
    href="/en/integrations/servidores-mcp/04-procedimiento-ver-la-ficha-que-estas-activando/"
  />
  <LinkCard
    title="Procedure: connecting a level-A template (with a key)"
    description="Requirements: Admin role; an API key from the provider, ideally with the minimum permissions its info sheet indicates (section 4)."
    href="/en/integrations/servidores-mcp/05-procedimiento-conectar-una-plantilla-de-nivel-a-con-clave/"
  />
  <LinkCard
    title="Procedure: connecting via OAuth (level B)"
    description="Requirements: Admin role; an existing account with the provider to authorize access from."
    href="/en/integrations/servidores-mcp/06-procedimiento-conectar-por-oauth-nivel-b/"
  />
  <LinkCard
    title="Managing and disconnecting an existing connection"
    description="The card of an already-connected template (level A or B) shows a summary: &quot;{active} of {total} tools active&quot; and the Disconnect button."
    href="/en/integrations/servidores-mcp/07-gestionar-y-desconectar-una-conexion-ya-hecha/"
  />
  <LinkCard
    title="What happens when a server stops being verified"
    description="The Platform periodically checks that every server in the catalog is still responding and is still the same service it always was."
    href="/en/integrations/servidores-mcp/08-que-pasa-cuando-un-servidor-deja-de-estar-verificado/"
  />
  <LinkCard
    title="The &quot;Connect with MCP&quot; piece in your flows"
    description="Any MCP connection you have active — Custom or from the catalog — also shows up as a piece in the Flows builder (Manual 55 · Jobs and Flows), so a flow can use its…"
    href="/en/integrations/servidores-mcp/09-la-pieza-conectar-con-mcp-en-tus-flujos/"
  />
  <LinkCard
    title="Frequently asked questions"
    description="Can I connect the same template twice, with two different keys?"
    href="/en/integrations/servidores-mcp/10-preguntas-frecuentes/"
  />
</CardGrid>