How to Use the Nutrient Workflow MCP in VS Code Copilot

Q: How do we share the Nutrient Workflow config across our team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and add the server configuration. When your team members open the project in VS Code with Copilot active, they will automatically have access to the tools.

Q: Can VS Code Copilot trigger a live Nutrient Workflow process?

Yes, Copilot can initiate active workflows. By invoking startrequest directly from the chat panel, your agent can start a document run to test your integration end-to-end.

Q: How do developers inspect specific task states using Nutrient Workflow in VS Code Copilot?

Developers can ask Copilot to run gettask or listusertasks to inspect the live state of any document step. This brings real-time debug information directly into the editor.

Q: What is the best way to list active requests during development?

You can use the listrequests tool. Your agent will fetch the active queue and display the status of your running documents directly in the chat panel.

Share PDF workflow tools across your engineering team inside VS Code Copilot with zero manual setup.

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 VS Code Copilot

Create your Vinkius account to connect Nutrient Workflow to VS Code Copilot — 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Standardize document workflows across your team

The `list_processes` tool exposes your entire catalog of document templates directly to VS Code Copilot. By committing the configuration to your repository, every developer on your team instantly gains access to the same live process definitions. Your agent uses this tool to help developers build UI components that map perfectly to your backend document configurations. This eliminates configuration drift across your engineering team. Developers can query `get_process` to inspect the exact input fields required for a signature step. This shared context ensures your frontend forms always align with your document backend.

Debug production reports using this MCP Server

The `list_reports` tool retrieves operational metrics directly into your Copilot chat interface. When troubleshooting slow document turnarounds, your agent calls this tool to analyze execution times across different stages. It pairs this with `list_requests` to identify if specific servers or users are causing delays. You can run these diagnostic queries without accessing production databases or opening separate dashboards. Your agent parses the JSON payload and points you directly to the bottleneck in your code or configuration. This speeds up incident response for your document pipelines.

Verify user routing rules inside VS Code Copilot

The `list_users` tool pulls your tenant's user directory directly into your editor environment via this MCP Server. When writing complex routing rules for contract approvals, your agent uses this list to verify that user IDs match your code configurations. It ensures that tasks triggered by `start_request` are routed to valid accounts. This prevents runtime routing errors before you commit your code. Your agent checks your local routing tables against the live user directory fetched by the server. You catch mismatched IDs early in the development lifecycle.

Setup guide

Set up Nutrient Workflow MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Nutrient Workflow MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Nutrient Workflow tools listed. Try asking: "List my recent Nutrient Workflow transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "nutrient-workflow-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and add the server configuration. When your team members open the project in VS Code with Copilot active, they will automatically have access to the tools.

Yes, Copilot can initiate active workflows. By invoking `start_request` directly from the chat panel, your agent can start a document run to test your integration end-to-end.

Developers can ask Copilot to run `get_task` or `list_user_tasks` to inspect the live state of any document step. This brings real-time debug information directly into the editor.

You can use the `list_requests` tool. Your agent will fetch the active queue and display the status of your running documents directly in the chat panel.

All communication with the server is encrypted using enterprise-grade protocols. Your reports and user directories are processed ephemerally within Vinkius's secure sandbox, ensuring no sensitive organizational structures are ever exposed or stored.

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