Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Descripción del creador (original en inglés)
MCP server for video transcripts, screenshots, and OCR on YouTube and web videos.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"ocular-audio": {
"command": "npx",
"args": [
"-y",
"ocular-audio-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add ocular-audio -- npx -y ocular-audio-mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"ocular-audio": {
"command": "npx",
"args": [
"-y",
"ocular-audio-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"ocular-audio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ocular-audio-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub RayAKaan, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.1.2) llegó al registro hace 4 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Figma Context MCP, Claude Real Video, Figma MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
The Figma MCP server brings Figma design context directly into your AI workflow.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Universal local-first media intelligence for AI agents.
OcularAudio lets MCP-compatible AI systems watch, listen to, search, inspect, compare, and reason over media. It turns URLs, streams, and local media into reusable timestamped evidence: metadata, transcripts, frames, OCR, retrieval results, multimodal moments, and cross-video intelligence.
v1.3.1 · MIT
Research and lecture analysis · product demonstrations · competitor analysis · interviews · technical talks · UI walkthroughs · multi-video comparison · evidence-grounded AI investigation.
| Capability | User outcome |
|---|---|
| Universal sources | Analyze URLs, files and streams through one interface |
| Transcript evidence | Find exactly when something was said |
| Visual evidence | Inspect what was shown at a timestamp |
| OCR | Search text visible inside video frames |
| Hybrid retrieval | Combine speech and visual evidence |
| Multimodal moments | Understand speech and visuals together |
| Batch analysis | Investigate collections of videos |
| Cross-video comparison | Compare evidence across sources |
| Agentic workflows | Execute bounded evidence investigations |
| Capability modes | Auto-select or enforce Lite, Intelligence, and Deep execution budgets |
| Cache | Make repeated analysis faster |
| MCP prompts | Start common investigation workflows |
| MCP resources | Give hosts operational context |
| HTTP deployment | Run as a protected network service |
All source artifacts are normalized into one local manifest per source. Evidence records have stable content-derived IDs, modality labels, timestamp bounds, content hashes, provenance pointers, and metadata. Transcript search, timelines, moment inspection, and hybrid retrieval share the same canonical IDs; OCR and visual-frame records are indexed alongside transcript evidence. Manifests are written atomically, validated on read, deduplicated by ID, and refreshed from the existing transcript and visual caches without requiring a migration or a database. Clearing a source removes its transcript, canonical manifest, visual index, and frame artifacts together. Manifest metadata intentionally stores a bounded summary rather than the source URL or credentials.
Every request is resolved through one deterministic policy engine. Auto resolves to Lite, Intelligence, or Deep based on query intent, requested features, source count, media duration, and an optional time budget. The decision is returned as machine-readable metadata with explicit limits, disabled features, capability gaps, and adjustments.
| Mode | Evidence | Visual frames | Default sampling | Runtime ceiling | Sources | Behavior |
|---|---|---|---|---|---|---|
| Lite | 8 | 8 | 30 s | 45 s | 1 | Transcript/metadata first; OCR, multimodal and batch are disabled |
| Intelligence | 24 | 24 | 10 s | 180 s | 10 | Balanced retrieval, visual/OCR and multimodal analysis |
| Deep | 64 | 64 | 3 s | 600 s | 32 | Expanded evidence and multi-step investigation |
| Auto | Policy-selected | Policy-selected | Policy-selected | Policy-selected | Policy-selected | Resolves to one of the three execution modes |
Modes enforce evidence caps, frame limits, source limits, retry counts, concurrency, sampling intervals, and runtime ceilings. Missing OpenCV, FFmpeg, or Tesseract is reported as a capability gap; optional unavailable features are disabled rather than represented as successful. Explicit source-limit violations fail with a clear error instead of silently dropping sources. Source coverage remains shared across modes.
The CLI's existing --mode flag now reaches the Python runtime. Use --budget-seconds to impose a caller-specified runtime ceiling (0.001-900 seconds). MCP planning, agentic execution, hybrid search, visual indexing, multimodal analysis, and batch analysis expose the same decision contract. Use --mode deep for comprehensive evidence or --mode lite for a fast overview.
Release status: this repository contains source version 1.3.1, which is not yet published to npm. The published package remains 1.2.1, so the npx examples below install 1.2.1 until 1.3.1 is separately published. To test the current checkout, clone the repository, install the Python dependencies from requirements.txt, then run node bin/cli.js from the checkout.
npx -y ocular-audio-mcp
Local MCP hosts can launch the same command. Example:
{ "mcpServers": { "ocular-audio": { "command": "npx", "args": ["-y", "ocular-audio-mcp"] } } }
Claude Code:
claude mcp add ocular-audio -- npx -y ocular-audio-mcp
Codex CLI:
codex mcp add ocular-audio -- npx -y ocular-audio-mcp
npx ocular-audio "https://www.youtube.com/watch?v=dQw4w9WgXcQ" npx ocular-audio --check npx ocular-audio --json "URL" npx ocular-audio --visual-index --ocr "URL" npx ocular-audio --multimodal-search "pricing" "URL" npx ocular-audio --plan "Find the pricing discussion and inspect its visual evidence" npx ocular-audio --agentic "Find every pricing discussion and inspect the relevant slides"
MCP host / agent | MCP tools + prompts + resources | Universal source resolver | Evidence: metadata + transcript + timestamps + chapters / | \ visual OCR retrieval \ | / multimodal moments | batch intelligence | agentic execution | operations / audit / readiness
Media/evidence: get_ocular_audio_transcript, get_ocular_audio_video_context, search_ocular_audio_video, get_ocular_audio_video_timeline, inspect_ocular_audio_moment, query_ocular_audio_evidence, get_ocular_audio_metadata, get_ocular_audio_chapters, inspect_ocular_audio_source, get_ocular_audio_capabilities.
Visual/OCR: get_ocular_audio_video_screenshots, index_ocular_audio_video_visuals, search_ocular_audio_visuals, get_ocular_audio_video_frame, get_ocular_audio_video_frame_burst, crop_ocular_audio_video_frame.
Retrieval/multimodal: search_ocular_audio_hybrid, analyze_ocular_audio_multimodal, inspect_ocular_audio_multimodal_moment, search_ocular_audio_cache.
Batch: analyze_ocular_audio_batch, search_ocular_audio_videos, compare_ocular_audio_videos, get_ocular_audio_batch, list_ocular_audio_batches.
Agentic/operations: plan_ocular_audio_analysis, run_ocular_audio_analysis, get_ocular_audio_health, get_ocular_audio_audit, get_ocular_audio_contract, get_ocular_audio_identity.
Cache: list_ocular_audio_cache, clear_ocular_audio_cache.
stdio is the default local MCP transport and requires no HTTP authentication.
npx ocular-audio --transport streamable-http --host 127.0.0.1 --port 8000
The MCP endpoint is /mcp. For network exposure, configure authentication, real issuer/resource URLs, allowed hosts and allowed origins. Do not expose an unauthenticated instance to an untrusted network.
cp .env.example .env docker compose -f docker/docker-compose.yml up --build -d
The supplied deployment uses Python 3.11, FFmpeg, a persistent cache volume, a read-only container filesystem, dropped capabilities, no-new-privileges, restart policy and a healthcheck.
For internet-facing deployments, use TLS and an organization identity provider. The built-in static bearer verifier is intended for controlled deployments and can be replaced by JWT validation or RFC 7662 introspection.
The NPM package does not hide native Python/system prerequisites; OcularAudio is a local media-processing server rather than a hosted API.
Operator-supplied cookies.txt can be used for sources that require an authenticated browser session. Never commit cookies, access tokens or credentials.
npm install npm run check npm pack
This creates ocular-audio-mcp-1.3.1.tgz. Inspect it before publishing:
npm publish ocular-audio-mcp-1.3.1.tgz --access public
See RELEASE_v1.3.1.md. A manual GitHub Actions workflow can also build and upload the exact tarball and SHA-256 checksum as artifacts.
python -m unittest discover -s tests -v node --check bin/cli.js npm run check
CI additionally validates the MCP SDK surface, tool/resource/prompt registration, Streamable HTTP authorization behavior, compilation, CLI syntax and package m
Solo se muestra el principio; lee el resto en el repo