MCP Tools

Manage, test, and monitor MCP tool executions

Total Tools

84

Categories

14

Executions Today

0

0.0% success
Avg Duration

0ms

All Tools (84)

Availability (3)

Avatar (1)

Claude (3)

Communication (4)

DevOps (19)

Kb (5)

N8n (10)

Persona (6)

Project (8)

Queue (3)

Repository (6)

System (2)

Team (6)

Teams (8)

agent_message_get

Communication
Get a specific message by ID or get an entire message thread. Use to read full message content or see conversation history in a thread.

agent_message_list

Communication
List messages for a persona. Can list sent, received, or unread messages. Use to check for incoming requests, see conversation history, or track pending responses. Required: persona_id

agent_message_reply

Communication
Reply to a message from another persona. Creates a response in the same thread and notifies the original sender. Required: message_id, sender_persona_id, content

agent_message_send

Communication
Send a message to another persona, team, or project. Use for cross-team collaboration, requesting help, escalations, or task handoffs. Messages are delivered to available personas based on routing. Required: sender_persona_id, recipient_type, recipient_id, content

availability_get

Availability
Get real-time availability status for a persona. Shows current sessions, capacity, queue depth, and workload metrics. Use this to check if a persona can handle a new task.

availability_list

Availability
List real-time availability for all personas. Filter by status or team. Shows summary stats and individual persona status. Useful for finding available personas for task assignment.

availability_set_status

Availability
Set a persona's availability status (online/offline). Use this to temporarily disable a persona from receiving tasks, or to bring them back online. Required: online

avatar_generate

Avatar
Generate an avatar image using Google Gemini image generation models (Imagen 3.0). The tool automatically selects the best available model based on rate limits and tries fallback models if needed. Supports custom prompt enrichment for better results. Required: prompt

claude_exchange_code

Claude
Exchange a Claude authorization code for an OAuth token. Use this after visiting the auth URL and getting the code. This bypasses the expect script which may fail in Docker. Required: code

claude_list_credentials

Claude
List all Claude credentials with their status. Shows which accounts are active, pending auth, or failed.

claude_save_token

Claude
Directly save a Claude OAuth token to the database and local file. Use this to bypass the interactive auth flow when it fails in Docker. Token format: sk-ant-oat01-... Required: token

devops_add_pull_request_code_comment

DevOps
Add an inline code comment to a specific file and line in an Azure DevOps pull request. Use for code review feedback on specific lines. Required: project_name, repository_name, pull_request_id, file_path, line_number, comment

devops_add_pull_request_comment

DevOps
Add a general comment to an Azure DevOps pull request. For inline code comments, use devops_add_pull_request_code_comment instead. Required: project_name, repository_name, pull_request_id, comment

devops_add_work_item_comment

DevOps
Add a comment to an Azure DevOps work item. Supports HTML formatting. Required: project_name, work_item_id, comment

devops_assign_work_item

DevOps
Assign Azure DevOps work item to a user. Returns updated work item with assignment info. Use this to delegate work to team members. Required: project_name, work_item_id, assigned_to

devops_complete_pull_request

DevOps
Complete (merge) an Azure DevOps pull request into the target branch. Optionally delete the source branch after merge. Returns merge status. Use this after code review approval to merge changes. Required: project_name, repository_name, pull_request_id

devops_create_branch

DevOps
Create a new branch in an Azure DevOps repository. Optionally specify source branch (defaults to default branch). Returns success status. Use this to start new feature development or bug fixes. Required: project_name, repository_name, branch_name

devops_create_pull_request

DevOps
Create a new pull request in Azure DevOps. Optionally link work items to the PR. Required: project_name, repository_name, source_branch, target_branch, title, description

devops_create_work_item

DevOps
Create a new Azure DevOps work item (User Story, Bug, Task, Feature, Epic). Returns the created work item ID and details. Use this when starting new development work or reporting issues. Required: project_name, work_item_type, title

