Remote MCP server

Connect directly to Ayneye's live MCP endpoint.

The Public Beta MCP server is available remotely over HTTPS and uses tenant-scoped Bearer authentication.

Resources Server design Safety Quickstart Policies Agent tools World-State docs

Public Beta MCP

Connect your AI agent to Ayneye

Create a Public Beta workspace, generate a scoped API key in the dashboard, and connect to the live remote MCP endpoint.

https://api.ayneye.com/mcp

Connection contract

Item	Value
Endpoint	https://api.ayneye.com/mcp
Transport	Streamable HTTP / JSON-RPC over HTTPS
Authentication	Bearer Ayneye API key
Tenant scope	Every operation remains scoped to the authenticated workspace
Processing maximum	60 seconds per processing session

Tool discovery

A compatible MCP client discovers the live tool schema from the server. The current Public Beta contract exposes exactly eight tools.

ayneye.create_video
ayneye.upload_video
ayneye.get_video_status
ayneye.get_video_artifacts
ayneye.ask_video
ayneye.start_live
ayneye.get_live_state
ayneye.stop_live

Server boundaries

Compatible MCP clients discover the current Public Beta tool schemas from the live server.
Runtime results remain provider-safe.
Raw video and raw frames are not sent to the language model.
Ask remains evidence-gated.
Unsupported visual claims must not be invented.

The purpose of this page is to make the MCP boundary concrete for builders, buyers, and reviewers. A useful MCP integration is not a promise that an agent can watch everything and decide everything. It is a disciplined interface over already-materialized evidence. Each tool call should be tenant-scoped, read-only by default, evidence-aware, cost-aware, and auditable. If the request asks for identity, intent, physical access, emergency response, employment action, or destructive change, the tool returns a review-required state instead of pretending that a video artifact is a final decision. This keeps the product useful for developers while making it credible for security, legal, and operations teams.

Camera bootstrap boundary

Ayneye's live MCP contract does not control local operating-system camera devices. A developer-side capture process pushes camera video through the public HTTPS camera-ingest contract and receives a video_id. MCP begins at that video boundary.

Layer	Public responsibility	Not its responsibility
Local device bridge	Discover/capture the webcam and publish MPEG-TS over HTTPS.	Evidence reasoning, QCE, or agent claims.
Camera bootstrap	Create the tenant-scoped ingest session and return video_id.	Adding a ninth MCP tool.
MCP	start_live, get_live_state, ask_video, stop_live over video_id.	Operating FFmpeg or reading arbitrary local device paths.
Ayneye intelligence	World-State, evidence, answerability and persistent Ask.	Sending raw unrestricted camera control to the agent.

Public HTTPS camera-ingest contract

For a webcam attached to the developer machine, create an Ayneye camera-ingest session before starting MCP live execution. Camera bootstrap is a public HTTPS ingest operation outside the MCP tool set; the MCP contract remains exactly eight tools.

1. Create a camera-ingest session

POST https://api.ayneye.com/v1/camera-ingest/sessions
Authorization: Bearer $AYNEYE_API_KEY
Content-Type: application/json

{
  "title": "Local webcam",
  "capture_seconds": 60
}

The response provides a tenant-scoped session_id, video_id, HTTPS ingest_url, short-lived publish_token, and expiry information.

2. Publish the camera

Protocol: MPEG-TS over HTTPS POST
Target: <ingest_url>

Required HTTP Content-Type:
video/mp2t

Required publish header:
X-Ayneye-Ingest-Token: <publish_token>

FFmpeg HTTP output must explicitly send:
-content_type video/mp2t

3. Check readiness

GET https://api.ayneye.com/v1/camera-ingest/sessions/{session_id}
Authorization: Bearer $AYNEYE_API_KEY

Wait until the camera-ingest session reports ready=true. Then use its video_id with the existing MCP live tools.

video_id
→ ayneye.start_live
→ ayneye.get_live_state
→ ayneye.ask_video
→ ayneye.stop_live
→ ayneye.ask_video again

Authorized RTSP and HLS URLs remain supported when a camera is already network reachable. They are not required for Ayneye's first-party local-camera HTTPS bootstrap.