Vendor Onboarding MCP server ​

The Vendor Onboarding MCP server enables LLMs to onboard new vendors across Coupa, DocuSign, and NetSuite through natural conversation. It provides tools to capture vendor intake and check for duplicates, send and track tax and insurance documentation through DocuSign, confirm banking submission and approval status in Coupa, and create and activate the vendor master record in Coupa and NetSuite, without requiring direct interaction with the Coupa, DocuSign, and NetSuite interfaces. Onboarding a vendor can span days to weeks while you wait on the vendor and approvers, so the server tracks progress and lets you pick up an in-flight onboarding in any later conversation.

Uses ​

Use the Vendor Onboarding MCP server to perform the following actions:

• Check a new vendor's legal name against existing Coupa suppliers before creating a record
• Send tax forms and insurance documentation to a vendor for signature through DocuSign
• Check whether a vendor has completed and returned requested documents
• Import a completed DocuSign envelope's signer-entered data into the vendor's Coupa record
• Check whether a vendor has submitted banking details through Coupa's Supplier Portal
• Submit a vendor for approval through Coupa's configured approval chain
• Create the vendor master record in Coupa and NetSuite
• Activate a vendor for transactions
• List in-flight vendor onboardings and see what each one is waiting on

Example prompts ​

Use the following example prompts to invoke Vendor Onboarding MCP server tools:

• Onboard Acme Corp as a new vendor.
• What's the status of the Acme onboarding?
• Which vendor onboardings are stuck waiting on the vendor?
• Check whether Acme's banking has come in yet.
• Send the tax and insurance forms to Acme Corp.
• Has Acme signed and returned their documents yet?
• Import Acme's signed form data into their Coupa record.
• Submit Acme's onboarding for approval.
• Create the vendor master record for Acme now that it's approved.
• Activate Acme for transactions.

Vendor Onboarding MCP server tools ​

The Vendor Onboarding MCP server provides the following tools:

Install the Vendor Onboarding MCP server ​

Complete the following steps to install a prebuilt MCP server to your project:

Vendor Onboarding connection setup ​

The following connections are required to use the Vendor Onboarding MCP server:

• Coupa
• DocuSign
• NetSuite

Role requirements ​

Each tool's availability depends on the scopes and permissions granted to the relevant connection. A request made without the required permission returns a permission-denied outcome rather than a partial result.

• Coupa: Requires the following permissions at minimum: - Supplier Information (read, write) - Suppliers (read, write) - Easy Form Responses (read, write, approval submission) - Approvals (read) - Attachments (read, write)
• DocuSign: Requires the following: - impersonation scope (JWT Grant) or equivalent send-on-behalf-of access (OAuth 2.0) to send envelopes
• NetSuite: Requires the following: - RESTlets and REST Web Services scopes - A NetSuite role with permission to create and edit Vendor records

Coupa connection setup steps ​

DocuSign connection setup steps ​

https://account.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=YOUR_INTEGRATION_KEY&redirect_uri=https://www.workato.com/oauth/callback

https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=YOUR_INTEGRATION_KEY&redirect_uri=https://www.workato.com/oauth/callback

NetSuite REST connection setup steps ​

openssl ecparam -list_curves

openssl ecparam -name prime256v1 -genkey -noout -out private-key.pem

openssl ec -in private-key.pem -pubout -out public-key.pem

openssl req -new -x509 -key private-key.pem -out cert.pem -days 365

Project property configuration ​

The Vendor Onboarding MCP server supports the following project-level properties to control behavior and defaults:

How to use Vendor Onboarding MCP server tools ​

Refer to the following sections for detailed information on available tools:

initiate_vendor_request tool ​

The initiate_vendor_request tool captures new-vendor intake details, checks for duplicates against existing Coupa suppliers, presents a preview for your approval, then creates the Supplier Information Management (SIM) record. Your LLM calls this tool once to capture the vendor's details, then calls it again after receiving your approval to create the SIM record.

Try asking:

• Onboard Acme Corp as a new vendor.
• Set up Acme Industries LLC as a new supplier — annual spend is around $500,000 in IT services.
• Register this vendor even though a similar name already exists — it's a different company.

send_vendor_onboarding_documents tool ​

The send_vendor_onboarding_documents tool assembles a single composite DocuSign envelope combining tax forms (W-9/W-8) and supporting-document requests, presents a preview for your approval, then sends it to the vendor's contact. Your LLM calls this tool once to display the preview, then calls it again after receiving your approval to send the envelope.

Try asking:

• Send the tax and insurance forms to Acme Corp.
• Send Acme their onboarding documents now.
• What documents will Acme receive, and when do they expire?

check_vendor_document_status tool ​

The check_vendor_document_status tool returns the DocuSign envelope's current status and, after the vendor completes it, the extracted form data and a document manifest. Your LLM uses this tool to check whether a vendor has signed and returned their documents. This tool is read-only.

Try asking:

