Model Context Protocol
Your coding agent should know why the idea might fail
Connect Claude Code, Cursor, Codex or any MCP client. Your agent can attack an idea before it writes a line of code, open the evidence behind any claim, and pull the build spec in its own format.
Why this matters more than it sounds
An agent handed an optimistic brief writes optimistic code. It widens the scope, builds the things on the “not yet” list, and never mentions the risk — because nothing in its context told it there was one.
Every response from these tools carries the verdict, the confidence, the scope exclusions and the kill criteria. The server even tells your agent, on connect, not to start building when the verdict is not “build candidate”.
The six tools
attack_ideacosts credits- Attack an idea the user brought you. Searches real complaints, payment signals and competitors, then returns build candidate, validate first, narrow the wedge, or kill it. Costs credits.
search_ideasfree- Search published opportunities by segment, difficulty and time to MVP. Returns verdicts and confidence, not just titles.
get_ideafree- The full evaluation of one idea: who feels the problem, who pays, the concierge version, what NOT to build, risks, and kill criteria.
get_evidencefree- The source records behind an idea — supporting, falsifying, payment evidence and what is missing. Every item links to the original post.
get_specfree- The build spec in your platform's exact format: CLAUDE.md, .cursor/rules, AGENTS.md, a Lovable knowledge base, a Bolt prompt under its word ceiling.
get_usagefree- Plan, remaining credits, recent attacks and generated specs. Call it before spending.
Setup
- 1
Create a token
Go to Settings → MCP access and create one. It is shown once — we store only a hash, so we cannot show it again.
- 2
Add the server to your client
Endpoint:
https://codekudo.com/api/mcpClaude Code
claude mcp add --transport http codekudo https://codekudo.com/api/mcp \ --header "Authorization: Bearer YOUR_TOKEN"
Cursor, Codex and other clients
Add this to your MCP config file:
{ "mcpServers": { "codekudo": { "type": "http", "url": "https://codekudo.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } - 3
Ask your agent to attack something
Try one of these:
- Attack my idea with CodeKudo: an AI website builder for hairdressers in Germany.
- Find CodeKudo ideas that are B2B, buildable in two weeks, and have payment evidence.
- Show me the evidence behind that verdict — I want to read the original posts.
- Pull the CodeKudo spec for that idea in Claude Code format and start on ticket one.
What the token can and cannot do
- Scoped to your account. It reads published ideas, your own attacks and your own specs. It cannot see another member's private work.
- Stored as a hash. We keep a SHA-256 digest, not the token. If our database leaked, the tokens in it could not be used.
- Revocable instantly. Revoking takes effect on the next request, with no deploy.
- It will not spend your credits silently. Only
attack_ideacosts credits, its cost is in the tool description, andget_specrefuses to generate a new spec — it tells your agent to do it in the app instead.