Markedet field Notes

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 ._@-.