Skip to content
MCP-BridgeMCP-Bridge
Developer ToolsAuto-generatedScore: 34

AGCO API MCP Server

AGCO API API

Quick Answer

  1. 1. The AGCO API MCP server lets Claude, Cursor, and VS Code interact with the AGCO API API through natural language.
  2. 2. Setup: Add the config to claude_desktop_config.json, set your environment variables, and restart.
  3. 3. 10 operations available including No Documentation Found., Activate or Deactivate an ECU, or Report an ECU as Damaged., Get injector codes given engine., and more.
  4. 4. Quality score: 34/99fair source quality and documentation coverage.

Overview

Category: Developer Tools

Auth: None

Endpoints: 10

Transport: STDIO

Command: npx -y @mcp/agco-ats-com

Spec: vv1

Setup time: ~30 sec (no auth)

Environment Variables

AGCO_API_API_KEY

Example: your_agco_api_api_key

One-Click Install

Copy the snippet for your MCP client and paste it in — zero editing required.

Claude Desktop

Add to claude_desktop_config.json

{
  "mcpServers": {
    "agco-ats-com": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp/agco-ats-com"
      ],
      "env": {
        "AGCO_API_API_KEY": "your_agco_api_api_key"
      }
    }
  }
}
Deep link

Cursor

Settings → MCP Servers → Add

{
  "mcpServers": {
    "agco-ats-com": {
      "url": "https://mcpbridge.org/config/agco-ats-com.json"
    }
  }
}

Saves as .cursor/mcp.json in the download. Move it to your project root.

Deep link install →

VS Code

Use with MCP extension

{
  "mcpServers": {
    "agco-ats-com": {
      "url": "https://mcpbridge.org/config/agco-ats-com.json"
    }
  }
}

MCP Server Configuration

Add this to your claude_desktop_config.json or Cursor MCP settings.

{
  "mcpServers": {
    "agco-ats-com": {
      "command": "npx",
      "args": ["-y","@mcp/agco-ats-com"],
      "env": {
      "AGCO_API_API_KEY": "your_agco_api_api_key"
}
    }
  }
}

What You Can Build

With the AGCO API MCP server, your AI assistant can:

  • Access 10 API operations through natural language
  • Read, create, and modify developer tools resources without writing HTTP requests
  • Chain multiple operations in a single conversation for complex workflows
  • Combine with other MCP servers for cross-tool automation

Endpoints

GET/api/v2/AftermarketServices/Certificates

No Documentation Found.

PUT/api/v2/AftermarketServices/ECUs/{serialNumber}

Activate or Deactivate an ECU, or Report an ECU as Damaged.

GET/api/v2/AftermarketServices/Engines/{serialNumber}/IQACodes

Get injector codes given engine.

PUT/api/v2/AftermarketServices/Engines/{serialNumber}/IQACodes

Report the IQA codes used by an engine

GET/api/v2/AftermarketServices/Engines/{serialNumber}/ProductionData

Get production calibration data for given engine.

GET/api/v2/AftermarketServices/Hello

Check whether there is connectivity to AGCO Power Web Services

GET/api/v2/AftermarketServices/UserStatuses

Retrieve the status of an EDT Kit Registration with AGCO Power Web Services

PUT/api/v2/AftermarketServices/UserStatuses

Update the status of an EDT Kit Registration with AGCO Power Web Services

PUT/api/v2/AuthenticatedUsers/{UserID}/Tokens

Manage API tokens.

POST/api/v2/Authentication

Authenticate a user.

Authentication

No authentication required. This MCP server can be used without API keys.

Spec Version

Version: v1

Spec version published with the OpenAPI document. Config auto-updates when the spec changes.

Page last updated: June 13, 2026

Quality Score

34/99Fair
  • +Auto-generated (+12)
  • +OpenAPI spec available (+8)
  • +10 endpoints (+14)

Own this API?

Claim your listing to update description, links, and category — and get a verified badge.

Claim this listing →