ansible-tmm/mcp-demo

mcp demo for AAP

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 43 minutes ago
Added to GitGenius on June 23rd, 2026
Created on January 8th, 2026
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 10
Total Stargazers: 16 (+0)
Total Subscribers: 0 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 0.1 hours
90th percentile: 0.1 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 31 days
Stale 30+ days: 3
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

mcp-demo is a demonstration repository that shows how to connect AI assistants to Ansible Automation Platform using the Model Context Protocol.

The repository addresses the need to integrate AI assistants with Ansible Automation Platform by providing setup guides for connecting multiple AI platforms to a single MCP server that exposes six distinct toolsets. These toolsets cover job management, inventory management, system monitoring, user management, security and compliance, and platform configuration. The approach works by offering platform-specific configuration guides that handle the differences in how each AI assistant authenticates and communicates with the MCP server.

The tool is suited for organizations running Ansible Automation Platform who want to enable natural language interaction with their automation infrastructure through AI assistants. It supports three different AI platforms: Cursor IDE for developers seeking AI assistance while coding, Claude Desktop for general-purpose AI interaction, and Microsoft Copilot Studio for enterprise users building custom copilots. The key distinction between platforms is their configuration method and certificate requirements—Cursor and Claude Desktop support development-friendly SSL certificate bypassing, while Copilot Studio requires valid certificates and uses an OpenAPI-based approach through Power Apps Custom Connectors.

The repository consists of setup guides and configuration examples rather than a deployable application itself, with the actual MCP server deployed separately on either RHEL or OpenShift. Development activity shows that the project maintains focused, targeted documentation with clear separation between platform-specific setup paths, suggesting an organized approach to managing multiple integration points. The repository includes structured guides for each supported platform with explicit configuration examples and authentication patterns, indicating deliberate attention to making each integration path clear and reproducible.