Jun Yi
11/10/2025, 8:45 AMError: MPC -32602: MCP error -32602: Invalid arguments for tool contract-testing_generate_pact_tests: [
{
"received": "python",
"code": "invalid_enum_value",
"options": [
"javascript",
"typescript",
"java",
"golang",
"dotnet",
"kotlin",
"swift",
"php"
],
"path": [
"language"
],
"message": "Invalid enum value. Expected 'javascript' | 'typescript' | 'java' | 'golang' | 'dotnet' | 'kotlin' | 'swift' | 'php', received 'python'"
}
]
Thanks!Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Jun Yi
11/11/2025, 6:45 AMJun Yi
11/11/2025, 6:45 AMJun Yi
11/11/2025, 9:46 AMMatt (pactflow.io / pact-js / pact-go)
just to double check, on-prem PactFlow on an air-gapped environment does not support MCP?it only supports the MCP commands that are not the AI ones hosted on pactflow cloud (code generation and code review). e.g. it supports the can-i-deploy query, and provider states endpoints etc. (these are available on both on-prem and OSS Pact Brokers)