devops_get_pull_request

DevOps
Get details of an Azure DevOps pull request. Returns title, description, source/target branches, status, creator, linked work items, and changed files. Required: project_name, repository_name, pull_request_id

devops_get_pull_request_diff

DevOps
Get the diff/changes of an Azure DevOps pull request. Returns changed files with their content, additions, and deletions. Required: project_name, repository_name, pull_request_id

devops_get_work_item

DevOps
Get details of an Azure DevOps work item by ID. Returns title, description, state, type, priority, tags, and other metadata. Required: project_name, work_item_id

devops_list_branches

DevOps
List all branches in an Azure DevOps repository. Returns branch details including name, last commit, author, and date. Use this to discover available branches for development or PR creation. Required: project_name, repository_name

devops_list_pull_requests

DevOps
List Azure DevOps pull requests for a repository with optional filters (status, creator, reviewer, branch). Returns PR details including ID, title, status, source/target branches, and linked work items. Use this to monitor code reviews and merge status. Required: project_name, repository_name

devops_list_repositories

DevOps
List all Azure DevOps repositories for a project. Returns repository details including name, default branch, URLs, and size. Use this to discover available repositories for development work. Required: project_name

devops_list_work_items

DevOps
List Azure DevOps work items using WIQL (Work Item Query Language). Returns work item details including ID, title, state, assigned to, and more. Use this to find work items by criteria like state, type, or assigned user. Required: project_name

devops_set_pull_request_vote

DevOps
Set your vote on an Azure DevOps pull request. Options: 'approve' (10), 'approve_with_suggestions' (5), 'no_vote' (0), 'wait_for_author' (-5), 'reject' (-10). Required: project_name, repository_name, pull_request_id, vote

devops_update_pull_request

DevOps
Update Azure DevOps pull request title or description. Returns updated PR details. Use this to improve PR documentation or clarify changes. Required: project_name, repository_name, pull_request_id

devops_update_work_item

DevOps
Update Azure DevOps work item fields (title, description, state, priority, etc.). Returns updated work item details. Use this to modify existing work items. Required: project_name, work_item_id, fields

devops_update_work_item_state

DevOps
Update the state of an Azure DevOps work item. Common states: 'New', 'Active', 'Resolved', 'Closed', 'In Progress', 'Done'. Required: project_name, work_item_id, new_state

get_agent_status

System
Get the current status of the AI Agent including health, active tasks, and system information

get_whoami_on_azure

System
Get the Azure AD user identity that the AI Agent is connected as

kb_get_topic

Kb
Get full content of an AppKit pattern topic including code examples, step-by-step instructions, required packages, and common mistakes to avoid. Use the topic ID from kb_search results, or specify platform/category/topic path.

kb_list_categories

Kb
List pattern categories for a platform (e.g., 'dotnet' has datasource, service, entity, etc.). Optionally include topics for each category. Required: platform

kb_list_platforms

Kb
List available AppKit pattern platforms. Each platform contains categories of patterns (e.g., dotnet has datasource, service, entity, etc.)

kb_search

Kb
Search AppKit Knowledge Base for patterns, best practices, and code examples. Use this when you need to implement AppKit patterns like DataSource, Service, Entity, Validator, etc. Always search before writing AppKit code to ensure you follow the correct patterns. Required: query

kb_summary

Kb
Get a summary of the AppKit Knowledge Base including available platforms, total categories and topics. Use this to understand what patterns are documented.

n8n_activate_workflow

N8n
Activate or deactivate an n8n workflow. Active workflows run automatically on triggers (webhooks, schedules, etc.). Inactive workflows can only be executed manually. Use this to enable/disable automated workflows. Required: workflow_id, active

n8n_create_credential

N8n
Create a new n8n credential for API authentication. Supports various credential types (httpBasicAuth, httpHeaderAuth, oAuth2Api, etc.). Use this to securely store API keys and authentication tokens for workflow nodes. Required: name, type, data

