Declare your app's MCP tools
dropyour_app_toolsMake YOUR graduated app callable by a third party's agent, as an MCP server at https://.dropyour.site/mcp — live as soon as ONE tool is declared; no tool declared = no /mcp at all (404). action='declarer': declare ONE tool — name (lowercase, no 'dropyour_' prefix: that would impersonate the platform), description (≤500 bytes), inputSchema (JSON Schema, ≤4KB), and the APP ROUTE the tool call POSTs to. The tool grants NOTHING beyond the route: your app's own guards apply unchanged, like a link (ADR-0264). action='retirer': close that surface — asks nothing, revoking is never harder than granting. action='lister': see what is declared. 16 tools max. Declared, never derived from your code: pushing new code never opens a surface silently. Note: the app-server transport builds on the 2026-07-28 MCP revision via a beta SDK — named here so you choose with open eyes.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| route | No | Absolute app path the tool call POSTs to, e.g. /api/commande. | |
| action | Yes | ||
| dropId | Yes | ||
| description | No | ||
| inputSchema | No | JSON Schema of the tool input, as a JSON string. | |
| managementToken | No |