Seevora MCP

Local stdio MCP server for Seevora.

This package does not run Seevora's evaluation engine locally. It acts as a local MCP bridge to the deployed Seevora agent API.

Tools

• preview_local_homepage_snapshot
• run_local_homepage_evaluation
• run_parallel_evaluation
• get_evaluation_status
• get_report
• list_agent_runs

Required environment variables

SEEVORA_API_BASE_URL=https://your-seevora-api-domain
SEEVORA_AGENT_API_TOKEN=your_agent_api_token
SEEVORA_AGENT_USER_ID=your_user_id
SEEVORA_AGENT_WORKSPACE_ID=your_workspace_id

The recommended source for these values is the website MCP connect page after you sign in with Google. The MCP server still consumes env vars locally, but the credential bundle can now come from the website instead of a shared prototype token.

Optional:

SEEVORA_AGENT_HOST=cursor

Run locally

From the repo root:

npm run mcp:start

Or invoke the package bin directly from the repo checkout:

node packages/seevora-mcp/bin/seevora-mcp.js

Package shape

This package is now wired with a bin entrypoint so it can be published as an installable CLI instead of requiring users to reference src/index.ts directly.

Recommended end-user command after publish:

npx -y seevora-mcp

Notes

• The MCP server communicates over stdio.
• It expects the Seevora API to expose the agent endpoints under /api/agent/evaluations.
• run_local_homepage_evaluation is the primary workflow for local or unpublished homepages. It collects the homepage entrypoint, local imports, and nearby app metadata files, then sends that snapshot to the Seevora backend.
• run_parallel_evaluation remains available for public URL scans.
• It is intended to point at a deployed Seevora backend or a locally running app.

Recommended workflow

For local homepage reviews:

1. Start the MCP server.
2. Call preview_local_homepage_snapshot to confirm the detected entrypoint and included files.
3. Call run_local_homepage_evaluation with an optional entrypoint like app/page.tsx.
4. Poll get_evaluation_status.
5. Fetch the final report with get_report.

Use run_parallel_evaluation only when the page is already publicly reachable.

For website-backed setup:

1. Sign in on the Seevora website.
2. Open /connect-mcp.
3. Generate MCP credentials.
4. Put those values into your local MCP env or Cursor MCP config.

Troubleshooting

• If autodetect misses the homepage, pass entrypoint explicitly, for example app/page.tsx, src/app/page.tsx, or pages/index.tsx.
• Check snapshot.includedFiles in the preview or run result to see exactly which files were captured.
• If your homepage relies on unusual aliases or generated wrappers, point the tool at the nearest real homepage source file.