How to integrate Nutrient Document Web Services API MCP with OpenAI Agents SDK

This guide walks you through connecting Nutrient Document Web Services API to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Nutrient Document Web Services API agent that can build documents, convert web pages to pdfs, ocr scanned pdfs, stage redactions, and add watermarks through natural language commands. This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Nutrient Document Web Services API account through Composio's Nutrient Document Web Services API MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Nutrient Document Web Services API logoNutrient Document Web Services API
Api Key

Nutrient Document Web Services API is a cloud document processing service for converting, OCRing, redacting, signing, and analyzing files. Use it to automate complex PDF and document workflows without running document infrastructure yourself.

11 Tools

Introduction

This guide walks you through connecting Nutrient Document Web Services API to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Nutrient Document Web Services API agent that can build documents, convert web pages to pdfs, ocr scanned pdfs, stage redactions, and add watermarks through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Nutrient Document Web Services API account through Composio's Nutrient Document Web Services API MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Nutrient Document Web Services API with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Nutrient Document Web Services API
  • Configure an AI agent that can use Nutrient Document Web Services API as a tool
  • Run a live chat session where you can ask the agent to perform Nutrient Document Web Services API operations

What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

What is the Nutrient Document Web Services API MCP server, and what's possible with it?

The Nutrient Document Web Services API MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Nutrient Document Web Services API account. It provides structured and secure access to document processing and account usage, so your agent can create and convert documents, OCR and improve PDFs, stage redactions, add watermarks, and check costs and usage on your behalf.

  • Document creation and conversion: Have your agent build documents from remote files, HTML, and new pages, or convert Markdown and public web pages into PDFs.
  • Searchable and accessible PDFs: Let the agent apply OCR to scanned PDFs or add screen-reader tags for PDF/UA accessibility.
  • Redaction review: Direct your agent to find matching content in a remote PDF and prepare a review copy with unapplied redaction marks.
  • PDF watermarking: Instruct your agent to add positioned text or image watermarks to every page of a PDF.
  • Cost and usage checks: Have your agent estimate a document job's required credits before processing, then review subscription status, remaining credits, and Processor usage.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Nutrient Document Web Services API project
  • Some knowledge of Python or Typescript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
3

Install dependencies

npm install @composio/openai-agents @openai/agents dotenv

Install the Composio SDK and the OpenAI Agents SDK.

4

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

5

Import dependencies

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Nutrient Document Web Services API.
6

Set up the Composio instance

dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
What's happening:
  • dotenv.config() loads your .env file so COMPOSIO_API_KEY and USER_ID are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.
7

Create a Tool Router session

// Create Tool Router session for Nutrient Document Web Services API
const session = await composio.create(userId as string, {
  toolkits: ['nutrient_document_web_services_api'],
});
const mcpUrl = session.mcp.url;

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only nutrient_document_web_services_api.
  • The router checks the user's Nutrient Document Web Services API connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Nutrient Document Web Services API.
  • This approach keeps things lightweight and lets the agent request Nutrient Document Web Services API tools only when needed during the conversation.
8

Configure the agent

// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Nutrient Document Web Services API. Help users perform Nutrient Document Web Services API operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Nutrient Document Web Services API and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a hostedMcpTool that connects to the MCP server URL we created earlier.
  • The headers object includes the Composio API key for secure authentication with the MCP server.
  • requireApproval: 'never' means the agent can execute Nutrient Document Web Services API operations without asking for permission each time, making interactions smoother.
9

Start chat loop and handle conversation

// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
What's happening:
  • The program prints a session URL that you visit to authorize Nutrient Document Web Services API.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using run().
  • The responses are printed to the console.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Nutrient Document Web Services API and OpenAI Agents SDK:

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['nutrient_document_web_services_api'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Nutrient Document Web Services API. Help users perform Nutrient Document Web Services API operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});

Conclusion

This was a starter code for integrating Nutrient Document Web Services API MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Nutrient Document Web Services API.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Nutrient Document Web Services API action and event your agent gets out of the box.

Analyze Build Cost

Estimate the credits and Processor features required by Build API instructions without executing the document job or consuming credits.

Build Document

Synchronously create one document from remote files, remote HTML, new pages, and composable safe actions, returning its filename, media type, and Base64 content up to 4 MB.

Convert Markdown to PDF

Convert CommonMark or GitHub-Flavored Markdown text into a PDF using optional built-in styling, custom CSS, page layout, and syntax highlighting settings.

Create PDF from Web Page

Render an HTML web page at a public URL, with optional page layout settings, into a PDF.

Get Account Information

Return the connected Nutrient account's subscription type, status, and estimated remaining credits.

Get Processor Usage

Return the connected account's Processor subscription status and credit usage counters.

Make PDF Accessible

Auto-tag a PDF at a remote URL for PDF/UA screen-reader accessibility and return the result's filename, media type, and Base64 content up to 4 MB.

OCR PDF

Apply optical character recognition to a PDF at a remote URL and return a searchable PDF's filename, media type, and Base64 content up to 4 MB.

Revoke JWT Token

Immediately revoke a bearer token created by CREATE_JWT_TOKEN using its ID.

Stage PDF Redactions

Find matching content in a remote PDF and return a review PDF's filename, media type, and Base64 content up to 4 MB with unapplied redaction marks.

Watermark PDF

Add a positioned text or image watermark to every page of a PDF at a public URL and return the copy's filename, media type, and Base64 content up to 4 MB.

FAQ

Frequently asked questions

With a standalone Nutrient Document Web Services API MCP server, the agents and LLMs can only access a fixed set of Nutrient Document Web Services API tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Nutrient Document Web Services API and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. OpenAI Agents SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Nutrient Document Web Services API tools.

Yes, absolutely. You can configure which Nutrient Document Web Services API scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Nutrient Document Web Services API data and credentials are handled as safely as possible.

Start with Nutrient Document Web Services API.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Nutrient Document Web Services API tool your agent needs.Free to start.

Start building