Give your agents document context they can defend.

Connect Ninjadoc as an MCP tool and let agents extract answers from PDFs with citation URLs, bounding boxes, and audit-ready evidence attached to every result.

Create an API key See auditability

MCP server config

{
  "mcpServers": {
    "ninjadoc": {
      "serverUrl": "https://api.ninjadoc.ai/mcp/nj_API_KEY"
    }
  }
}

How agents use it

Connect the tool

Add the Ninjadoc MCP server URL to your MCP-compatible client or agent runtime.

Ask document questions

The agent can request fields, facts, or answers from uploaded PDFs and document workflows.

Return evidence

Every answer includes source coordinates and citation URLs the agent can pass downstream.

Tool result

The agent gets an answer and the proof behind it.

A normal parser stops at text. Ninjadoc returns evidence in the same response, so an agent can cite the source, link to the highlighted document region, and hand off the result to a reviewer or system of record.

Bounding boxes

Citation URLs

Cropped source images

Confidence scores

Agent tool response

{
  "answer": "The termination notice period is 30 days.",
  "confidence": 0.97,
  "evidence": [{
    "page_index": 4,
    "citation_url": "https://api.ninjadoc.ai/citations/01JV.../4/page.jpg",
    "citation_url_cropped": "https://api.ninjadoc.ai/citations/01JV.../4/cropped.jpg",
    "located": [{
      "boxes": [{
        "normalized": { "x1": 112, "y1": 530, "x2": 748, "y2": 589 }
      }]
    }]
  }]
}

Build paths

Use MCP for agent workflows

Best when a model or agent client needs to call document extraction as a tool and include source evidence in its response.

Create an API key

Use REST for product workflows

Best when your backend controls uploads, batching, storage, routing, and review queues directly.

Read API docs

FAQ

What does MCP-ready mean?

MCP-ready means an AI client or agent can connect to Ninjadoc as a tool server and request source-grounded document answers without custom integration code for every agent environment.

Which agents can use this?

The Ninjadoc MCP server is designed for MCP-compatible clients and agent environments, including Claude Desktop, Cursor, and custom MCP clients.

What does the agent receive?

The agent receives structured answers with confidence, page indexes, bounding boxes, citation URLs, and cropped citation URLs, so it can include source evidence in downstream responses.

Can I still use the REST API?

Yes. MCP is for agent workflows. The REST API remains the best fit when you want direct application integration, batch processing, or custom backend control.