Skip to main content
Docusnap365 exposes your environment through the Model Context Protocol (MCP). Any MCP-capable AI tool you already use—Claude, ChatGPT, or another—can then work directly with your Docusnap365 data: query the inventory, have relationships explained, create assets. The same questions the built-in AI Assistant answers, your AI tool answers too—inside the AI tool you are already working in.

​
Connecting

You can connect Docusnap365 in two ways. Either way, you sign in with your Docusnap365 account—no key, no copying credentials.

​
Claude

Add the Docusnap · MCP-Server connector from Claude’s directory and sign in.
In Team and Enterprise organizations, an Owner first adds the connector for the organization. Each member then connects with their own account.

​
Other MCP-capable AI tools

The address is your Docusnap365 address with /mcp appended, for example https://docusnap365.com/mcp. The AI tool handles the sign-in.
Where you enter the address in your AI tool differs by provider. The provider’s own instructions apply.

​
Permissions

The AI tool acts with your own role: it reads and changes exactly what you yourself are allowed to in Docusnap365, no more. Every change is attributed to you.

​
Tools

Eight tools are available: Docusnap365 tells your AI tool for every tool whether it changes data. discover, list_schema, describe, query and get are marked read-only; update and delete are marked as tools that overwrite or remove existing data. create only adds new data. Anything an AI tool deletes goes to the Trash, just as when you delete it in Docusnap365, and can be restored there. Which fields a type carries is in the data model.
Before creating or changing a record, the AI tool presents the details to you for confirmation instead of carrying them out unasked.
If a tool rejects a call—say, because a required field is missing or an id is invalid—your AI tool gets a message it can use to correct and retry the call. For an unexpected error, it only learns that the call failed—repeat the question, or check the matter in Docusnap365 itself.
Scan jobs cannot be started through MCP. Scanning remains an action in Docusnap365 itself.

​
Quota

Every tool call counts as one request against your subscription’s quota, regardless of how much data the tool queries for it. MCP and the REST API consume the same quota. Establishing the connection and retrieving the tool list do not count. A call that the tool rejects, for example because a required field is missing, has already been counted. If your AI tool corrects the call and retries it, both calls count.
Once the quota is used up, Docusnap365 runs no further tool calls and no further REST API requests until the next period begins. Your AI tool receives a message stating when requests are possible again.
If the quota temporarily cannot be checked, Docusnap365 does not run the call either. Repeat the question later.

​
Limits

The AI tool knows only what is captured in Docusnap365. Your data leaves Docusnap365 toward the AI tool you use—that AI tool’s data protection terms apply for this path.
Responses may contain errors. Check figures you rely on in the corresponding list.
What the built-in Assistant can additionally do is at AI Assistant—Basics.