Find and book a location sound recordist / production sound mixer in Dubai and the UAE.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Availability is not published. Returns how to ask for given dates.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http alexey-sound https://alexeysound.ae/agent.php
Availability is not published. Returns how to ask for given dates.
| Argument | Type | Description |
|---|
| dates | string |
{
"type": "object",
"properties": {
"dates": {
"type": "string"
}
}
}Everything about Alexey Sound, a production sound mixer / location sound recordist in Dubai: services, price (from AED 2,500/day), kit, FAQ, credits, reviews, contacts.
No arguments.
{
"type": "object",
"properties": {}
}Send a booking request to Alexey for the client. It is NOT a confirmation: Alexey replies to the client personally. Ask the client for every required field first.
| Argument | Type | Description |
|---|---|---|
| name* | string | Client name |
| dates* | string | Shooting dates (e.g. 2026-11-20, or 20–21 Nov 2026) |
| company | string | Company / production |
| contact* | string | Email or phone of the client |
| details | string | Anything else: hours, crew, cameras, budget |
| location* | string | City / venue |
| shoot_type* | string | Commercial, documentary, interview, corporate, podcast, film, TV… |
| people_on_camera | string | How many people speak on camera |
{
"type": "object",
"required": [
"name",
"contact",
"dates",
"location",
"shoot_type"
],
"properties": {
"name": {
"type": "string",
"description": "Client name"
},
"dates": {
"type": "string",
"description": "Shooting dates (e.g. 2026-11-20, or 20–21 Nov 2026)"
},
"company": {
"type": "string",
"description": "Company / production"
},
"contact": {
"type": "string",
"description": "Email or phone of the client"
},
"details": {
"type": "string",
"description": "Anything else: hours, crew, cameras, budget"
},
"location": {
"type": "string",
"description": "City / venue"
},
"shoot_type": {
"type": "string",
"description": "Commercial, documentary, interview, corporate, podcast, film, TV…"
},
"people_on_camera": {
"type": "string",
"description": "How many people speak on camera"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 10, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.