Documentation Index
Fetch the complete documentation index at: https://docs.parallel.ai/llms.txt
Use this file to discover all available pages before exploring further.
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.This feature is currently in beta and requires the
parallel-beta: mcp-server-2025-07-17 header when using the Task API.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 themcp_servers field in the Task API call. Each request can include up to 10 MCP servers.
| Parameter | Type | Description |
|---|---|---|
type | string | Always url. |
url | string | The URL of the MCP server. |
name | string | A name for the MCP server. |
headers | dict[string, string] | Headers for authenticating with the MCP server. |
allowed_tools | array[string] or null | List of tools to allow, or null for all. |
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
liteandcore, 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:| Parameter | Type | Description |
|---|---|---|
tool_call_id | string | Unique identifier for the tool call. |
server_name | string | Name of the MCP server, as provided in the input. |
tool_name | string | Name of the tool invoked. |
arguments | string | JSON-encoded string of the arguments used for the tool call. |
content | string | Response from the MCP server. |
error | string | Error message if the tool call failed. Either content or error will always be populated. |
warning field in the Task Run output
will be populated.