• Has Acme signed and returned their documents yet?
• Check the status of Acme's DocuSign envelope.
• What did Acme submit on their tax form?

import_vendor_form_data tool ​

The import_vendor_form_data tool downloads the vendor's completed documents from DocuSign, prepares the signer-entered form data for the Coupa SIM record, presents a preview with sensitive values masked, then writes the data and attaches the downloaded documents. Your LLM uses this tool in the following four call workflow:

1. check_vendor_document_status reports an envelope is complete.
2. get_vendor_write_policy maps the fields into a Coupa SIM write payload.
3. import_vendor_form_data displays a preview of the payload.
4. import_vendor_form_data commits the import after receiving your approval.

A signed envelope can return more fields than the deployment's mapping covers. The tool drops a field without a mapping entry instead of blocking the import, so confirm get_vendor_write_policy covers every field you need, especially sensitive fields.

Try asking:

• Import Acme's signed form data into their Coupa record.
• Write Acme's completed tax form into their vendor record.
• Show me what will be written to Acme's record before you import it.

check_vendor_bank_details tool ​

The check_vendor_bank_details tool checks whether the vendor has submitted banking details through Coupa's native Supplier Portal flow and returns masked account and routing numbers. Your LLM uses this tool to check on banking before submitting a vendor for approval. The tool is read-only and doesn't send a banking request to the vendor.

This tool reads a legacy SIM Easy Form Response. The server may not recognize a submission made through Coupa's newer Coupa Pay Payment Methods flow.

Try asking:

• Check whether Acme's banking has come in yet.
• Has Acme submitted their bank details?
• Show me what banking information Acme has submitted so far.

submit_vendor_for_approval tool ​

The submit_vendor_for_approval tool identifies the vendor's Easy Form Response(s), presents a preview of the responses and spend amount for your approval, then submits them into Coupa's configured spend-based approval chain. Your LLM calls this tool once to display the preview, then calls it again after receiving your approval to submit. Coupa determines the approver from its own configured chain at submission time, so the preview doesn't name the approver.

Try asking:

• Submit Acme's onboarding for approval.
• Send Acme's vendor record through Coupa approval.
• What spend amount will be submitted for Acme's approval?

create_vendor_master_netsuite tool ​

The create_vendor_master_netsuite tool prepares the fields needed to finalize the existing Coupa supplier and create the corresponding NetSuite vendor record, presents a preview for your approval, then writes to both systems, creating the vendor inactive in NetSuite until activation. Your LLM calls this tool once, after approval is complete, to display the preview, then calls it again after receiving your approval to commit the write. If a probable duplicate turns up at this stage, your LLM presents it and asks you how to proceed.

Try asking:

• Create the vendor master record for Acme now that it's approved.
• What fields will be written to Coupa and NetSuite for Acme?
• Finalize Acme's supplier record and create their NetSuite vendor.

activate_vendor_for_transactions tool ​

The activate_vendor_for_transactions tool previews the status change for each system, including inactive to active in Coupa and NetSuite, and then activates the vendor in both apps. This makes the vendor eligible for transactions and payments. Your LLM calls this tool once, after the vendor master is created, to display the preview, then calls it again after receiving your approval to activate.

Try asking:

• Activate Acme for transactions.
• Turn on Acme so we can start transacting with them.
• What changes when I activate Acme in Coupa and NetSuite?

list_pending_vendor_onboardings tool ​

The list_pending_vendor_onboardings tool returns a paginated list of the in-flight vendor onboardings you initiated, grouped by why each vendor onboarding is stalled. Your LLM uses this tool when you ask what's outstanding or which vendors are stuck. This tool is read-only.

Try asking:

• Which vendor onboardings are stuck waiting on the vendor?
• Show me what's outstanding in my vendor onboarding queue.
• List onboardings that are waiting on approval.

get_vendor_onboarding_status tool ​

The get_vendor_onboarding_status tool returns the full status of a vendor's onboarding across Coupa, DocuSign, and NetSuite, including the current blocker, if any, and who owes the next action. Your LLM uses this tool when you ask about a specific vendor's progress. This tool is read-only.

Try asking:

• What's the status of the Acme onboarding?
• What's holding up Acme's onboarding?
• Who still needs to act on Acme's vendor approval?

get_vendor_write_policy tool ​

The get_vendor_write_policy tool returns the deployment's configured docusign.form_data_mapping project property, which contains the field mapping, types, and sensitivity flags. The tool also returns a fixed list of fields import_vendor_form_data always rejects, regardless of configuration. Your LLM calls this tool before writing using the import_vendor_form_data tool. This tool is read-only.

Try asking:

• What fields will be written when I import Acme's documents?
• Which of Acme's submitted fields are treated as sensitive?
• Show me the write policy this server uses for importing vendor data.

Getting started ​

View and manage your MCP server tools in the Overview page Tools section. Tool management provides the following capabilities:

• Start tools
• Remove tools
• Edit tools
• Add tools
• Edit your LLM-facing MCP server description