> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Build with Docusign and AI > Explore how to build with Docusign and AI tools, including LLM-assisted experiences and MCP integrations that help you develop faster and support smarter agreement workflows. Docusign helps organizations prepare, sign, act on, and manage agreements. As large language models (LLMs) become a standard part of how developers work with APIs and documentation, Docusign is introducing tools that bring AI directly into the developer experience. From the [Docusign Developer AI Assistant for VS Code (Beta)](/tools/ai-assistant-vs-code), to markdown documentation that’s easy to copy into an LLM, or the [MCP Server](/tools/mcp-server) that enables natural-language interactions with Docusign APIs, these tools are designed to reduce friction and speed up development. Together, they help developers get answers faster, explore capabilities more easily, and work with Docusign using AI in ways that fit naturally into existing workflows. ## The Docusign Developer AI Assistant for VS Code The [Docusign Developer AI Assistant for VS Code (Beta)](/tools/ai-assistant-vs-code) is a Visual Studio Code extension that puts answers and examples right where you write code. By tagging @docusign in a Copilot Chat, you can ask about available APIs, walk through authentication flows, or get code snippets tailored to your project. The extension is designed to reduce the time you spend searching across documentation or switching contexts between your browser and editor. Beyond convenience, the assistant ensures that the information you receive is accurate and aligned with official Docusign developer resources. It can also help you generate access tokens and test sample calls inside your local environment. This integration enables you to build and validate solutions without leaving VS Code, keeping your workflow focused and uninterrupted. [Learn more about the Docusign Developer AI Assistant for VS Code →](/tools/ai-assistant-vs-code) ![A screenshot showing the Copilot chat box](/_fern-files/_img/770b4aef68653e1a3ef330a3be18d3964ea5e52bc1ca7427b4c82862eb77250e.webp) ## MCP Server The Docusign MCP Server gives developers a way to work with Docusign APIs through natural-language interactions using any AI assistant that supports the MCP standard. It allows you to explore Docusign capabilities, test API calls, and more without switching between multiple tools or references. By interpreting plain-language prompts and translating them into the correct Docusign actions, the MCP Server makes integrations more intuitive and supports faster experimentation and automation. [Learn more about the MCP Server →](/platform/mcp-server) ![A screenshot showing the Claude MCP server response to a prompt](/_fern-files/_img/60781003d71c4de0286e2cd3f7775659fe6d4dc3e93010defdc7c94645669e84.webp) ## Markdown files and the role of LLM-optimized content Docusign documentation can now be viewed and copied in plain-text formats optimized for large language models. On supported pages, you’ll see two new options that surface the underlying markdown content: * **View as Markdown:** Opens the same page in a new browser tab with `.md` appended to the URL, displaying a clean, text-only version of the content. * **Copy for LLM:** Instantly copies the page’s plain-text content so you can paste it into the LLM of your choice. ![LLM and Markdown button screenshot](/_fern-files/_img/b4818890667197dd7b5d787877cedfc72dfe7da8ecab04fbfaf860863f042496.webp) Markdown is a better input source for LLMs than scraping or copying from a rendered HTML page because: * It avoids extra formatting tokens that can confuse an LLM. * Content hidden in tabs or expandable sections is included in the markdown version, so nothing is lost. * The structure and hierarchy of markdown headings are easy for models to parse. * Clean, structured formatting improves accuracy and retrieval, helping LLMs return more precise answers. The **Copy for LLM** button is simply a shortcut for grabbing the entire markdown output without opening the separate `.md` view. It gives you immediate access to the plain-text version of the page so you can paste it directly into an LLM with no extra steps. When used together, the **View as Markdown** and **Copy for LLM** options give developers a simple way to bring Docusign documentation into AI-driven development. Whether you open the markdown view or copy the plain-text version directly into a model, both approaches ensure that your AI tool works with the same trusted material available in the Developer Center and formatted for clear, reliable consumption. Currently, these options are available on [Use case](/use-cases) pages, with broader support coming soon. ## Discover more * Install the [Docusign Developer AI Assistant for VS Code (Beta)](/tools/ai-assistant-vs-code) and try asking it about a workflow you’re building. * Check out this technical blog on how to [Build no-code agreement agents with Docusign and Microsoft Copilot Studio](https://www.docusign.com/blog/developers/technical-deep-dive-build-no-code-agreement-agents).