0 Fork 0

mirror of https://github.com/Dvorinka/Primora.git synced 2026-10-28 07:41:23 +00:00

Files

T

Tomas DvorakandDevin f9e7002048 fix(mcp): resolve pre-existing tsc drift in server.ts

zod v4 requires z.record(keySchema, valueSchema); the integration tool
passed a string literal where the generated client wants the enum.

Authored By: TDvorak <[email protected]>

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-09-24 18:49:03 +02:00

src

fix(mcp): resolve pre-existing tsc drift in server.ts

2026-09-24 18:49:03 +02:00

package.json

feat: phase 5 distribution — tauri shell, pwa, desktop release artifacts

2026-09-16 19:59:53 +02:00

README.md

feat: encrypted secrets vault across CLI, desktop, dashboard, and backend

2026-09-24 18:46:37 +02:00

tsconfig.json

feat: ship phase 1 surface area (v0.2.0)

2026-09-16 14:04:43 +02:00

README.md

@primora/mcp

Primora MCP stdio server - exposes the platform as primora_* tools to any MCP client (Claude Desktop, Cursor, etc.).

Build

npm run build --workspace @primora/mcp   # → dist/server.js

Configure

Point your MCP client at node dist/server.js. The server shares the CLI's config file - primora login once and both tools work. Env vars override: PRIMORA_BASE_URL, PRIMORA_API_KEY, PRIMORA_ORG, PRIMORA_PROJECT.

Tools

30+ primora_* tools covering organizations, projects, buckets, objects, collections, API keys, integrations, webhooks, scheduled jobs, telemetry, and audit: primora_whoami, primora_list_projects, primora_upload_object, primora_query_audit, primora_run_job, …

Secrets are agent-safe by design — values are never returned by any tool:

primora_vault_status / primora_vault_list — local-vault state and metadata (names/urls/notes only); requires primora vault unlock on the host.
primora_vault_exec — runs primora commands with a vault secret injected into the child's env; vault/secrets/inject/agent/login/use and keys:create are denied so no response can carry a credential.
primora_secrets_list / primora_secrets_set — project-vault metadata and write-only storage. No reveal or delete: agents consume secrets through secret://NAME references in job payloads, resolved server-side at delivery.