Search app ideas and generate mockups from Claude Code, Codex, Cursor, VS Code / Copilot, or Windsurf with one remote MCP server and a browser-based OAuth flow.
Choose the instructions that match the MCP client you are actually using. Every host connects to the same remote AppWispr endpoint, but the place you store the config differs.
Current host support
Claude Code is the most direct tested flow. Codex, Cursor, VS Code / Copilot, and Windsurf can all point at the same remote HTTP MCP URL and finish the OAuth browser handoff the first time they connect.
Best if you want the fastest guided AppWispr setup. The command below registers the remote HTTP MCP server directly.
Terminal
claude mcp add --transport http appwispr https://appwispr.com/api/mcp
Connect and authenticate
1Run the command in the repository where you want AppWispr available.
2Open Claude Code and run `/mcp`.
3Select `appwispr` and finish OAuth in the browser window that opens.
4Prompt Claude to use `search_ideas` or `generate_mockups`.
Authentication
AppWispr MCP uses OAuth with a browser-based authorization code flow. Your MCP client discovers metadata, opens the authorization page, and stores the resulting bearer token for future tool calls.
The resource endpoint ishttps://appwispr.com/api/mcp
Supported scope:mcp:tools
Tokens are created from the signed-in AppWispr session, so you do not need to manage a separate API key.
Rate Limits
AppWispr MCP does not currently publish a separate public credit or header-based rate-limit contract. Instead, treat the server as a workflow endpoint and keep long operations bounded with timeouts.
Usewait_for_completion=falsewhen you want to queue work and poll separately.
Discovery timeouts accept 10 to 300 seconds, and mockup generation timeouts accept 10 to 600 seconds.
For long-running work, callget_idea_search_runorget_mockup_buildafter the initial call.
Tools Reference
The AppWispr MCP server currently exposes four tools. Together they cover discovery kickoff, discovery polling, mockup kickoff, and mockup polling.
search_ideasMCP Tool
Starts a new AppWispr discovery run against live sources and optionally waits for idea candidates to finish loading.
Inputs
`query`
`sources`
`wait_for_completion`
`timeout_seconds`
`limit`
Output
Returns `run_id`, status metadata, idea summaries, and a `workspace_url` for the full run.
get_idea_search_runMCP Tool
Fetches the latest status of an existing discovery run so the agent can poll until ideas are ready.
Inputs
`run_id`
`limit`
Output
Returns the same discovery shape as `search_ideas`, including top ideas and the workspace link.
generate_mockupsMCP Tool
Starts AppWispr Build It for a chosen idea slug and can wait until the mockup project has produced screens.
Inputs
`idea_slug`
`app_surface`
`requested_screen_count`
`wait_for_completion`
`timeout_seconds`
`include_html`
Output
Returns build progress, screen summaries, `workspace_url`, and generated screen metadata.
get_mockup_buildMCP Tool
Fetches the latest build status for an idea slug and returns screens when they are available.
Inputs
`idea_slug`
`include_html`
Output
Returns the latest build summary with status, progress, and any generated screens.
Workflow Pattern
The most reliable pattern is to treat discovery and mockup generation as two-stage jobs.
1. Callsearch_ideaswith a niche or pain point.
2. If you do not wait for completion, pollget_idea_search_rununtil you have idea candidates and a slug.
3. Startgenerate_mockupswith the chosen idea slug.
4. If needed, pollget_mockup_builduntil the build is complete and screen metadata is ready.
Workspace Links
AppWispr MCP returnsworkspace_urlfields so the assistant can hand you directly into the full product when you want deeper review.
Discovery runs
Discovery tools link to/workspace/runs/<run_id>
Mockup projects
Build tools link to/workspace/ideas/<idea_slug>/mockup
CLI Reference
If your client supports command-line registration, this is the fastest way to add AppWispr.
Production endpoint
claude mcp add --transport http appwispr https://appwispr.com/api/mcp
Open the MCP panel again, select the AppWispr server, and finish the browser OAuth flow. If the client cached a bad attempt, remove and re-add the server entry.
A tool is still running
Queue the job withwait_for_completion=falseand then poll with the correspondingget_*tool.
No build exists for an idea slug
Make sure you have already calledgenerate_mockupsfor that slug. The polling tool only works after a build has been created.
Ready to connect AppWispr?
Start with the MCP landing page if you want the overview first, or jump straight into the workspace after you have authenticated your coding assistant.