MCP — call_endpoint sends form fields

mcp

call_endpoint takes a form argument: text fields sent as multipart/form-data, for routes that take a form instead of JSON. ElevenLabs speech-to-text is one; until now it answered a JSON body from MCP with 422, so an agent could not transcribe through MCP. Pass model_id and cloud_storage_url in form. body and form cannot be combined, and uploading a file still needs a direct HTTP call. Guides: MCP, ElevenLabs.

MCP — a JSON object over 512 KB is cut to fit

mcp

call_endpoint used to return a JSON object over the 512 KB cap as text cut mid-way, which no agent could parse. Now it is cut down to fit and comes back as JSON when it can be: a list keeps its first items, a string keeps its start, and each cut is listed in omitted with its path and size. An object over 8 MB, or one that cannot be cut down, still comes back as cut text. The case that exposed it: Scrapfly pages that asp renders in a browser carry every XHR in result.browser_data; add proxified_response=true to receive only the content or the extraction. Guides: MCP, Scrapfly.

MCP — sign in with your NativePort account

mcp

An agent can connect to the MCP server by signing in with your NativePort account instead of sending a key: add https://api.nativeport.ai/mcp with no Authorization header and approve the connection in the browser. Claude, Claude Code, ChatGPT and Codex already sign in this way. Approved apps appear under Connected apps in the panel, where you can revoke them; for now, a revoked app cannot sign in to the same account again. An account that was never opened in the panel now gets a message saying so, instead of a sign-in loop. A key remains the way to connect without a browser. Guide: MCP.