Your media library,
in your agent's hands.
Point Claude Desktop, Claude Code, Cursor, or any MCP-capable Pro client at MetaTana and your agent can browse, query, dedupe, organize, and clean up — using the same REST surface the app uses, with the same auth as your account.
{
"mcpServers": {
"metatana": {
"command": "npm",
"args": ["run", "mcp:stdio"],
"cwd": "/path/to/metatana/app",
"env": {
"METATANA_MCP_BASE_URL": "http://127.0.0.1:3000"
}
}
}
}The open standard from Anthropic for connecting AI agents to local tools and data.
Model Context Protocol (MCP) lets a Pro AI client like Claude Desktop, Claude Code, or Cursor connect to local services and use their tools — read your library, run a scan, apply a metadata patch — all under your control.
MetaTana ships its own MCP server for Pro. The bridge verifies a signed-in Pro account before exposing any tools, then forwards your hosted account session to the app so existing route checks decide what each request can do.
Small surface. Full coverage.
Three clients. Same five-line config.
{
"mcpServers": {
"metatana": {
"command": "npm",
"args": ["run", "mcp:stdio"],
"cwd": "/path/to/metatana/app",
"env": {
"METATANA_MCP_BASE_URL": "http://127.0.0.1:3000"
}
}
}
}claude mcp add metatana \ --cwd /path/to/metatana/app \ --env METATANA_MCP_BASE_URL=http://127.0.0.1:3000 \ -- npm run mcp:stdio
{
"name": "metatana",
"command": "npm",
"args": ["run", "mcp:stdio"],
"cwd": "/path/to/metatana/app",
"env": {
"METATANA_MCP_BASE_URL": "http://127.0.0.1:3000"
}
}Pro at startup, then the app's existing route checks decide.
The MCP stdio bridge verifies a signed-in Pro hosted account before exposing any tools. If the account is Free or unverifiable, the bridge exits at startup and the client sees no tools.
After that startup gate, the bridge forwards the hosted session to the app and the app's existing route checks decide whether each request can run. Free routes pass through; Pro routes return 402 when the entitlement is missing and 503 when hosted verification is unreachable.
| Status | Meaning | Agent behavior |
|---|---|---|
| Startup failure | The MCP process could not verify a signed-in Pro account. | Stop and ask the user to sign in with Pro or configure the hosted Pro session securely. |
| 200 | The route accepted the request. | Continue to operation or readback verification. |
| 401 | Local API auth or hosted session is missing or invalid. | Stop and ask the user to sign in or configure credentials. |
| 402 | The verified account lacks the route entitlement. | Do not retry until the account or entitlement changes. |
| 503 | Hosted entitlement verification is temporarily unavailable. | Retry later or ask the user to check hosted connectivity. |
Three real things you can ask your agent to do.
Argon 9 — Keep the 4K HDR (38.4 GB). The 1080p copy is missing Atmos and HDR metadata. Frees 8.2 GB.
Vesper Line— Keep both. Director's cut adds 23 min and is the canonical version.
Harbinger — Two identical 4K copies. Already resolved via AI.
NFO sidecars — 247/247 complete.
Artwork coverage — 98.4%.
Unmatched titles — 2 files need review.
Broken hardlinks — 0.
Want me to triage the 2 unmatched files?
Ready to hand your library to your agent?
MetaTana ships a Pro MCP server with every Pro account. Includes monthly AI Vision credits so your agent can second-pass hard files without a per-call charge.