MCP Integration Overview

The Model Context Protocol (MCP) is the foundation of APM's architecture—all interactions happen through MCP, making APM a universal hub for AI-augmented workflows.

What is MCP?

MCP is an open protocol that enables:

  • 🔌 Tool Calling - AI agents can execute functions
  • 📊 Context Sharing - Systems share data seamlessly
  • 🔄 Event Broadcasting - Real-time notifications of changes
  • 🛠️ Resource Access - Structured data exposure

APM's Dual Role

APM as MCP Client

External MCP Server
APM
Execute Tools

APM as MCP Server

External MCP Client
APM
Create/Query Data

APM as MCP Client

Connect to external MCP servers to:

  • Execute tools from AI agents and services
  • Pull in external data and capabilities
  • Orchestrate complex multi-tool workflows

APM as MCP Server

APM exposes a powerful MCP server that allows:

  • External tools to create/update tasks and actions
  • AI agents to query project data
  • Workflow automation from any MCP client
  • Event subscriptions for real-time updates

Available APM Tools

createTask

Create a new task in a project

Parameters:
  • project_id - The project to create the task in
  • title - Task title (required)
  • description - Detailed task description
  • assignee_id - User or agent to assign to
  • implementation_plan - Step-by-step plan for completion

updateTask

Update an existing task

Parameters:
  • task_id - The task to update (required)
  • status - New status: unstarted, in_progress, complete
  • assignee_id - Reassign to different user/agent
  • title - Update the task title
  • description - Update the description

createAction

Create an approval/review action

Parameters:
  • type - Action type (e.g., implementation_plan, deployment_approval)
  • title - Action title (required)
  • priority - Priority level: low, medium, high, critical
  • assignee_id - Who should process this action
  • requester_id - Who is requesting the action
  • payload - Custom data for the action

updateAction

Process an action (approve/reject)

Parameters:
  • action_id - The action to update (required)
  • status - New status: approved, rejected, in_progress
  • resolution_notes - Explanation of the decision
  • assignee_id - Reassign if needed

getTasks

Query tasks with filters

Parameters:
  • project_id - Filter by project
  • assignee_id - Filter by assignee
  • status - Filter by status (array)
  • created_after - ISO timestamp for date filtering
  • limit - Maximum results to return

getActions

Query actions with filters

Parameters:
  • assignee_id - Filter by assignee
  • status - Filter by status (array)
  • priority - Filter by priority level
  • project_id - Filter by project
  • include_resolved - Include completed actions (default: false)

getProjects

List available projects

Parameters:
  • include_archived - Include archived projects
  • name_contains - Filter by name substring

Connection Methods

1. Stdio (Standard I/O)

For local command-line tools and scripts:

{
  "mcpServers": {
    "my-tool": {
      "command": "ruby",
      "args": ["my_mcp_server.rb"]
    }
  }
}

2. Network Transport (Coming soon)

3. APM CLI Bridge

Use the provided CLI tool to connect stdio-based MCP clients to APM. You can visit the MCP tab of the main menu to get your specific path but it will most likely be:

# Auto-discover and connect
/Applications/APM.app/Contents/MacOS/APM-MCP-Server

Event System

APM broadcasts real-time events that MCP clients can subscribe to:

Task Events

  • apm_task_created - New task added

Coming Soon:

  • apm_task_updated - Task modified
  • apm_task_completed - Task finished
  • apm_task_assigned - Task assignment changed
  • apm_task_started - Task work begun

Action Events (Coming Soon)

  • apm_action_created - New action needs attention
  • apm_action_updated - Action status changed
  • apm_action_approved - Action approved
  • apm_action_rejected - Action rejected

Project Events (Coming Soon)

  • apm_project_created - New project created
  • apm_project_updated - Project settings changed
  • apm_project_member_added - Team member joined
  • apm_project_member_removed - Team member left

Subscribing to Events

# Todo

Security & Permissions

  • Local Only: APM's MCP server only accepts local connections

Getting Started

Next Steps

Was this page helpful?