How to Use the Nutrient Workflow MCP in CrewAI

Q: Can I filter tools in Nutrient Workflow for CrewAI?

Yes, use the toolfilter option in your agent setup. This lets you restrict access so agents only see the tools they actually need for their role.

Q: How does CrewAI handle memory with Nutrient Workflow?

Shared memory allows your agents to remember the output of gettask. This prevents redundant calls and speeds up your total document processing time.

Q: Does Nutrient Workflow support hierarchical crews in CrewAI?

It does. You can have a manager agent call listreports to oversee the performance of your worker agents in real-time.

Deploy autonomous document crews using CrewAI and the Nutrient Workflow MCP Server for hands-off signature management.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Nutrient Workflow MCP to CrewAI

Create your Vinkius account to connect Nutrient Workflow to CrewAI — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Nutrient Workflow with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Autonomous document crews

Assign a researcher agent to `list_requests` while a moderator agent uses `complete_task` to finalize signatures. They share memory to keep the process aligned. The crew executes these tasks sequentially or hierarchically. You set the rules, and the agents handle the document routing without you touching a file.

Automated process monitoring

Let your monitor agent call `get_process` to track progress across large document batches. It flags delays before they become bottlenecks. Use `list_user_tasks` to distribute work among your agents based on their assigned roles. This keeps your signature pipeline efficient and organized.

Role-based document control

Configure your agents with tool_filter to limit access to `start_request`. This ensures only specific members of your crew can initiate new workflows. Check for unauthorized attempts by auditing the results of `list_users`. Your crew can flag suspicious activity and halt the document process instantly.

Setup guide

Set up Nutrient Workflow MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Nutrient Workflow tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Nutrient Workflow Analyst",
    goal="Access and analyze Nutrient Workflow data via MCP.",
    backstory="Expert analyst with direct Nutrient Workflow access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Nutrient Workflow transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Nutrient Workflow Analyst",
        goal="Access and analyze Nutrient Workflow data via MCP.",
        backstory="Expert analyst with direct Nutrient Workflow access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Nutrient Workflow transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Nutrient Workflow. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Nutrient Workflow now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Nutrient Workflow MCP in CrewAI

Include the server URL in your agent definition. The crew will automatically discover the tools and make them available for your agents to use.

Yes, use the tool_filter option in your agent setup. This lets you restrict access so agents only see the tools they actually need for their role.

Shared memory allows your agents to remember the output of `get_task`. This prevents redundant calls and speeds up your total document processing time.

It does. You can have a manager agent call `list_reports` to oversee the performance of your worker agents in real-time.

The server enforces strict access controls via your endpoint token. No document data is shared outside your environment, and all tool interactions are logged.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript