Agent-native video API: create live video sessions, mint restricted app keys and verify recorded camera and mic media.
Scored across 11 tools
Each tool targets a distinct resource or action: project/key/token/session creation, account/project/session listing, manifest reading, guidance, and two clearly differentiated verification paths. The potential overlap between run_media_check and verify_session is explicitly resolved in the descriptions: one tests Synento's synthetic call path, the other verifies the app's published recording.
All tool names use consistent snake_case and follow a predictable verb_noun pattern (create_*, get_*, list_*, run_*, verify_*). There are no mixed conventions or vague standalone verbs.
The server exposes 11 tools, which is well within the appropriate range for an integration/session-management surface. Each tool appears to earn its place by covering a distinct operation in the project, key, token, session, and verification workflow.
Core workflows are covered: creating projects, minting server keys and connection tokens, creating and listing sessions, reading manifests, and verifying integrations. Minor lifecycle gaps exist, such as no explicit delete/end session or key/token revocation operations, but the main integration surface is usable.
Mint a short-lived connection token for one participant to join a session from a browser — for trying the integration locally. In production the app’s server mints these with its own key. (Requires scope mcp:write.)
Inputs: user_id (required), session_id (required), mode.
Create a project in the organisation. The new project is added to this connection, so the other tools can use it. (Requires scope projects:create.)
Inputs: name (required), environment, idempotency_key.
Mint a restricted server key (rk_live_…) for one project, for the app’s server-side environment. It can only create sessions, mint connection tokens and read manifests in that project. The secret is returned once: write it to a gitignored env file, never to browser code or a commit. (Requires scope keys:mint.)
Inputs: project_id (required), label.
Create a video session in a project. Returns its id; browsers join it with connection tokens. Subject to the plan’s limits, and fires the session.created webhook. (Requires scope mcp:write.)
Inputs: project_id (required), name, idempotency_key.
The organisation, the signed-in person, the projects this connection may use, plan usage and limits, and the scopes granted. (Requires scope mcp:read.)
Inputs: no named parameters.
Read a Synento guide. Available: index, getting-started, guides/mcp, concepts, api-reference, browser-support, guides/access-control, guides/cli, guides/json2video-clips, guides/recordings-replay, guides/sdk, guides/sessions, guides/webhooks, examples/cli-examples, examples/sdk-advanced, examples/sdk-basic, examples/web-quickstart. (Requires scope mcp:read.)
Inputs: path (required).
The raw session manifest: every participant and track that actually holds recorded media, with time bounds. A track is listed only once media reached it. (Requires scope mcp:read.)
Inputs: session_id (required).
The projects this connection may use. (Requires scope mcp:read.)
Inputs: no named parameters.
Recent sessions in a project, newest first. (Requires scope mcp:read.)
Inputs: project_id (required), limit.
Run a synthetic two-participant call (camera and microphone) through Synento’s real WebSocket endpoint into a new session in the project, then verify it from the recording. Proves the Synento side works for this project; it does not run or test the app’s code — use verify_session for that. Takes about five seconds. (Requires scope mcp:write.)
Inputs: project_id (required).
Prove an integration works: read the recording of a session the app published into, and check each expected participant actually carried media on each expected track. Returns whether each expected participant’s tracks hold media, plus, on failure, what is missing and what usually causes it. (Requires scope mcp:read.)
Inputs: session_id (required), kinds, user_ids, min_participants.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Add one secure layer between your agents and this server.