Sign in
Feedback

Send feedback to the MCPJam team

Tell the MCPJam team about MCPJam itself (a bug, a missing capability, something confusing, or a docs gap) at the moment you hit it. THE TEXT IS SENT TO THE MCPJAM TEAM, outside your organization, and kept for 180 days. It is stored in MCPJam's own database and never published. Summarize: never include secrets, tokens, or raw tool output. When a call failed, include its requestId (the failing response's x-request-id) so the report can be joined to our logs.

A 201 means the report is stored; notifying the team happens afterwards and cannot fail it. An identical report from you in the last 24 hours is answered with the existing report's id and duplicate: true instead of being filed again. Requires a signed-in account: guest tokens get 401. Rate-limited per user (429 with Retry-After); duplicates and key replays do not count.

post/feedback

Headers

Idempotency-Keystring

Retry-safe report key, validated STRICTLY. Replaying the SAME key with the SAME report returns the original receipt; reusing it for DIFFERENT content is a 409. A header that is present but empty, or longer than 256 characters, is a 400, never silently ignored. x-mcpjam-idempotency-key is accepted as an alternative spelling; sending both with different values is a 400.

x-mcpjam-launcherstring

The launching process's own DECLARED identity, as compact JSON: {"kind":"cli"|"mcp"|"github_action","client":"…","version":"…"}. Stored on the run as launcher and used only as a display label — source stays api and the audit trail reads the platform-minted attribution instead.

A header rather than a body field so that sending it never breaks against an older deployment: both eval-run bodies reject unknown properties, while an unknown header is ignored everywhere. For the same reason a malformed value, or a kind outside the three above, is DROPPED rather than rejected — a label must never fail a launch. Max 512 bytes.

Request body

kind'bug' | 'missing_capability' | 'confusing' | 'docs' | 'other' required

What sort of problem this is.

summarystring required

One line: what went wrong or what is missing. Trimmed. Appears in the team's notification.

detailsstring

What you were trying to accomplish, what you expected, and what blocked you. For a missing capability, name the task and any workaround you tried; there may be no request id. Summarize; never paste secrets, tokens, or raw tool output. Stored only in MCPJam's database, never emailed, and deleted after 180 days.

operationstring

The tool, CLI command or app page in use.

requestIdstring

The failing call's x-request-id, when there is one.

errorCodestring

The failing call's error code, e.g. INTERNAL_ERROR.

projectIdstring

A project you can see, when the report is about one; anything else is a 404. Omit it otherwise: no project is assumed.

Response

The report is stored. duplicate: true means an identical report from you was already recorded.

idstring required

The stored report's id.

receivedAtnumber required

When the report was received, in epoch milliseconds.

duplicateboolean required

True when an identical report from you was already recorded in the last 24 hours; id is that report.

Changes

Changed in 1 of the 126 revisions of this API.1