Idea search built for demand
Start with a niche, audience, or problem statement and let your assistant run discovery before it commits to a direction.
v0.1.0 — remote MCP now available
Give your AI assistant the power to find what to build.
A lightweight MCP server that lets Claude Code, Codex, Cursor, VS Code/Copilot, and Windsurf search ideas, inspect discovery runs, and turn the strongest concept into mockups.
Claude Code
Add the remote MCP server directly from Claude.
$
claude mcp add --transport http appwispr https://appwispr.com/api/mcpCodex CLI
Use the official Codex MCP add command for the same endpoint.
$
codex mcp add appwispr --url https://appwispr.com/api/mcpBuilt for
Claude CodeCodexCursorVS Code / CopilotWindsurf
OAuth completes in the browser once, then your MCP client can keep calling the AppWispr tools directly.
Why It Fits
Idea research and mockups as one protocol.
The AppWispr MCP flow is built around the moment before code: searching for demand, choosing the best direction, and turning that direction into screens a team can react to.
Mockups from the winning idea
Once an idea is chosen, the same agent can kick off mobile mockup builds and wait for the visual package to finish.
OAuth-native MCP flow
Remote MCP plus OAuth means no API keys to paste into clients. Sign in once in the browser and keep moving.
Setup
Zero-friction connection.
Add the remote HTTP server to your MCP client, finish OAuth in the browser, and you are ready to prompt for ideas or mockups.
Start with Claude Code if you want the quickest path:/mcp
If your client prefers a config file, point it athttps://appwispr.com/api/mcp
Read the setup guideClaude Code
One command to register the server.
claude mcp add --transport http appwispr https://appwispr.com/api/mcpCodex
Official Codex CLI add command for a remote HTTP MCP server.
codex mcp add appwispr --url https://appwispr.com/api/mcp.mcp.json
Useful for clients that want a project-level config file.
{
"mcpServers": {
"appwispr": {
"url": "https://appwispr.com/api/mcp"
}
}
}Tooling
Four tools. One workflow.
The AppWispr server exposes the exact tools your coding assistant needs to search, wait, generate, and poll without asking you to hop between products.
search_ideas
Start a discovery run from a theme, niche, or pain point and return the generated idea candidates your assistant can reason over.
get_idea_search_run
Poll a discovery run to inspect completion status, the strongest ideas, and the slugs the next tool should use.
generate_mockups
Turn a selected idea slug into a mockup build request, including device framing and screen-count instructions.
get_mockup_build
Check a mockup build until the generated visual package is ready for review or downstream handoff.
Learn More
Keep exploring from the page.
MCP docs and setup flow
Read the AppWispr setup guide, OAuth notes, and tool reference for the remote MCP server.
Open the AppWispr workspace
Jump into the signed-in product and keep exploring ideas, runs, and generated mockups from the full app.
See the daily featured idea
A live example of the kind of build direction AppWispr turns research into once signals are processed.
Read the AppWispr blog
Editorial notes on demand, positioning, and how strong app ideas turn into build-ready output.
FAQ
Questions before you connect?
What does the AppWispr MCP server actually do?
It gives MCP-compatible coding assistants direct access to AppWispr's idea discovery and mockup generation workflows, so the agent can search, compare, and generate without leaving the editor.
Which assistants can connect today?
The landing page is framed for Claude Code, Codex, Cursor, VS Code / Copilot, and Windsurf because those are the same hosts the reference page highlights and the flow maps well to AppWispr's remote MCP endpoint.
How does authentication work?
The server uses OAuth. Your MCP client opens a browser window once, you complete sign-in, and the client stores the resulting session for future tool calls.
What is the fastest way to test it?
For Claude Code, the quickest path is adding the remote HTTP MCP server, finishing OAuth in the browser, and then prompting the assistant to use search_ideas followed by generate_mockups.
Do I need AppWispr open in another tab while I use it?
No. After the OAuth handoff, your MCP client can call the remote tools directly. You can still open the full site whenever you want deeper review in the workspace.
Start building from the terminal.
Connect AppWispr once, let your assistant discover better ideas, and move straight into mockups when a direction is worth pursuing.
Used by teams exploring AppWispr from Claude Code, Codex, Cursor, and more.