[ Docs ](https://sendnda.com/docs) [ Agents and the API ](https://sendnda.com/docs/agents) Connect over MCP ================ Add Send NDA to Claude or any MCP client, and sign in with your email address. 05 Agents and the API ------------------ Article 1 of 3 Send NDA is an MCP server. Connect it to Claude or another MCP client once, and your assistant can do what the NDA's page does, on either side: send an NDA and change it, check the ones sent to you, fill in your details, and sign when you tell it to. It acts as you: the NDAs it sends come from your account. The address ----------- The server answers at one URL, over streamable HTTP: ``` https://sendnda.com/mcp ``` It needs a signed-in account. There are two ways in: OAuth, which is what connectors in Claude and ChatGPT use, and an [API token](https://sendnda.com/docs/agents/api-tokens) for a client that doesn't do OAuth. Connect Claude -------------- In Claude, add a custom connector and paste the address above. In Claude Code, run: ``` claude mcp add --transport http send-nda https://sendnda.com/mcp ``` Your client registers itself with Send NDA and sends you to sign in. Signing in works as it does on the site: type your email address and open the link we send you, or use a passkey. There's no password. An address we haven't seen before gets an account on the spot. Then you see a consent screen that names the client asking for access and the host it receives that access at. Approve it and the client gets a token with one scope, `mcp:use`. That scope only opens the MCP server. Other clients ------------- Send NDA publishes its OAuth details where MCP clients look for them, at `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`, and accepts dynamic client registration. A client may only register a redirect address on `claude.ai`, `claude.com`, `chatgpt.com` or `localhost`. The last one is there for the MCP inspector. Any other client can use an API token instead. What your assistant can see --------------------------- Every tool is scoped to your account. It sees the NDAs created on your account, the ones sent from your verified email address through the public site, and the ones sent to your verified email address. Nobody else's. The nine tools are `list-ndas`, `get-nda`, `create-nda`, `amend-nda`, `set-recipient-details`, `sign-nda`, `resend-nda`, `delete-nda` and `read-docs`. [The tools](https://sendnda.com/docs/agents/the-tools) covers what each one takes and returns. Two things to know up front: `create-nda` sends straight away, with no draft step, so a well-behaved assistant confirms the details with you before it calls it. And `sign-nda` signs for you, so it shows you the agreement first and signs only when you say so. The server tells it both. Limits ------ The server allows 120 requests per minute per account, and one IP address can register ten clients an hour. We note when your account last used the MCP server, at most once a minute. We never receive your conversation with the assistant, only the tool calls it makes. Disconnect an app ----------------- The **Agents** page lists every app you connected under **Connected**, with when you connected it and the host it receives its access at. Choose **Disconnect** and confirm, and it loses access straight away: its access and refresh tokens are revoked, so it cannot renew them. To use it again, connect it again. Checked against the code on 25 September 2026. [ The tools ](https://sendnda.com/docs/agents/the-tools)