TL;DR

[Benchmark] DeepWiki Repo Q&A is a devops workflow that chains DeepWiki to automate a common task. Internal benchmark recipe — DeepWiki single-tool repo Q&A, no API key needed. Once configured, it saves n/a and runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.

🧠

DevOpsBeginner

[Benchmark] DeepWiki Repo Q&A

Internal benchmark recipe — DeepWiki single-tool repo Q&A, no API key needed.

10-30s per run1 MCP requiredSaves n/a

How it works

🧠DeepWiki

Automated

1ask_question(repo, question)

Hostable — runs in your browser1/1 MCPs hosted

Run with MCPizy

New

Execute this recipe in your browser — no local install, no Claude Code. Streams results live.

Whitelisted MCPs: perplexity, notion, anthropic, openai, tavily, firecrawl, coingecko, stripe, slack, github, gitlab, linear, resend, sendgrid, elevenlabs, shopify, sentry, posthog, supabase-mcp, context7, deepwiki~4k tokens · ~$0.012 est.

Why this combo?

Benchmark only — single-MCP, remote, no key.

Without this workflow

N/A

With MCPizy

N/A

Business value

Concrete ROI — not marketing fluff.

Time saved

n/a

Benchmark only

Workflow steps

1
ask_question(repo, question)

Use cases

APC benchmark: DeepWiki Q&A

MCPs required

🧠

DeepWiki

DeepWiki MCP Server

View

Agent prompt (copy into Claude Code)

This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.

You are a repo-Q&A agent. Given a GitHub repo (owner/repo) and a question:
1. Call deepwiki.ask_question with repoName=<owner/repo> and question=<question>
2. Respond with a 3-sentence answer grounded in the returned content.
Do not call any other tool.

Trigger & credentials

How this workflow fires and what env vars you need.

.env.example

ManualTrigger

🧠DeepWiki· 0 var

One-command deploy

Install everything — MCPs, prompt, env template — in a single call.

$ mcpizy recipe install bench-deepwiki-repo-1

✓ Installs all 1 MCP server
✓ Writes prompt to ~/.mcpizy/prompts/bench-deepwiki-repo-1.md
✓ Generates .env.example in current directory
✓ Ready to paste into Claude Code

Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.

Quick install (MCPs only)

10-30s per run

$ n/a

More DevOps recipes

🟢🐙

Auto DB Migrations on Push

Every push to main triggers a Supabase migration automatically. Schema diffs are committed and applied with zero manual steps.

🐙▲

Preview Deploy on Every PR

Open a PR and a Vercel preview URL appears as a comment within minutes. Branches are cleaned up automatically when PRs close.

🐳☁️

Container Deployment to AWS

Build, tag, push to ECR and deploy to ECS in one automated pipeline triggered by a git tag or manual dispatch.

⚡🐙

Branch-per-PR Databases

Each PR gets its own Neon database branch for isolated testing. Branch is deleted automatically when the PR closes.

Frequently asked questions

What is this workflow?

[Benchmark] DeepWiki Repo Q&A is a devops automation that uses DeepWiki together via the Model Context Protocol. Internal benchmark recipe — DeepWiki single-tool repo Q&A, no API key needed.

How long does setup take?

Setup takes around 10-30s per run. You install the required MCP servers with `n/a`, connect your accounts, and the workflow is ready to run.

How much time does this workflow save?

Once running, this workflow saves n/a. The concrete business value: Benchmark only.

Which MCP servers do I need for this?

You need 1 MCP server: DeepWiki (mcpizy install deepwiki). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.

Does this work with Claude Code, Cursor, and Windsurf?

Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.

Start building this workflow

Install the required MCPs from the marketplace and automate this in 10-30s per run.

$ n/a

🧠Install DeepWiki

Free to install. Connect your accounts and this workflow runs itself.

You are a repo-Q&A agent. Given a GitHub repo (owner/repo) and a question: 1. Call deepwiki.ask_question with repoName=<owner/repo> and question=<question> 2. Respond with a 3-sentence answer grounded in the returned content. Do not call any other tool.

$ mcpizy recipe install bench-deepwiki-repo-1 ✓ Installs all 1 MCP server ✓ Writes prompt to ~/.mcpizy/prompts/bench-deepwiki-repo-1.md ✓ Generates .env.example in current directory ✓ Ready to paste into Claude Code