KovaPDF
Work on PDF files: compress, merge, split, convert, read scans, redact and check signatures.
होस्ट किया गया MCP सर्वर
npx add-mcp 'https://mcp.kovapdf.com'Claude Code, Codex, Cursor और अन्य में इंस्टॉल होता है
दस्तावेज़
Connect with KovaPDF
Let people connect KovaPDF to your app, automation tool or AI assistant in one click. Once connected, your app works on their files as them, with exactly the same limits as their KovaPDF account. It can never do more than the account can.
Overview
- Connect with KovaPDF is standard OAuth: the person sees your app's name, its domain and what it may do, and chooses Allow or Cancel. You get an access token for their account.
- Files and jobs run the tools: upload a file, start a job, and download the result from a short-lived link. They work with that access token, or with an API key.
- The MCP server gives AI assistants the same tools, with the same connection.
Files and results are deleted within an hour. Every file gets the same virus scan and safety checks as a file uploaded on the website.
Connect with KovaPDF
The authorization code flow with PKCE (S256), nothing else: no client secrets, no implicit flow, no password flow. Your app finds every address in the metadata at https://api.kovapdf.com/.well-known/oauth-authorization-server.
- Identify your app. Best: use an https address that serves a Client ID Metadata Document as your
client_id(it names your app and its redirect addresses, and shows your domain as verified). Or register withPOST /oauth/registerand keep theclient_idyou get. - Send the person to
/oauth/authorizewithresponse_type=code, yourclient_id, aredirect_uriyou registered (it must match exactly), acode_challengewithcode_challenge_method=S256, astate, and thescopeyou need. - They sign in if needed, see the request and choose Allow. They come back to your
redirect_uriwith acode, yourstateandiss. - Within two minutes, exchange the code at
POST /oauth/tokenwith yourcode_verifier. A code works once.
curl https://api.kovapdf.com/oauth/token \
-d grant_type=authorization_code \
-d client_id="$CLIENT_ID" \
-d code="$CODE" \
-d redirect_uri="https://yourapp.example/callback" \
-d code_verifier="$VERIFIER"
The answer has an access_token (one hour) and a refresh_token. A refresh token works once: each refresh returns a new pair, so always keep the newest. Using an old refresh token again ends the connection, as it may have been copied. Revoke a token at POST /oauth/revoke. The person can remove your app at any time in Dashboard, Connected apps; its tokens stop at once.
What an app may do
Ask only for what you need. The consent page lists each one in plain words.
tools:run: Compress, merge, split, organize, convert, read text from scans, redact and convert Bangla or Hindi text, within your account's usual limits.verify: Check the digital signatures in a PDF and read the report.sign:read: List your signature requests and see who has signed.sign:write: Prepare signature requests and send them after you confirm.
Files
Upload a file once and use its id in jobs. It is kept for one hour.
curl https://api.kovapdf.com/api/v1/files \
-H "Authorization: Bearer $TOKEN" \
-F file=@report.pdf
Small files can also be sent as JSON { "name": "a.pdf", "contentBase64": "..." }, and a file on the web as { "url": "https://..." }. An address is downloaded once, over https, from public addresses only.
Jobs
curl https://api.kovapdf.com/api/v1/jobs \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{ "tool": "compress", "inputs": ["FILE_ID"], "options": { "level": "strong" } }'
The answer is the job, queued. Ask for GET /jobs/ID until its state is done or failed; while it runs, the Retry-After header says how many seconds to wait. When it is done, result.files has download links that work for 15 minutes (ask again for fresh ones) and result.report has what the tool found.
Full example: upload, run, download
Compress one PDF from start to finish. $TOKEN is an access token from Connect with KovaPDF, or an API key that may run tools.
1. Upload the file. Keep the file.id from the answer.
curl https://api.kovapdf.com/api/v1/files \
-H "Authorization: Bearer $TOKEN" \
-F file=@report.pdf
# 201 Created
{ "file": { "id": "FILE_ID", "name": "report.pdf", "type": "application/pdf", "size": 482113, "expiresAt": "..." } }
2. Start the job. Keep the job.id.
curl https://api.kovapdf.com/api/v1/jobs \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{ "tool": "compress", "inputs": ["FILE_ID"], "options": { "level": "basic" } }'
# 202 Accepted
{ "job": { "id": "JOB_ID", "tool": "compress", "state": "queued", "retryAfter": 3 } }
3. Ask for the job until state is done or failed. Wait the seconds in Retry-After between asks.
curl https://api.kovapdf.com/api/v1/jobs/JOB_ID \
-H "Authorization: Bearer $TOKEN"
# 200 OK, when it is done
{ "job": { "id": "JOB_ID", "state": "done",
"result": {
"files": [ { "id": "RESULT_ID", "name": "report-compressed.pdf", "type": "application/pdf",
"download": { "url": "https://api.kovapdf.com/api/v1/downloads/...", "expiresAt": "..." } } ],
"report": { "originalBytes": 482113, "compressedBytes": 96410 } } } }
4. Download the result from download.url. The link itself is the permission, so it needs no Authorization header. It works for 15 minutes; ask for the job again for a fresh one.
curl -o report-compressed.pdf "DOWNLOAD_URL"
If the job ends failed, its error.code says why, as in Errors and limits. Fix the request for a 4xx code; wait and try again for busy or limit_reached. The JavaScript and Python packages do these four steps for you.
Tools
| Tool | MCP name | What it does | Options |
|---|---|---|---|
verify | verify_pdf_signature | Check PDF signatures | No options. Needs the verify permission. |
compress | compress_pdf | Compress PDF | level (basic, strong or quality) or targetKb. |
merge | merge_pdfs | Merge PDFs | Two or more PDFs, in order. |
split | split_pdf | Split PDF | mode all, range (with pages), every (with pagesPerPart) or size (with maxMb). |
organize | organize_pages | Reorder, rotate or delete pages | pages: the new order, each a number or { page, rotate }. |
convert | convert_pdf | Convert files | to word, excel, jpg or png for a PDF; to pdf for an office file or pictures. |
ocr | ocr_pdf | Read text from a scan | language and pages. |
redact | redact_pdf | Redact a PDF | terms and or patterns, matchCase, wholeWord, label. The report lists every removal. |
bijoy_to_unicode | bijoy_to_unicode | Bijoy to Unicode | text, or one.txt file; keepEnglish. |
unicode_to_bijoy | unicode_to_bijoy | Unicode to Bijoy | text, or one.txt file. |
kruti_to_unicode | kruti_to_unicode | Kruti Dev to Unicode | text, or one.txt file; keepEnglish. |
The list, with what each tool needs, is also at GET /tools. The OpenAPI file describes every call.
MCP server
AI assistants that support remote MCP servers can add KovaPDF at https://mcp.kovapdf.com (Streamable HTTP). The assistant connects with Connect with KovaPDF, then offers the tools above with the person's own limits. Files can be given as a file id, an https link, small base64, or a file attached in the chat. Results come back as download links.
Add it in one click: Add to Cursor (or the web link), Add to VS Code (or the web link). Other assistants take the address https://mcp.kovapdf.com.
Every result says it was done with KovaPDF. Text read from a file comes back marked as file content, so an assistant treats it as data and never as instructions.
Signature requests are always two steps: the assistant prepares a draft, shows it to the person, and sends it only after they confirm.
The assistant needs a connected KovaPDF account: every tool then works within that account's usual limits, and a free account is enough to start. Without one, the server answers 401 with a sign in challenge, and the assistant starts Connect with KovaPDF.
Errors and limits
Every error is JSON { error, code }. The codes to act on:
limit_reached(429): the account's allowance is used up for now, the same as on the website.Retry-Aftersays when, andnextFreeAtwhen known.too_many_jobs(429): this account already has the most jobs waiting. Wait for one to finish.busy(503): KovaPDF is busy. Try again afterRetry-Afterseconds. Integrations have their own lane, so they never slow down people on the website.too_big(413): the file is too big for this way of sending it.insufficient_scope(403): the token or key may not do this.invalid_token(401): connect again.file_expired,link_expired(410): upload the file again, or ask for the job again for a fresh link.invalid_options(400): an option is wrong for this tool. The sentence names it (for examplemode range needs pages, for example 1-3,5), andissueslists each problem with its option.unsupported_file,invalid_pdf(422): the file is not one this tool takes, or the PDF cannot be read. Send another file.
Every code the files, jobs and MCP calls can answer with is in the Tools API and MCP table.
See also every error code and the API limits.