---
sidebar_position: 1
keywords:
- MCP Server
sidebar_label: Introduction
title: MCP server
description: Connect AI tools to your architecture catalog
---

import AddedIn from '@site/src/components/MDX/AddedIn';

import PlanBanner from '@site/src/components/MDX/PlanBanner';

<PlanBanner plan="Scale" />

Every EventCatalog instance automatically includes a [Model Context Protocol (MCP) server](https://modelcontextprotocol.io/introduction). 

<!-- This allows AI assistants to access your documentation content directly, making it easy for tools like Claude Desktop, Cursor, and VS Code extensions to answer questions using your docs.

The MCP server is available at your site's URL with `/docs/mcp` appended.

### Using the standalone server?

:::warning Standalone server
The standalone server `@eventcatalog/mcp-server` is getting deprecated. If you want to use the MCP server you should migrate to the `/mcp/` endpoint.
:::

For teams that are using the standalone server, you can still read the documentation for the standalone server below.

<details>
<summary>View standalone server documentation</summary>

The standalone server runs locally (stdio) or as an HTTP API.

**Transport types:**
- [stdio](/docs/development/ask-your-architecture/mcp-server/getting-started#use-standalone-server) - Local development and testing
- [HTTP API](/docs/development/ask-your-architecture/mcp-server/getting-started#use-standalone-server) - Production and integrations

**Source code:** [github.com/event-catalog/mcp-server](https://github.com/event-catalog/mcp-server)

</details> -->






