Skip to main content

Troubleshooting

My client doesn't show PrompTick tools​

  1. Restart the client fully after adding the config. Most MCP clients only reload servers on startup.
  2. Check the config file path. Each client's page lists the exact filename (e.g. .cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json).
  3. Validate the JSON. A trailing comma or missing quote will silently disable the server.
  4. Confirm the key format. It must start with mk_live_.

401 Unauthorized​

  • Key was revoked, mistyped, or the wrong key type (starts with pk_live_ instead of mk_live_).
  • Regenerate in the MCP page and update your client config.

429 Rate limit exceeded​

Your key hit its per-key rate limit. Wait a few seconds and retry. For sustained higher throughput, contact support about a higher-tier plan.

needs_clarification loop in generate_prompt / improve_prompt​

If your assistant keeps hitting clarification responses, either:

  • Supply more detail in use_case / improvement_instructions upfront, or
  • Set skip_clarification: true to get an immediate best-guess result.

needs_context in enrich_coding_prompt​

That's the normal first-step response. Your assistant should read each requested file/path, then re-call the tool with context_answers filled in and task_analysis_passthrough passed back unchanged from step 1.

Tool calls aren't counted / budget seems wrong​

  • Every MCP tool call consumes one AI Action. Internal sub-steps within a single workflow are free.
  • Check Settings → Usage at app.promptick.ai for your current month's AI Action count.

Progress notifications aren't appearing​

Progress notifications require an SSE-capable transport. All supported clients handle this automatically, but if you've proxied the endpoint through a layer that strips streaming (some corporate gateways), progress won't appear — the tool still completes correctly.

Still stuck?​

Reach out via the contact form on promptick.ai or your PrompTick support channel.