MCP

Use a Model Context Protocol (MCP) client to call document and Node media tools. Configure this remote server URL:

https://agentsmarkdown.com/mcp

It supports discovery and typed calls for documents, review, sharing, events, and local-Node media.

Authentication

There are two useful patterns:

Scoped document work: pass a document share URL or a document ID plus key in tool arguments.

Account and Node work: send an AgentsMarkdown app-session token as:

Authorization: Bearer APP_SESSION_TOKEN

Replace APP_SESSION_TOKEN with an AgentsMarkdown asess_ token. Node media tools require the account session. A share key alone is intentionally insufficient.

Document tools

The server provides the following operations:

• Create, read, replace, and append documents
• List and add comments
• List, add, accept, and reject suggestions
• Create scoped shares
• Publish or unpublish
• List events
• Read the current AgentsMarkdown skill

Use the exact names returned by tools/list. They are namespaced with agentsmarkdown..

Node media tools

If your signed-in Node has the required capability, you can call these tools:

• agentsmarkdown.generate_image
• agentsmarkdown.speak_text
• agentsmarkdown.transcribe_audio
• agentsmarkdown.ocr_image

Image and speech tools return insertable Markdown. Transcription and OCR return text. Audio or image input can be supplied as base64 data or as an authorized same-origin /f/ asset URL.

Inspect the server

To read the server metadata, send this request:

curl -fsS https://agentsmarkdown.com/mcp

List tools with JSON-RPC:

curl -fsS https://agentsmarkdown.com/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"tools/list",
    "params":{}
  }'

Append a document item

To append a completed task, send this request:

curl -fsS https://agentsmarkdown.com/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/call",
    "params":{
      "name":"agentsmarkdown.append_doc",
      "arguments":{
        "doc":"DOC_ID",
        "key":"SHARE_KEY",
        "text":"- [x] Verified the build"
      }
    }
  }'

Replace DOC_ID and SHARE_KEY with the values from your share link.

For replacements with a version check, read the document first and pass its baseVersion.

Client configuration

MCP client configuration formats differ. Add the endpoint as a remote HTTP MCP server, then attach an authorization header only when the client needs account-owned documents or Node media.

Avoid pasting an asess_ token into a shared configuration file. Prefer the client's secret or environment-variable support.