n8n_delete_credential

N8n
Delete an n8n credential by ID. Warning: This will affect any workflows using this credential. Use this to remove outdated or unused credentials. Required: credential_id

n8n_execute_workflow

N8n
Execute an n8n workflow manually with optional input data. Returns execution ID, status, start time, and results. Use this to trigger automated workflows from AIAgent, such as data processing, notifications, or integrations. Required: workflow_id

n8n_get_execution

N8n
Get detailed information about a specific n8n workflow execution by ID. Returns complete execution data including node run data, results, errors, and timing. Use this to inspect execution results and debug workflow issues. Required: execution_id

n8n_get_workflow

N8n
Get detailed information about a specific n8n workflow by ID. Returns complete workflow definition including nodes, connections, settings, tags, and metadata. Use this to inspect workflow structure before execution or modification. Required: workflow_id

n8n_list_credentials

N8n
List all n8n credentials. Returns credential ID, name, type, and timestamps. Note: Sensitive credential data is not returned for security. Use this to discover available credentials for workflow configuration.

n8n_list_executions

N8n
List n8n workflow executions with optional filters. Returns execution ID, workflow ID, status, start/stop times, and completion status. Use this to monitor workflow execution history and track automation results.

n8n_list_workflows

N8n
List all n8n workflows with optional filters. Returns workflow ID, name, active status, tags, and timestamps. Use this to discover available workflows for execution or management.

n8n_retry_execution

N8n
Retry a failed n8n workflow execution. Creates a new execution using the same input data from the original execution. Use this to recover from transient errors or retry after fixing external dependencies. Required: execution_id

persona_assign

Persona
Assign a specific persona to handle messages from a Teams channel or DM conversation. This affects routing for future messages. Required: persona_code, channel_id

persona_capabilities

Persona
List all available persona capabilities (e.g., 'backend', 'frontend', 'devops') and tech stack expertise (e.g., '.NET', 'Vue.js') with counts

persona_get

Persona
Get detailed information about a specific AI persona by their unique code (e.g., 'PETER_PARKER', 'IRON_MAN') or ID

persona_list

Persona
List active AI personas with optional filtering by universe (Marvel, DC, StarWars, etc.) or capability (backend, frontend, devops, etc.)

persona_recommend

Persona
Analyze message content and recommend the best persona(s) to handle it based on topic, keywords, and required capabilities Required: message

persona_search

Persona
Search AI personas by name, alias, or code. Supports partial matching (e.g., 'Peter' will find 'Peter Parker', 'Spider' will find 'Spider-Man') Required: query

project_assign_team

Project
Assign personas to a project team. Use this to build a development team for a project by specifying persona codes or IDs for each role. Roles: product_owner, tech_lead, backend_developers, backend_qa, frontend_developers, frontend_qa, devops. Example: Assign PETER_PARKER as tech_lead and IRON_MAN as backend developer.

project_build_team

Project
Analyze a project's repositories and suggest/build a development team. Matches personas to required roles based on repository type, tech stack, and capabilities. Can auto-assign the suggested team or just return suggestions for review.

project_create

Project
Create a new project for AI Agent orchestration. Projects define how tasks from Azure DevOps are routed to personas. Required: display_name, devops_project

project_dependency_add

Project
Add a new dependency relationship between two projects. Use when you need to track that one project depends on another. Example: Project A (frontend) depends on Project B (shared library). Required: dependent_project_id, dependency_project_id, type

project_dependency_list

Project
List dependencies for a project. Can show what a project depends on (dependencies) or what depends on it (dependents). Also can show the full dependency graph or statistics.

project_dependency_trigger

Project
Trigger notifications to all projects that depend on a given project. Use when you've updated a package, API, or shared resource and need to notify dependent projects. Example: After publishing a new npm package version, trigger dependents to update. Required: project_id, reason

