DropMCP
Give AI the tools it is allowed to use.
What it is
DropMCP makes selected capabilities discoverable and usable by compatible AI clients and providers while retaining the checks of the system that owns each operation.
How it works
Select the surface
Choose the tools, resources and prompts that a defined participant can discover.
Route the request
Make selected capabilities available through supported AI connections.
Preserve ownership
Keep each capability subject to the owning institution’s permissions.
How it connects
- DropAgents
- Supplies approved tools to specialized AI workers.
- DropAPI
- Routes to configured operations when that integration is used.
- TAG
- Keeps runtime control attached to governed calls.
Why it matters
Tool discovery does not become blanket authority. The useful AI interface and the application’s operating boundary stay connected.
An AI worker prepares a service summary.
It can retrieve the approved manual and request a permitted status check. It cannot infer that those tools also authorize changing the device’s configuration.
DropMCP is a supported integration route, not a mandatory hop for every workflow or system call.