Ultralayer API
MCP Server (V0)
POST
https://api.ultralayer.ai
/v0/mcp
This endpoint serves the remote Model Context Protocol (MCP) server for Ultralayer V0.
Tools
- semantic_search: Perform a semantic search over indexed document chunks using a query string. Returns the top-k most relevant chunks by cosine similarity with optional filters for timestamp, source metadata, entity type, utility score, and sentiment score.
- semantic_search_multi: Perform semantic search across multiple queries in one request. Results are flattened, deduplicated, and returned in a single ranked list. Benefits (vs just making multiple semantic_search calls): 1. simpler client implementation, 2. smarter strategies for deduplication and ranking, 3. cheaper as duplicates arent charged.
- identify_stakeholders: Identify key stakeholders relevant to a given query, with optional context and instructions to guide the identification process.
- search_developments: Search for developments semantically (or not). Various filters available: timestamp, development type, stakeholder impact, and more.
- retrieve_development: Retrieve a specific development by its ID.
- retrieve_event_developments: Retrieve all developments associated with a known event_id. Filters for timestamp and occurrence are available. Track and understand the full event lifecycle through its developments.
- search_events: Search for events semantically (or not). Various filters available: timestamp, occurrence, event type and more.
- create_alert: Create an alert that periodically polls an endpoint and delivers new results to your configured receivers (webhook, email, and/or telegram).
- get_alerts: Retrieve all alerts for the authenticated user, including recent attempt and delivery history.
- deactivate_alert: Deactivate an alert by setting its status to 'paused'.
- activate_alert: Activate an alert by setting its status to 'active'.
- delete_alert: Permanently delete an alert from the database.
- execute_alert: Execute an alert immediately to test it. Runs the exact same path as scheduled execution, including history and dedup.
MCP Server (V0) › Responses
200
MCP Protocol Stream
No data returned