project_get

Project
Get detailed information about a specific project including team members. Can search by project ID or Azure DevOps project name.

project_list

Project
List all projects with their team assignments. Useful for seeing which projects exist and who is assigned to them.

queue_assign

Queue
Manually assign a queue item to a specific persona. Use when you want to override automatic assignment or assign to a specific person. Required: queue_id, persona_id

queue_prioritize

Queue
Update the priority of a queue item or escalate it. Use when a task needs urgent attention or should be deprioritized. Required: queue_id

queue_status

Queue
Get the task queue status including statistics and waiting items. Use to monitor queue health, check for pending tasks, and identify bottlenecks.

repository_analysis_get

Repository
Get the latest analysis results for a repository. Shows languages, frameworks, libraries, package dependencies, project references, and file statistics.

repository_analyze

Repository
Analyze a repository to detect languages, frameworks, package dependencies (NuGet, NPM, Pub), and build internal dependency graph. Can analyze by repository ID or name. Set force_reanalyze=true to re-analyze even if recent analysis exists.

repository_create

Repository
Create a new repository record in the system. Registers a repository with its DevOps connection, tech stack, and workspace configuration. After creation, use team_assignment_create to assign teams. Required: name, display_name, project_id, type, devops_project_name, devops_repo_name

repository_get

Repository
Get detailed information about a specific repository. Can search by ID, name, or alias. Returns clone URLs, tech stack, team assignments, and configuration.

repository_list

Repository
List all repositories in the organization. Shows repository details including clone URLs, tech stack, and assigned teams. Filter by project, type, or active status.

repository_update

Repository
Update an existing repository record. Modify display name, aliases, clone URLs, tech stack, or archive status. Use repository_get first to see current values.

team_assignment_create

Team
Assign a team to a project or repository. Specify the role (Developer, QA, Reviewer, etc.) and permissions. Set clone_to_workspace=true for teams that need the repo in their workspace. Required: team_id, role

team_assignment_delete

Team
Delete a team assignment. Removes a team's access to a project or repository. Use team_assignment_list first to find the assignment ID. Required: id, confirm

team_assignment_list

Team
List team assignments for projects and repositories. Shows which teams work on which repositories, their roles (Developer, QA, Reviewer, etc.), and permissions (canWrite, canApprove, canMerge, canDeploy).

team_assignment_update

Team
Update an existing team assignment. Modify role, permissions, priority, or workspace settings. Use team_assignment_list first to find the assignment ID. Required: id

team_get

Team
Get detailed information about a specific team including all members. Can search by team ID or code.

team_list

Team
List all organizational teams with their members. Teams are hierarchical (e.g., Engineering -> Backend, Frontend).

teams_channel_configure

Teams
Configure a Teams channel. Enable AutoRespond to receive @mentions, set default persona for the channel, or assign the channel to a project.

teams_channel_create

Teams
Create a new Teams channel in the configured AI Agent team. Can optionally link the channel to an existing project. If the channel already exists, it will be linked instead of created. Required: name

teams_channels_list

Teams
List all Teams channels registered in the system. Shows channel name, purpose, AutoRespond status, and associated project.

teams_reply_to_message

Teams
Reply to an existing message in a Microsoft Teams channel or chat thread. Required: channel_id, reply_to_id, message

teams_send_error_notification

Teams
Send an error notification to the configured Teams notification channel. Use for reporting errors and issues. Required: error

teams_send_message

Teams
Send a message to a Microsoft Teams channel or chat. Supports HTML formatting. Required: channel_id, message

teams_send_message_with_mentions

Teams
Send a message to Microsoft Teams with @mentions to specific users. Required: channel_id, message, mention_user_ids

teams_send_persona_response

Teams
Send a response as a persona with an Adaptive Card containing avatar, name, and universe info. Creates rich visual feedback in Teams. Required: chat_or_channel_id, persona_name, response_text