2 months ago
Hi Railway Support Team,
I create an airtable mcp server with n8n and experiencing a critical bug with write operations.
Issue Summary:
Working: Read, Search, Delete, and Get operations work perfectly
Failing: Create, Update, and Upsert operations consistently fail with error:
"Your request is invalid or could not be processed by the service"
Technical Details: The issue appears to be identical to this known n8n community bug: https://community.n8n.io/t/airtable-create-upsert-nodes-not-working-via-mcp-server-trigger/130841
Root Cause: The MCP server is incorrectly sending field data to Airtable's API. Instead of wrapping field data in a fields
object as required by Airtable's API specification, it's sending field names as top-level parameters.
Current (Incorrect) Format Being Sent:
{
"Base": "app1JajG25DmqsKm1",
"Table": "Table 1",
"Name": "Test Record",
"Notes": "Test notes",
"Typecast": true
}
Required (Correct) Format:
{
"fields": {
"Name": "Test Record",
"Notes": "Test notes"
},
"typecast": true
}
My Configuration:
{
"mcpServers": {
"airtable-n8n": {
"command": "C:\\Users\\Legion\\AppData\\Roaming\\npm\\supergateway.cmd",
"args": [
"--streamableHttp",
"https://primary-production-f0de0.up.railway.app/mcp/airtable-mcp",
"--outputTransport",
"stdio",
"--header",
"Authorization: Bearer [my_token]"
]
}
}
}
Request:
Can you confirm if this is a known issue?
Do you have a timeline for when this bug will be fixed?
Is there an updated version of the MCP server available?
Can you provide a workaround or alternative endpoint?
Additional Context:
I've verified my API token has proper create/update permissions
I've tested with multiple Airtable bases with the same result
The error occurs consistently across different field types and configurations
This bug is preventing me from using the MCP server for any write operations to Airtable. Any assistance or timeline for a fix would be greatly appreciated.
Thank you for your help!
Best regards,
1 Replies
a month ago
Probably best to hit up the MCP author directly. They should have a GitHub where you can open an issue.