doora-mcp 0.2.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -9
- package/dist/index.js +9 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -48,15 +48,20 @@ error when you first try to resolve a handle.
|
|
|
48
48
|
|
|
49
49
|
## Tools
|
|
50
50
|
|
|
51
|
-
| Tool | What it does | Network |
|
|
52
|
-
|
|
53
|
-
| `resolve_handle` | Look up address for a `username@label` handle | ✓ |
|
|
54
|
-
| `
|
|
55
|
-
| `
|
|
56
|
-
| `
|
|
57
|
-
| `
|
|
58
|
-
|
|
59
|
-
|
|
51
|
+
| Tool | What it does | Network | Needs `DOORA_API_KEY` |
|
|
52
|
+
|---|---|---|---|
|
|
53
|
+
| `resolve_handle` | Look up address for a `username@label` handle | ✓ | yes |
|
|
54
|
+
| `start_handle_creation` | Mint a device-flow session so the user can create a new handle in their browser. Returns a `claim_url` to show them. | ✓ | **no** |
|
|
55
|
+
| `check_handle_status` | Poll the result of `start_handle_creation` until the user finishes. | ✓ | **no** |
|
|
56
|
+
| `encode_digipin` | lat/lng → 12-char DIGIPIN string | — | no |
|
|
57
|
+
| `decode_digipin` | DIGIPIN → lat/lng centroid | — | no |
|
|
58
|
+
| `list_demo_handles` | Curated list of test-key-resolvable handles | — | no |
|
|
59
|
+
| `validate_handle_shape` | Regex-check a handle without an API call | — | no |
|
|
60
|
+
|
|
61
|
+
The two anonymous tools (`start_handle_creation` + `check_handle_status`)
|
|
62
|
+
let an agent help a user without a doora account create one — they
|
|
63
|
+
sign in / sign up themselves in the browser; the agent only sees the
|
|
64
|
+
resulting handle string. Full flow + trust model:
|
|
60
65
|
**https://www.doora.to/docs/mcp**.
|
|
61
66
|
|
|
62
67
|
## Configuration
|
package/dist/index.js
CHANGED
|
@@ -49,7 +49,7 @@ import { DoraApiError, resolveHandle, startClaimSession, checkClaimSession, } fr
|
|
|
49
49
|
const HANDLE_PATTERN = /^([a-z0-9-]{3,24})@([a-z0-9-]{2,16})$/i;
|
|
50
50
|
const server = new McpServer({
|
|
51
51
|
name: 'doora',
|
|
52
|
-
version: '0.
|
|
52
|
+
version: '0.3.1',
|
|
53
53
|
}, {
|
|
54
54
|
capabilities: { tools: {} },
|
|
55
55
|
instructions: `doora exposes India-aware addresses behind memorable handles like \`praneeth@home\`. ` +
|
|
@@ -62,11 +62,14 @@ const server = new McpServer({
|
|
|
62
62
|
server.registerTool('resolve_handle', {
|
|
63
63
|
title: 'Resolve doora handle to address',
|
|
64
64
|
description: 'Look up the full delivery address for a doora handle. Returns coordinates, ' +
|
|
65
|
-
'DIGIPIN,
|
|
66
|
-
'
|
|
67
|
-
'
|
|
68
|
-
'
|
|
69
|
-
'
|
|
65
|
+
'DIGIPIN, the place_type (apartment / villa / independent_house / commercial / ' +
|
|
66
|
+
'other) so you can phrase the response with the right vocabulary (society + flat ' +
|
|
67
|
+
'for apartment, plot number for villa, suite for commercial, etc.), the building/' +
|
|
68
|
+
'floor/unit/notes fields the owner has shared, verification method, and an audit ' +
|
|
69
|
+
'id. Use this when the user mentions any string in `username@label` shape (e.g. ' +
|
|
70
|
+
'"praneeth@home", "demo@office") and wants the underlying address. Requires the ' +
|
|
71
|
+
'DOORA_API_KEY environment variable; test keys can only resolve handles owned by ' +
|
|
72
|
+
'the configured demo user — call list_demo_handles to see those.',
|
|
70
73
|
inputSchema: {
|
|
71
74
|
handle: z.string()
|
|
72
75
|
.describe('Doora handle in the form `username@label`. Case-insensitive; will be lowercased before lookup.'),
|