Un servidor de protocolo de contexto de modelo para la integración de acciones de GitHub.
Este es un servidor MCP basado en TypeScript, diseñado para la integración con GitHub Actions. Ofrece las siguientes características:
Herramienta para obtener acciones de GitHub disponibles desde un repositorio
Herramienta para obtener información detallada sobre una acción específica de GitHub
Herramienta para activar eventos de envío del flujo de trabajo de GitHub
Herramienta para obtener las últimas versiones de un repositorio de GitHub
Related MCP server: GitHub MCP Server
get_github_actions : obtener las acciones de GitHub disponibles para un repositorio
Parámetros obligatorios: owner (propietario del repositorio, nombre de usuario u organización) y repo (nombre del repositorio)
Parámetros opcionales: token (token de acceso personal de GitHub, para acceder a repositorios privados o aumentar los límites de velocidad de la API)
Devuelve datos JSON con ID de flujo de trabajo, nombre, ruta, estado, URL y contenido
get_github_action : obtenga información detallada sobre una acción de GitHub específica, incluidas las entradas y sus requisitos
Parámetros obligatorios: owner (propietario de la acción, nombre de usuario u organización) y repo (nombre del repositorio de la acción)
Parámetros opcionales:
path : Ruta al archivo de definición de acción (predeterminado: 'action.yml')
ref : referencia de Git (rama, etiqueta o confirmación SHA, predeterminado: 'principal')
token : token de acceso personal de GitHub (opcional)
Devuelve información detallada sobre la Acción, incluido el nombre, la descripción, el autor, las entradas (y si son obligatorias), etc.
trigger_github_action : activa un flujo de trabajo de GitHub y pasa parámetros relevantes
Parámetros requeridos:
owner : Propietario del repositorio (nombre de usuario u organización)
repo : Nombre del repositorio
workflow_id : El ID o nombre de archivo del flujo de trabajo que se activará
Parámetros opcionales:
ref : La referencia git para activar el flujo de trabajo (predeterminado: 'principal')
inputs : Entradas que se pasarán al flujo de trabajo (deben coincidir con las entradas definidas del flujo de trabajo)
token : token de acceso personal de GitHub (debe tener el alcance del flujo de trabajo)
Devuelve información de ejecución del flujo de trabajo, incluido el estado, la URL, etc.
get_github_release : obtenga las 2 últimas versiones de un repositorio de GitHub
Parámetros obligatorios: owner (propietario del repositorio, nombre de usuario u organización) y repo (nombre del repositorio)
Parámetros opcionales: token (token de acceso personal de GitHub, opcional)
Devuelve información sobre los 2 últimos lanzamientos
La forma más sencilla de instalarlo y usarlo es a través del comando npx en el archivo de configuración de Claude Desktop sin instalación local manual:
{
"mcpServers": {
"github-action-trigger-mcp": {
"command": "npx",
"args": [
"-y",
"@nextdrive/github-action-trigger-mcp"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
}
}
}
}Beneficios de este método:
No se requiere instalación de paquetes locales
Utiliza automáticamente la última versión
Configúrelo una vez y listo para usar
Configuración de token de GitHub integrada
Si prefiere instalarlo manualmente, siga estos pasos:
Instalar el paquete:
npm install -g @nextdrive/github-action-trigger-mcpUso en la configuración de Claude Desktop:
En MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json En Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"github-action-trigger-mcp": {
"command": "@nextdrive/github-action-trigger-mcp",
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
}
}
}
}Para acceder a la API de GitHub, especialmente para repositorios privados o activadores de flujo de trabajo, necesitas configurar un token de acceso personal de GitHub. Hay varias maneras de hacerlo:
Establezca el token directamente en el archivo de configuración de Claude Desktop a través del campo env :
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
}Establezca la variable de entorno GITHUB_TOKEN :
# On Linux/MacOS
export GITHUB_TOKEN=your_github_token
# On Windows
set GITHUB_TOKEN=your_github_tokenEditar el archivo de configuración:
~/.nextdrive-github-action-trigger-mcp/config.jsonEstablezca su token de GitHub:
{
"githubToken": "your_github_token"
}Se crea automáticamente una plantilla para este archivo de configuración la primera vez que se inicia el servidor.
Instalar dependencias:
npm installConstruir el servidor:
npm run buildPara la reconstrucción automática durante el desarrollo:
npm run watchUtilice MCP Inspector para depurar:
npm run inspectorEl Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.
Si desea publicar este paquete en npm, siga estos pasos:
Asegúrate de haber iniciado sesión en npm y de tener permisos para publicar en la organización @nextdrive :
npm loginConstruir el proyecto:
npm run buildPublicar en npm (los paquetes con alcance de organización son privados de manera predeterminada, use --access public para hacerlos públicos):
npm publish --access publicDespués de publicar, cualquiera puede ejecutar esta herramienta usando el comando npx @nextdrive/github-action-trigger-mcp o usarla en su configuración de Claude Desktop.
Utilice la herramienta get_github_actions para obtener acciones de GitHub para un repositorio:
{
"owner": "username-or-org",
"repo": "repository-name"
}Si se configura un token predeterminado, se utilizará automáticamente al acceder a repositorios privados.
Ejemplo de respuesta:
[
{
"id": 12345678,
"name": "CI",
"path": ".github/workflows/ci.yml",
"state": "active",
"url": "https://github.com/owner/repo/actions/workflows/ci.yml",
"content": "name: CI\n\non:\n push:\n branches: [ main ]\n pull_request:\n branches: [ main ]\n\njobs:\n build:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v2\n - name: Setup Node.js\n uses: actions/setup-node@v2\n with:\n node-version: 16.x\n - name: Install dependencies\n run: npm ci\n - name: Build\n run: npm run build\n - name: Test\n run: npm test\n"
}
]Utilice la herramienta get_github_action para obtener información detallada sobre una acción específica:
{
"owner": "actions",
"repo": "checkout",
"ref": "v4"
}Ejemplo de respuesta:
{
"name": "Checkout",
"description": "Check out a Git repository at a particular version",
"author": "GitHub",
"inputs": [
{
"name": "repository",
"description": "Repository name with owner. For example, actions/checkout",
"default": "",
"required": false
},
{
"name": "ref",
"description": "The branch, tag or SHA to checkout.",
"default": "",
"required": false
}
],
"runs": {
"using": "node20",
"main": "dist/index.js"
}
}Utilice la herramienta trigger_github_action para activar un flujo de trabajo de GitHub:
{
"owner": "username-or-org",
"repo": "repository-name",
"workflow_id": "ci.yml",
"inputs": {
"deploy_environment": "production",
"debug_enabled": "true"
}
}Ejemplo de respuesta:
{
"success": true,
"message": "Workflow dispatch event triggered successfully",
"run": {
"id": 12345678,
"url": "https://github.com/owner/repo/actions/runs/12345678",
"status": "queued",
"conclusion": null,
"created_at": "2025-03-19T06:45:12Z",
"triggered_by": "API"
}
}Nota: Para activar flujos de trabajo se requiere lo siguiente:
El flujo de trabajo debe estar configurado para admitir el evento workflow_dispatch
El token de GitHub debe tener el permiso de alcance workflow
Los parámetros de entrada pasados deben coincidir con los definidos en el flujo de trabajo
Utilice la herramienta get_github_release para obtener las 2 últimas versiones de un repositorio:
{
"owner": "username-or-org",
"repo": "repository-name"
}Ejemplo de respuesta:
{
"count": 2,
"releases": [
{
"id": 12345678,
"name": "v1.0.0",
"tag_name": "v1.0.0",
"published_at": "2025-03-15T10:00:00Z",
"draft": false,
"prerelease": false,
"html_url": "https://github.com/owner/repo/releases/tag/v1.0.0",
"body": "Release notes for version 1.0.0",
"assets": [
{
"name": "app-v1.0.0.zip",
"size": 1234567,
"download_count": 42,
"browser_download_url": "https://github.com/owner/repo/releases/download/v1.0.0/app-v1.0.0.zip",
"created_at": "2025-03-15T10:05:00Z",
"updated_at": "2025-03-15T10:05:00Z"
}
],
"author": {
"login": "username",
"html_url": "https://github.com/username"
}
},
{
"id": 87654321,
"name": "v0.9.0",
"tag_name": "v0.9.0",
"published_at": "2025-03-01T10:00:00Z",
"draft": false,
"prerelease": true,
"html_url": "https://github.com/owner/repo/releases/tag/v0.9.0",
"body": "Pre-release notes for version 0.9.0",
"assets": [],
"author": {
"login": "username",
"html_url": "https://github.com/username"
}
}
]
}Enable auto-merge for a specific pull request. This will automatically merge the PR when all required checks pass.
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner of the repository (username or organization) | |
| repo | Yes | Name of the repository | |
| pull_number | Yes | The pull request number | |
| merge_method | No | The merge method to use when auto-merging (MERGE, SQUASH, or REBASE) | |
| token | No | GitHub personal access token (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. While it states the tool enables auto-merge and describes the triggering condition, it lacks critical information about permissions needed, whether this is reversible, rate limits, error conditions, or what happens to existing auto-merge settings. For a mutation tool with zero annotation coverage, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is perfectly concise with two sentences that directly communicate the core functionality. Every word earns its place, and it's front-loaded with the main purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address permissions, error handling, return values, or important behavioral details like whether this overrides existing settings or requires specific repository configurations. The context signals show this is a non-trivial operation (5 parameters, 3 required), warranting more comprehensive documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all 5 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, but it does provide context about the overall purpose that helps understand parameter usage. Baseline 3 is appropriate when schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Enable auto-merge') and the target resource ('for a specific pull request'), with additional detail about the automatic merging behavior when checks pass. It distinguishes itself from sibling tools (which are all read operations) by being a write/mutation tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It mentions the condition 'when all required checks pass' but doesn't specify what happens if checks fail or if there are other requirements like permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get detailed information about a specific GitHub Action, including inputs and their requirements
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner of the action (username or organization) | |
| repo | Yes | Repository name of the action | |
| path | No | Path to the action.yml or action.yaml file (usually just 'action.yml') | |
| ref | No | Git reference (branch, tag, or commit SHA, default: main) | |
| token | No | GitHub personal access token (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It describes what information is returned but lacks details on permissions required (e.g., public vs. private repos), rate limits, error conditions, or response format. For a tool with no annotations, this leaves significant behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core functionality and includes a useful detail about inputs and requirements. Every part of the sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description is minimally adequate for a read-only tool. It clarifies the scope (detailed info about a specific action) but doesn't address behavioral aspects like authentication needs or response structure. For a tool with 5 parameters and no structured safety hints, it should provide more context about usage constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't clarify 'path' defaults or 'token' usage scenarios). Baseline 3 is appropriate when schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get detailed information about a specific GitHub Action, including inputs and their requirements.' It specifies the verb ('Get') and resource ('GitHub Action') with additional detail about what information is retrieved. However, it doesn't explicitly differentiate from sibling tools like 'get_github_actions' (plural vs. singular).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_github_actions' (which likely lists multiple actions) or 'trigger_github_action' (which executes an action). There's no context about prerequisites, limitations, or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get available GitHub Actions for a repository
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner of the repository (username or organization) | |
| repo | Yes | Name of the repository | |
| token | No | GitHub personal access token (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, what authentication is required (though 'token' is optional in schema), rate limits, pagination, or what 'available' means (e.g., active vs. all actions). This leaves significant gaps for safe invocation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a straightforward tool, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'available GitHub Actions' entails (e.g., list format, metadata included), authentication needs despite an optional token, or error handling. Given the complexity of GitHub APIs and sibling tools, more context is needed for reliable use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond implying the tool fetches actions for a repository, which aligns with the schema but doesn't enhance parameter understanding. Baseline 3 is appropriate given high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('GitHub Actions for a repository'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_github_action' (singular) or 'get_github_release', leaving some ambiguity about scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, constraints, or relationships with sibling tools like 'get_github_action' (singular) or 'trigger_github_action', leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the latest 2 releases from a GitHub repository
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner of the repository (username or organization) | |
| repo | Yes | Name of the repository | |
| token | No | GitHub personal access token (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical details like whether it requires authentication (though the token parameter is optional in the schema), rate limits, error handling, or the format of returned data. This leaves significant gaps in understanding the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct sentence that efficiently conveys the core functionality without unnecessary words. It is front-loaded and appropriately sized for the tool's scope, making it easy to understand at a glance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of interacting with GitHub APIs, no annotations, and no output schema, the description is incomplete. It fails to address key aspects like authentication needs, rate limiting, error responses, or the structure of the release data returned, which are essential for effective tool usage in a real-world context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, clearly documenting all parameters (owner, repo, token). The description does not add any additional meaning or context beyond what the schema provides, such as explaining the 'latest 2 releases' constraint or token usage. Baseline 3 is appropriate as the schema handles parameter documentation adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('latest 2 releases from a GitHub repository'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_github_action' or 'get_github_actions', which focus on GitHub Actions rather than releases, so it misses full sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, such as when to choose it over other GitHub-related tools or how it fits into broader workflows. There is no mention of prerequisites, exclusions, or contextual usage scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Trigger a GitHub workflow dispatch event with custom inputs
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner of the repository (username or organization) | |
| repo | Yes | Name of the repository | |
| workflow_id | Yes | The ID or filename of the workflow to trigger | |
| ref | No | The git reference to trigger the workflow on (default: main) | |
| inputs | No | Inputs to pass to the workflow (must match the workflow's defined inputs) | |
| token | No | GitHub personal access token (must have workflow scope) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'trigger' and 'custom inputs,' which implies a write operation, but lacks details on permissions required (beyond the token parameter), rate limits, whether the action is idempotent, what happens on failure, or the expected response format. This leaves significant gaps for an agent to understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose ('Trigger a GitHub workflow dispatch event') and adds necessary context ('with custom inputs'). There is no wasted verbiage, and it directly communicates the tool's function without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of triggering GitHub actions (a write operation with multiple parameters and no output schema), the description is insufficient. It lacks details on behavioral aspects like authentication needs, error handling, or response structure, which are critical for an agent to use the tool effectively. The high schema coverage helps with parameters, but overall completeness is poor due to missing operational context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, so the schema already documents all six parameters thoroughly. The description adds minimal value beyond implying that 'custom inputs' map to the 'inputs' parameter, but it doesn't provide additional syntax, format details, or constraints not covered in the schema. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('trigger') and resource ('GitHub workflow dispatch event') with additional context ('with custom inputs'). It distinguishes from sibling tools like 'get_github_action' or 'enable_pull_request_automerge' by focusing on initiating workflows rather than retrieving information or modifying settings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is provided on when to use this tool versus alternatives. While it's implied for triggering workflows, there's no mention of prerequisites (e.g., needing a GitHub token with specific scopes), when not to use it (e.g., for manual triggers vs. automated ones), or how it differs from other workflow-related tools in the ecosystem.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0enable_pull_request_automergeget_github_actionget_github_actionsget_github_releasetrigger_github_actionScored across 5 tools
Most tools have distinct purposes: enabling auto-merge, getting action details, listing available actions, fetching releases, and triggering actions. However, 'get_github_action' and 'get_github_actions' could be slightly confusing as they both retrieve action information but differ in scope (single vs. multiple). The descriptions clarify this, but the names are similar enough to cause potential misselection.
The naming follows a consistent verb_noun pattern with 'get', 'enable', and 'trigger' as verbs, all using snake_case. The only minor deviation is 'enable_pull_request_automerge' which includes a compound noun, but it still fits the overall style. This consistency makes the tools predictable and easy to understand.
With 5 tools, the count is well-scoped for a GitHub Action Trigger server, covering key operations like triggering actions, managing auto-merge, and retrieving related information. It's slightly lean but reasonable, as it focuses on core functionality without unnecessary bloat, though a few more tools might enhance coverage.
The toolset covers triggering actions and getting action/release info, but has notable gaps. For example, there's no way to disable auto-merge, manage action runs (e.g., cancel or list workflows), or handle other GitHub Actions lifecycle aspects like secrets or environments. This limits agents to basic triggering and info retrieval, with missing operations that could cause workarounds or failures.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol server for Wix AI tools
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
