Connect your agent to MdPlex

Prerequisites

• An MdPlex account (free to register)
• An API token — generate one in Settings → API Tokens
• An MCP-compatible client: Claude Code, Cursor, or any client supporting HTTP+SSE transport

01 Generate your API token

1. Go to Settings → API Tokens in your MdPlex account
2. Click Create token
3. Name it descriptively — e.g. Claude Code — main
4. Set scope to read_write
5. Copy the token immediately — it's only shown once

If your agent only needs to read documents (not write back), a read-scoped token is sufficient and limits exposure if the token is compromised.

02 Configure your MCP client

Claude Code

Add MdPlex to your project's .claude/settings.json or your global Claude Code settings:

{
  "mcpServers": {
    "mdplex": {
      "type": "http",
      "url": "https://app.mdplex.com/mcp/documents",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Cursor

In Cursor's MCP settings panel, add a new server:

• Name: MdPlex
• URL: https://app.mdplex.com/mcp/documents
• Transport: HTTP+SSE
• Auth header: Authorization: Bearer YOUR_TOKEN

Other MCP clients

Any client supporting HTTP+SSE transport works with the same endpoint and auth header. Refer to your client's MCP documentation for the exact configuration format.

03 Verify the connection

Once configured, ask your agent to list your documents:

"List my MdPlex documents"

The agent will call list_documents and return your document list. If you see your documents, you're connected.

Available tools

Agent write-back

The core capability of MdPlex is bidirectional — your agent can write documents back, not just read them. This turns MdPlex into a shared memory layer between you and your agent.

Basic workflow

1. Create the document — Start with a context doc (e.g. project-context.md) via the web UI
2. Agent reads it — At session start, the agent fetches it via get_document
3. Agent updates it — At session end, the agent calls update_document to record decisions, open questions, current state
4. You review — Document shows agent_updated status — skim before your next session

Instructing your agent

Add this to your CLAUDE.md for automatic context in every session:

## Context
- At session start: read MdPlex document ID 42 (project context)
- At session end: update that document with decisions made and questions resolved

Troubleshooting

Agent can't connect / no MdPlex tools available

• Verify your API token hasn't been revoked (Settings → API Tokens)
• Check the MCP server URL is exactly https://app.mdplex.com/mcp/documents
• Confirm your client supports HTTP+SSE transport

Agent can read but not write

• Check your token scope — must be write or read_write for write operations
• A read-scoped token succeeds on list/get/search but fails on create/update/delete

401 Unauthorized errors

• Ensure you're passing the full token value — it starts with a number followed by a pipe: 1|AbCd...
• If the token was copied from Infisical or a password manager, check for truncation
• Regenerate the token in Settings → API Tokens if in doubt

Rate limit errors (429)

• Free accounts are limited to 10 req/hr across REST API and MCP
• Upgrade to Builder for 500 req/hr