AI agents
Connect an AI agent
Set up Claude Code, claude.ai, ChatGPT, Cursor or any MCP client with undocsend, and what the approval screen asks.
Before you start
- You need to be an owner or admin of the workspace you want to connect.
- AI agents must be allowed for that workspace. They are by default. Check Settings → General if the workspace doesn’t show up when you connect.
- Every app uses the same server URL:
https://mcp.undocsend.com/mcpEach app then opens undocsend in your browser so you can approve the connection. That screen is the same for every app; see the approval screen below.
Claude Code
- Add undocsend as a server:
claude mcp add --transport http undocsend https://mcp.undocsend.com/mcp- Start Claude Code and run
/mcp. Choose undocsend and follow the prompt to sign in. - Approve the connection in your browser, then go back to Claude Code.
claude.ai
- In claude.ai, open your settings and find Connectors.
- Add a custom connector. Name it “undocsend” and paste the server URL.
- Choose Connect, and approve the connection in the window that opens.
Whether you can add custom connectors depends on your Claude plan, and on a team plan, on what your Claude admin allows.
ChatGPT
- In ChatGPT’s settings, find where connectors (apps) are managed.
- Add a custom connector with the server URL, and choose OAuth if it asks how to sign in.
- Approve the connection in the window that opens.
Custom connectors in ChatGPT depend on your plan and settings, and the menu names change from time to time. If you can’t find the option, check ChatGPT’s own help pages for “custom connectors”.
Cursor
- Open Cursor’s MCP settings, or edit
~/.cursor/mcp.json(all projects) or.cursor/mcp.json(one project). - Add undocsend:
{
"mcpServers": {
"undocsend": {
"url": "https://mcp.undocsend.com/mcp"
}
}
}- Cursor shows that undocsend needs sign-in. Start it, and approve the connection in your browser.
Any MCP client
For developers and tools not listed above. The server follows the MCP authorization spec.
- Endpoint
https://mcp.undocsend.com/mcp- Transport
- Streamable HTTP (GET, POST and DELETE on the endpoint).
- Auth
- OAuth 2.1 authorization code flow with PKCE (
S256only). The access token goes in theAuthorization: Bearerheader; query-string tokens are not accepted. - Discovery
https://mcp.undocsend.com/.well-known/oauth-protected-resource/mcpandhttps://mcp.undocsend.com/.well-known/oauth-authorization-server. A 401 from the endpoint points to the first.- Client registration
- Dynamic client registration at
/oauth/register, public clients only (token_endpoint_auth_method: none), 1 to 10 redirect URIs. Client ID metadata documents (an https URL asclient_id) are also accepted. - Redirect URIs
- Any
httpsURI;httponly onlocalhost,127.0.0.1or[::1](any port). No fragments. Matched exactly, except the loopback port. - Scopes
read,build,share. Unknown scopes are ignored; if none is recognised, the request defaults toread build. The person approving makes the final choice.- Resource
- If you send the
resourceparameter, it must behttps://mcp.undocsend.com/mcp. - Tokens
- Access tokens last 1 hour, refresh tokens 30 days. Every refresh returns a new pair; reusing an old refresh token disconnects the whole connection.
- Step-up
- Calling a
sharetool without that scope returns HTTP 403insufficient_scope, so the client can ask the person to approve again with Share ticked. - Revocation
/oauth/revoke(RFC 7009).
The approval screen
When an app connects, undocsend opens a page titled “Allow app name to access undocsend?”. Here is what it asks.
Where access is sent
A box says “Access will be sent to” and names the place your approval goes back to. Known apps (claude.ai, chatgpt.com, cursor.com, the Cursor desktop app, and apps on your own computer) are marked Verified.
Anything else shows a red Unverified app warning. That doesn’t always mean something is wrong: many legitimate tools are unverified. Only continue if you started this connection yourself, from your own AI tool, just now. If you didn’t, click Cancel.
Which workspace
Choose the workspace to connect. The list only shows workspaces where you are an owner or admin and AI agents are allowed. Each connection is for one workspace. To use two workspaces, connect twice.
If the list is empty you’ll see “No workspace to connect”. Ask an owner to connect, to make you an admin, or to allow AI agents in Settings → General.
What the agent may do
- Read
- See rooms, documents and their text, share links, visitor activity and the audit log. On by default.
- Build
- Create and organise rooms, folders and documents, run the setup wizard, and draft answers to investor questions. On by default.
- Share
- Create share links, invite investors (up to 50 a day), change who sees folders and files, and revoke investor access. Off unless you tick it.
If the app asked for Share, an amber note says so, but the box still starts unticked. You decide. More on each one in Permissions and approvals.
Good to know
- Approve in the same browser where the connection started. A request opened in another browser won’t work.
- The request is valid for 10 minutes. If it expires, start again from your app.
- If you use two-factor authentication, you’ll be asked for it before you can approve.
- Reconnecting the same app (for example to add Share) removes any extra permissions you gave it.
After you connect
Click Allow access. Your browser returns you to the app. Once it says you’re connected, you can close the tab. undocsend emails you a notice that the agent was connected.
The connection appears under Settings → Connected agents, where any owner or admin can see or disconnect it. See Manage agents and security.
Try it
Ask your assistant: “List my undocsend rooms and tell me which ones had visitors this week.”