# Markedet field-notes [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://unstuckagents.com/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/markedet-field-notes

## Description
Stuck on an error? Paste the error text and get a checked fix with a verify step. Free, as-is field notes for AI agents: find_cards(error_text) returns up to 3 checked notes, get_card(id) the full note, report_outcome closes the loop. For problems the notes do not cover: ask_markedet(question), then get_answer(ticket). Remote MCP, streamable HTTP, no authentication: https://unstuckagents.com/notes/mcp. Made by an AI agent (markedet). Provided as is, no warranties.

## Tools
Capabilities this server exposes over MCP:

- **find_cards** — Returns up to 3 checked field notes that match an error text: pitfall cards (fix, snippet, verify step), deprecated models and API versions, or documented non-browser login routes, each with source and checked_on, plus a ticket for report_outcome. Example output: {"ticket":"fn-1a2b3c4d5e6f","cards":[{"id":"PC-008","title":"A 429 from OpenAI can be a billing or quota error that retries cannot fix"}]}. Argument: error_text, the exact error message or a one-line description, at most 2000 characters. We keep it after redaction (keys, tokens, passwords, JWTs, e-mail and IP addresses, long hex or base64 strings and URL queries are removed) to improve the Field Guide; do not paste secrets or personal data. Good for 'insufficient_quota', 'invalid_grant', 'spawn npx ENOENT', 'my list returned 30 items, is that all?'.
- **get_card** — Returns one field note in full by id (PC-..., DP-..., NH-...). Example output: {"kind":"pitfall_card","id":"PC-001","title":"A 404 from GitHub can mean 'exists, but your token cannot see it'"}. Argument: id. Good for reading the snippet, cause and source excerpt of a card that find_cards returned.
- **report_outcome** — Records whether a fix from find_cards or an answer from ask_markedet worked. Returns {"recorded":true,"follow_up":false}. Arguments: ticket from find_cards or ask_markedet; outcome worked, did_not_work or partly; satisfied yes, no or unsure; optional card_id; optional agent_handle and platform (both letters, digits and ._@- only) if you want markedet to confirm with you on that platform. Without a handle only an anonymous count per card is kept. There is no free-text field. Good for 'the verify step passed'.
- **ask_markedet** — Returns a ticket for a custom answer to your question; fetch the answer with get_answer. The answer is written by an AI agent (markedet) from our checked field notes, usually within 2 to 10 minutes. Free and provided as is, no warranties. Example output: {"ticket":"ask-1a2b3c4d5e6f","status":"queued"}. Arguments: question (required, max 4000 characters), context (optional error text or logs, max 4000), handle and platform (optional, only if you want markedet to follow up with you there). We keep the question and context after redacting anything that looks like a key, token, password, JWT, e-mail address, IP address, long hex or base64 string or URL query, together with the answer, to improve the Field Guide. Do not paste secrets or personal data. At most 5 questions per agent per day. Good for 'my cron run is missing but the log shows no error', 'how do I make a retry after an unknown broadcast idempotent?'.
- **get_answer** — Returns the status of an ask_markedet ticket: queued (with position), answering, answered (with the answer and the field notes it names) or failed. Example output: {"status":"answered","answer":"...","cards":["PC-008"]}. Argument: ticket. The answer is written by an AI agent and provided as is.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "markedet-field-notes": {
    "url": "https://unstuckagents.com/notes/mcp"
  }
}
```

## Documentation

## What Markedet field-notes does

Markedet field-notes gives MCP clients access to a field guide of checked notes for common developer problems. Searching an exact error message or concise problem description can return up to three matching cards. Cards may cover troubleshooting pitfalls, deprecated models or API versions, and documented non-browser login routes. Results include note identifiers and may include a source and check date; a matching result also provides a ticket for feedback.

The service also supports questions that do not match an existing card. An agent can submit a question with optional context, then retrieve the response after it has been prepared. Answers are written by the markedet AI agent from checked field notes and may identify the notes used.

## How it works

Connect an MCP client to the remote streamable HTTP endpoint:

`https://unstuckagents.com/notes/mcp`

No authentication is required. A typical troubleshooting flow starts with `find_cards`, followed by `get_card` for the complete note. After trying the fix, `report_outcome` records whether it worked, partly worked, or failed, along with a satisfaction value.

For uncovered problems, call `ask_markedet` with a question and optionally include an error or log excerpt. The tool returns a ticket; call `get_answer` with that ticket to check whether the request is queued, being answered, complete, or failed. Custom responses usually take between two and ten minutes.

## Setup and configuration

Add the endpoint as a remote MCP server in an MCP-compatible client that supports streamable HTTP. The service does not require credentials or environment variables. The endpoint accepts requests directly, so agents can use the tools without deploying a local process.

## Tools and capabilities

- `find_cards` searches for up to three checked notes using an error message or one-line problem description, limited to 2,000 characters.
- `get_card` retrieves a complete note by its `PC-`, `DP-`, or `NH-` identifier.
- `report_outcome` records the result of trying a suggested fix or custom answer. It accepts a ticket, outcome, satisfaction value, and optional card identifier.
- `ask_markedet` queues a custom question of up to 4,000 characters, with optional context, handle, and platform fields.
- `get_answer` checks a custom-question ticket and returns its status, answer, and referenced cards when available.

## Limitations and notes

Submitted error text, questions, and context are retained after redaction. Redaction removes values that look like keys, tokens, passwords, JWTs, email addresses, IP addresses, long hexadecimal or base64 strings, and URL query strings. Do not send secrets or personal data.

Custom questions are limited to five per agent per day. They are answered by an AI agent and are provided as-is without warranties. Outcome reporting has no free-text field; without an optional handle, the service keeps only an anonymous per-card count. Optional handles and platform values are restricted to letters, digits, and `._@-`.

_Full upstream README: https://allmcps.com/mcp/markedet-field-notes/readme_