Skip to content
Confirm MCP server compatibility
Public Preview

MCP server compatibility, schema rules, and call contract

Lists MCP server compatibility requirements, Tool schema rules, authentication modes, and the call contract for connecting an MCP server to Duale AI.

This reference covers MCP server compatibility requirements, authentication mode selection, and the MCP call contract for Duale AI connections.

  • MCP server compatibility and tool schema requirements.
  • Authentication mode selection and credential validity.
  • MCP call contract, error handling, and tool pause behavior.

Summaries were generated by AI.

Check that an MCP server meets these requirements before you connect it. Tool limits lists the catalog and call limits.

Confirm MCP server compatibility

An MCP Connection supports Streamable HTTP at one exact public HTTPS URL, with no user name, password, query string, or fragment. The server must negotiate MCP 2025-06-18, 2025-11-25, or 2026-07-28, and answer at that URL without a redirect. It must also work without cookies and send uncompressed responses.

Duale AI offers a Tool to a model only when the Tool meets these conditions:

  • Its input schema is a JSON object schema. The top level declares "type": "object", with properties as an object and required as an array when they are present. At the top level, a call uses only properties, required, and $defs. A call carries only the arguments that properties lists.
  • No top-level argument name starts with two underscores (__). Reserved argument names explains how to fix it.

The Catalog view shows an incompatible Tool with its reason.

Choose one authentication mode

Choose no authentication, one bearer token, or one API key in a custom header. The header name cannot be one that HTTP, authentication, or MCP reserves, such as Authorization or a name that starts with MCP-. Duale AI runs no OAuth sign-in flow. Use a credential that stays valid, and replace it in the Connection before it expires: an expired credential makes catalog checks fail, and the catalog becomes Expired.

Understand the MCP call contract

Return text or structured content from every Tool. A call ends as Unsupported, even when its result also carries text, if the result:

  • asks for more input (input_required);
  • returns an MCP task handle;
  • contains an image, audio, embedded resource, or resource-link block.

The server has already run the Tool, so any change it made stands.

Report a failure that the model can act on, such as a rate limit, as a Tool error result (isError: true): the call ends as Failed, and the model reads your error text. An HTTP error status or an MCP protocol error in answer to a Tool Call ends it as Outcome unknown, because Duale AI cannot tell whether the server ran the Tool.

Duale AI does not repeat a call if the server possibly received it. When it cannot confirm the response, the call ends as Outcome unknown, as Read a Tool Call outcome defines. The model can still request the same operation in a later turn, so make a Tool that changes data safe to call twice. Secure integration gives the controls.

After repeated technical failures of one Tool, Duale AI pauses calls to that Tool. Answer MCP Tool Calls states how many failures start a pause and how long it lasts. During the pause, a call to that Tool reports that the Tool is temporarily paused and ends as Failed without reaching the server. A Tool error result does not count toward a pause.