Skip to main content
For AI agents: a documentation index is available at https://docs.parallel.ai/llms.txt. The full text of all docs is at https://docs.parallel.ai/llms-full.txt. You may also fetch any page as Markdown by appending .md to its URL or sending Accept: text/markdown.

Overview

The Parallel API allows you to specify remote MCP servers for Task API execution. This enables the model to access tools hosted on remote MCP servers without needing a separate MCP client.

Specifying MCP Servers

MCP servers are specified using the mcp_servers field in the Task API call. Each request can include up to 10 MCP servers.

Sample Request

Restrictions

  • Only MCP servers with Streamable HTTP transport are currently supported.
  • From the MCP specification, only tools are supported.
  • For MCP servers using OAuth, you must generate the authorization token separately and include it as a bearer token in the headers.
  • You can specify up to 10 MCP servers per request, but using fewer is recommended for optimal result quality.

Using MCP Servers in the Task API

When you make a Task API request, the API first fetches the available tools from the specified MCP servers. The processor will invoke tools from these servers if it determines they are useful for the task. The number of tool calls depends on the processor:
  • For lite and core, at most one tool is invoked.
  • For all other processors, multiple tool calls may be made.

Response Content

The Task API response includes a list of tool calls made during execution. Each tool call entry contains: If there is an authentication issue with any MCP server, the top-level warning field in the Task Run output will be populated.