Agent integrations

Connect textportdocx to your AI assistant

textportdocx ships a hosted MCP server. Add it once and Claude, ChatGPT, Cursor or any MCP-capable assistant can check your credits, list your payments, and convert LaTeX into Word — acting as you, with your own balance.

https://textportdocx.in/mcp

What the MCP server is

One connector, your account.

MCP (Model Context Protocol) is the standard way an AI assistant talks to an external service. Our server lives at https://textportdocx.in/mcp and speaks Streamable HTTP. You sign in once with your textportdocx account; the assistant then gets a scoped token and every tool call runs as you — same credits, same history, same permissions as the website.

You need an account with credits

Reading your balance is free. A conversion costs 1 credit, charged only when it succeeds. Top up on the Credits page.

Connect in four steps

Takes about a minute.

  1. 1

    Copy the server URL

    https://textportdocx.in/mcp
  2. 2

    Add it as a custom connector

    In your assistant, open its connector / MCP settings and add a new remote (HTTP) server. Name it textportdocx and paste the URL. No API key or command line is needed for clients that support remote MCP.

  3. 3

    Sign in and approve

    The assistant opens a textportdocx sign-in window. Log in with the same account you use on the site, then approve the access request. That approval is what links the assistant to your credits.

  4. 4

    Try it

    Ask your assistant: “Check my textportdocx credit balance.” If it answers with your balance, the connection is live.

Client-by-client

Where the setting lives.

Claude (web & desktop)

Settings → Connectors → Add custom connector → paste the URL → Connect, then sign in and approve.

ChatGPT

Settings → Connectors → Create / Add MCP server → paste the URL, choose OAuth authentication, then enable it in the composer's tools menu.

Cursor / VS Code

Add an MCP server of type http with url: https://textportdocx.in/mcp in your MCP settings, then complete the browser sign-in it launches.

Clients without remote MCP

Bridge over stdio with mcp-remote using the JSON config below.

{
  "mcpServers": {
    "textportdocx": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://textportdocx.in/mcp"]
    }
  }
}

Tools your assistant gets

Seven tools, all scoped to you.

  • convert_latex_to_docxStart a LaTeX → Word conversion. Returns a pre-flight report (packages, math complexity, TikZ, bibliography, known issues) plus a one-time claim link valid for 30 minutes. Max 2 MB of .tex. Costs 1 credit, charged only on success.
  • get_conversion_resultPoll a job by job_id. Once finished, returns a signed expiring download URL — and the file inline for smaller documents.
  • list_conversionsTrack your agent-initiated jobs: pending, completed, failed or expired, with claim links for anything still waiting on you.
  • purchase_creditsLive credit packs with prices and a secure checkout link you open in your browser. It never charges a card.
  • get_accountYour email, credit balance, credits purchased, pages used and referral code.
  • list_credit_transactionsRecent credit ledger entries: purchases, referrals, conversions.
  • list_paymentsRecent credit-pack purchases with invoice numbers and status.

You can follow the same jobs in your browser on the agent dashboard, and top up on the pricing page.

How a conversion works over MCP

One click from you finishes it.

  1. 1

    The assistant calls convert_latex_to_docx

    It sends your .tex source and gets back a job id, a pre-flight report and a claim link.

  2. 2

    You open the claim link

    Signed in, the page runs the exact same in-browser engine the website uses — including server-side TikZ rendering — and uploads the finished .docx back to your job. The link expires in 30 minutes if unopened.

  3. 3

    The assistant calls get_conversion_result

    It receives the download URL (or the file inline) and can hand you the Word document directly.

Why the extra click?

The conversion engine is a WebAssembly build that runs in a browser, not on a server. Keeping it there is what lets the website promise your documents never leave your machine.

Privacy on the agent path

Different from the website flow.

An assistant can't reach your browser directly, so a file sent through MCP is stored briefly on textportdocx servers so the job can be completed. The stored source and the Word output are deleted within an hour of completion, and unclaimed jobs are dropped when the link expires. Conversions you start directly on textportdocx.in are unaffected — they run entirely in your browser and upload nothing.

Read the full Privacy policy.

Troubleshooting

The usual suspects.

“Failed to start authorization”

Your client cached an old registration. Remove the connector, restart the client, and add the URL again. Make sure you used the https URL with no trailing slash.

Sign-in window closes without connecting

Pop-ups or third-party cookies are blocked for textportdocx.in. Allow them and retry the approval step.

Tools return “Not authenticated”

The connector's token expired or was revoked. Disconnect and reconnect to sign in again.

“Insufficient credits”

Conversions need at least 1 credit. Top up on the Credits page; balance changes apply to the assistant immediately.

The job stays pending

Nobody opened the claim link yet. Open it while signed in, in the same browser as your account, then poll again.

File too large

The agent path caps .tex input at 2 MB. Convert larger projects or ZIPs directly on the website.

Still stuck? Reach us from the Contact page.

textportdocx

Loading everything into your browser — please wait…

Everything runs locally in your browser