Questions about installing and using Docusign MCP Server connectors in your AI agent? Ask us here.

hey brendyn.

im currently trying to use the docusign mcp connector in claude to write information from a form into a docusign agreement. i have created the template in docusign, but haven’t found out how to actually write to the fields i need to. i set those fields to sender fields because it looked like that’s what the docs said, but i still seem to be having trouble. 

im even more confused because i was able to write to this a couple of days ago but now i can’t  

 

Hey ​@Jarred0926! Thanks for question, and sorry you're experiencing trouble!

Setting fields to ‘sender’ is the correct approach for the MCP connector, so you're on the right track. To help troubleshoot, can you please answer a few quick question?

1. Just to confirm: when you say ‘form’, do you mean a set of questions or inputs inside Claude (or a Claude-based UI) that collects values like name, amount, and dates need to be filled in the agreement? And ‘template’ is for the Docusign agreement that you want to send?

2. What type of fields are you trying to write to? (e.g., text fields, dropdown, checkbox, etc.)

3. When it stopped working, did anything change on your end? (e.g. updating your MCP configuration, regenerating your access token, modifying the template, etc)

4. What does Claude show when it fails? Is there an error message, or does it technically succeed but the fields end up empty in the envelope?

5. Are you using the same template as before, or did you create a new version?

This will help us narrow down whether it's a configuration issue or something that changed in the beta. Since the MCP Server is in open beta, it's possible a recent release affected this workflow.

Hey ​@emily.cook! 

I think the issue is coming from the fact that i built a template in a demo account that didn’t have permissions to add the pre-fill sender fields. For transparency, I’m building this solution out for a client of mine. I’m going to test from his Docusign account later today. 

To answer some of your questions. 

1. When I said form I meant template that I created on Docusign itself.
   
   
   2. Im trying to write text fields 
   
   3. It will populate the template but the fields are blank. 
   
   I’ll update you once I try with him. 

Hey ​@Jarred0926! Just checking in, did it work? If not I can have someone on the team jump in to help figure it out

Hi, does the DocuSign MCP connector support accessing agreements and taking actions in CLM?

Has anyone gotten Cursor (or another MCP client) past OAuth? Unauthenticated calls to mcp-d / mcp.docusign.com return 403 RBAC with no WWW-Authenticate.”

**Cursor cannot start OAuth against DocuSign MCP — unauthenticated requests return 403 without WWW-Authenticate**

I’m trying to connect Cursor to the DocuSign MCP server (open beta):

- Demo: `https://mcp-d.docusign.com/mcp`
- Prod: `https://mcp.docusign.com/mcp`

Cursor never reaches `needsAuth` / the OAuth browser flow. The MCP server stays in `error`.

**What happens**

An unauthenticated request to either endpoint returns **HTTP 403** with body **“RBAC: access denied”**, and **no `WWW-Authenticate` header**.

Per the MCP authorization spec, an unauthenticated request should return **401** plus something like:

```http
WWW-Authenticate: Bearer resource_metadata="https://mcp.docusign.com/.well-known/oauth-protected-resource"
```

(or the demo equivalent). A plain 403 is treated as “a token exists but permissions are insufficient,” so spec-compliant clients (including Cursor) never start OAuth.

Cursor staff confirmed this is not a client-config issue. The Integration Key / Client ID + Secret never get used, because OAuth never starts. Details: [Cursor forum 167942](https://forum.cursor.com/t/docusign-mcp-plugin-rbac-access-denied-never-reaches-oauth-needsauth/167942).

**Ask**

Please update the MCP gateway so unauthenticated requests return **401 + `WWW-Authenticate: Bearer resource_metadata="..."`** (prod and demo). Similar server-side pattern: [MCP OAuth + Entra ID writeup](https://forum.cursor.com/t/working-solution-mcp-server-oauth-with-microsoft-entra-id-on-azure-container-apps/151813).

Happy to provide HAR / `curl -i` output if useful.