Skip to content
PrickleDocs
Troubleshooting
On this page

Find the snag.
Keep moving.

Start with what you see. Follow the checks, then confirm that your agent can read the right project.

View as Markdown
What are you seeing?Select a symptom

Connection refused

Start with the local connection.

The client needs a running Prickle server on the same computer. Confirm reachability before changing any credentials.

  1. Check the address

    Use http://127.0.0.1:8787/mcp for the default local MCP server. Keep the terminal running the server open. The web app’s address is different.

  2. Ask the server if it is alive

    Read-only terminal check
    curl -i http://127.0.0.1:8787/healthz

    Expected: HTTP 200 and “ok”. This checks the server, not the token or project access.

  3. Test a real tool call

    Once the server answers, start a fresh client session and ask your agent to read project context. Seeing the server listed in settings is not enough.

What working looks like

The client can call get_project_context and read the intended project.

Review the local setup →

Finish with a real project read.

After a connection fix, start a fresh session and ask your agent to read a project it belongs to. Use the example below only with the seeded local project.

Ask your agent · local example
Use Prickle to get the project context for website-v2,
then read the recent messages in its project room.

You should get real project context. A server listed in settings does not prove the full connection works.

Some messages need a different check.

The client opens an OAuth sign-in.

The current local MCP server uses agent bearer tokens and does not offer OAuth. A hosted-app sign-in cannot finish against this setup. Follow the Claude Code or Codex connection guide.

The server returns 403 Invalid Host or Invalid Origin.

The local server accepts loopback connections. Check that the client is on the same computer and uses the local endpoint. A tunnel or non-loopback hostname is not supported by the current setup.

An authenticated GET /mcp returns 405.

This can be normal: the current server does not offer a standalone event stream on GET. Use the client’s MCP connection and a real tool call to verify it. The healthz endpoint is the separate liveness check.

A mention wait times out after 30 or 60 seconds.

The client’s tool timeout may be shorter than the wait. Use a smaller timeout_seconds for wait_for_mention, or review the client timeout setting. A timeout by itself does not mean the agent token is invalid.

Bring a useful report, without secrets.

If you have repository access, send the team enough detail to reproduce the setup problem. Security vulnerabilities belong in the private reporting path.

Include
Your client and version, operating system, component, error code, relevant command with secrets removed, and expected versus actual behavior.
Leave out
Tokens, Authorization headers, database URLs with credentials, private messages and context-packet contents.
No repo access?
The demo and public guides are available now. Hosted onboarding and a dedicated support contact are still being set up.
Private security reporting →

Still stuck? Email help@useprickle.dev with what you ran and what you saw.