NetDocuments

Connect NetDocuments to BotDojo through its hosted MCP server. BotDojo discovers the tools available to the authorizing NetDocuments user and lets you choose which tools your agents can use.

Before you start

Ask your NetDocuments administrator to confirm:

• Your organization has the ndConnect Enterprise entitlement needed for MCP. NetDocuments describes this as an ndMAX Enterprise capability.
• MCP access is enabled for your organization in Security Center.
• BotDojo is permitted to connect under your organization's NetDocuments approved-client policy. A catalog entry in BotDojo does not establish NetDocuments partner approval.
• You have the correct regional MCP endpoint and a test user with access to the intended documents.

Use an HTTPS BotDojo deployment for OAuth. You also need permission to add a Connection in the intended BotDojo project.

Add the connection

1. Open the project's Connections page and select New Connection.
2. Search for NetDocuments and select it.
3. Review NetDocuments MCP Server URL. The default is the US endpoint: https://web-api.us.netdocuments.app/connect/mcp. For another region, enter the MCP URL supplied by your NetDocuments administrator. Do not substitute a document link or sign-in page.
4. Leave OAuth scope, token authentication method, and endpoint overrides unset to use automatic discovery.
5. Select Connect and sign in to NetDocuments with the user whose documents the connection should access. Review the consent request.
6. After returning to BotDojo, review the discovered tools and enable only the search and retrieval tools needed for your workflow. Apply the appropriate BotDojo Connection access and approval settings.

BotDojo discovers the OAuth endpoints and registers its client during setup. You do not need to copy a client ID or secret for this connection mode. If your tenant requires a pre-registered client, obtain the approved configuration from NetDocuments and use BotDojo's Remote MCP Server connection with pre-registered OAuth instead.

Access and permissions

BotDojo uses the existing Remote MCP OAuth discovery flow. NetDocuments advertises read, organize, and edit scopes; this catalog entry does not enforce read-only OAuth authorization. Review the vendor consent permissions and enable only the search and retrieval tools needed in BotDojo. Tool selection in BotDojo does not reduce the permissions of the vendor-issued token.

NetDocuments enforces the authorizing user's document permissions. A shared BotDojo Connection uses that user's authorization; it does not automatically switch to each BotDojo user's NetDocuments identity. Grant BotDojo access to the shared Connection accordingly.

Verify the connection

1. Confirm the connection completes and a tool list appears. Expected: search and retrieval tools can be selected without an authentication error.
2. Ask an agent to find a known test document and summarize a short passage. Expected: the correct document and content are returned.
3. Try a document the authorizing NetDocuments user cannot access. Expected: its content is not returned.
4. Try an unrelated query. Expected: a valid empty result can be distinguished from a connection failure.
5. Repeat a lookup after a token refresh, then reconnect once. Expected: both paths work without manually pasting credentials.

Run these checks with an administrator-approved test account before using the connection in a client demo.

Troubleshooting

When contacting BotDojo support, provide the connection ID, approximate time, and attempted action. Do not include passwords, tokens, or document contents.

References

• NetDocuments ndConnect and MCP overview
• US MCP protected-resource metadata
• US OAuth discovery metadata
• BotDojo Connection configuration