> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/mcp-integration-contributor-guide/get-started-with-mcp-integration-development.md).

# Get started with MCP integration development

#### What are MCP Integrations? <a href="#uuid-de638ad8-3376-1423-923c-44fa2257e1bb_bridgehead-id235583625972503" id="uuid-de638ad8-3376-1423-923c-44fa2257e1bb_bridgehead-id235583625972503"></a>

MCP (Model Context Protocol) integrations connect Cortex Agentic AI to external MCP servers, automatically discovering and exposing their tools as agentic system actions. Unlike traditional integrations that implement specific business logic, MCP integrations are generic bridges that:

* Connect to a vendor’s MCP server endpoint.
* Authenticate using the vendor’s preferred method.
* Dynamically discover available tools at runtime.
* Execute tools on demand with user-provided arguments.

When an MCP integration is configured in Cortex:

* The `list-tools` command is executed periodically to discover available tools from the MCP server.
* Agentic actions are auto-generated for each discovered tool.
* When an agent calls one of these actions, the integration’s `call-tool` command is invoked with the tool name and parameters.

#### Integration development and existing integrations <a href="#uuid-de638ad8-3376-1423-923c-44fa2257e1bb_bridgehead-id235585344311616" id="uuid-de638ad8-3376-1423-923c-44fa2257e1bb_bridgehead-id235585344311616"></a>

If this is your first time contributing to the Cortex Platform content repository, review the [general contribution guide](https://xsoar.pan.dev/docs/contributing/contributing) first. This guide assumes you’re familiar with standard content contribution practices and the development workflow.

**Sample MCP integrations**

To understand how to structure, authenticate, and enable tool discovery for your own integrations, we recommend reviewing these official MCP content packs.&#x20;

| Integtation                                                                                                   | Path                                              | Details                                                                                                       |
| ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [GitHub MCP](https://xsoar.pan.dev/docs/reference/integrations/github-mcp)                                    | <p></p><p><code>Packs/GitHubMCP</code></p><p></p> | Learn how to map repository tools (issues, PRs, code search) to AI Actions and managing OAuth authentication. |
| <p></p><p><a href="https://xsoar.pan.dev/docs/reference/integrations/generic-mcp">Generic MCP</a> </p><p></p> | `Packs/GenericMCP`                                | Understand how to create a flexible pass-through integration that connects to any standard MCP server.        |
| [Atlassian Cloud MCP](https://xsoar.pan.dev/docs/reference/integrations/atlassian-cloud-mcp)                  | `Packs/AtlassianCloudMCP`                         | Examples of connecting to multi-tool SaaS environments (Jira, Confluence) via a single MCP interface.         |
| [Cloudflare MCP](https://xsoar.pan.dev/docs/reference/integrations/cloudflare-mcp)                            | `Packs/CloudFlareMCP`                             | Review high-velocity telemetry and network tool integration patterns.                                         |

{% hint style="info" %}
You can also find these packs directly in the Cortex Marketplace by filtering for the MCP type. Reviewing the Integration Configuration page within the product will show you the specific parameters (URLs, Headers, and Auth) required for each.
{% endhint %}

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/mcp-integration-contributor-guide/get-started-with-mcp-integration-development.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.