> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vumasign.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI tools

> Let an agent read these docs instead of guessing at the API.

Agents asked to integrate with an e-signature product invent endpoints — confidently, with
plausible names — and every one of those is a Not Found somebody finds by hand later. This site runs a
Model Context Protocol server so that an agent writing your integration can **search** these docs,
and read any page in full, including every page of the
[API reference](/api-reference/list-templates), instead.

```bash theme={null}
claude mcp add --transport http vumasign-docs https://docs.vumasign.com/mcp
```

Any client that speaks MCP over HTTP can use the same URL: `https://docs.vumasign.com/mcp`. It
needs no key.

**It reads documentation, and the only thing it can send is a report to our docs team** that a
page is wrong or unclear. It holds no credential and cannot send an envelope, read your account,
revoke a key or mint a signing URL — a signing URL is a bearer credential for a legal act, and a
model will put it in a transcript. For anything that touches real data, call the API with your own
key.

For a tool that reads plain text rather than MCP, the same pages are indexed at
`https://docs.vumasign.com/llms.txt`, and served in full at `https://docs.vumasign.com/llms-full.txt`.