The IndexMCP

MCP server

Every service on the Index, as tools an agent can call. Point your MCP client at one address: the formula reader works with no key, and the project tools take the same key and credit as the API.

Open now

The address

https://api.intex.institute/mcp

Streamable HTTP, one JSON answer to each request, no sessions. It speaks the current protocol, 2026-07-28, and the handshake of 2025-11-25, 2025-06-18 and 2025-03-26, so clients from this year and last connect alike.

Connecting a client

In Claude Code:

claude mcp add --transport http intex https://api.intex.institute/mcp --header "Authorization: Bearer YOUR_KEY"

In a client that takes a JSON configuration (the field names vary a little from client to client):

{"mcpServers": {"intex": {
  "type": "http",
  "url": "https://api.intex.institute/mcp",
  "headers": {"Authorization": "Bearer YOUR_KEY"}
}}}

Without the header, read_formula works and the project tools answer with where to get a key. Keys and credit are on the API page of your portal, app.intex.university/api-keys, and an account is free at intex.university/signup. Keep the key in your client's own settings, out of files you share.

The tools

ToolWhat comes backPrice
read_formulaFor one formula: what it reads as, the words a screen reader says, the text it copies out as, and its MathML. The same as Formula.Free without a key, thirty every ten minutes; with one, a tenth of a cent
count_projectPages, formulas, figures and tables, and what each tool below would cost for the project.Free, with a key
make_tagged_pdfThe tagged PDF, as a file in the answer.6¢ a page
make_web_pageThe web page: its HTML and its figures, as files.4¢ a page
check_accessibilityThe report, as data: each WCAG 2.1 criterion with its verdict, and every place a person is needed, by file and line.3¢ a page
make_everythingAll of it from one build: the PDF, an archival copy, the page and the report.10¢ a page

Pages are the pages of the PDF the project makes, the same count count_project gives for free, so an agent can ask the price before it spends anything.

Sending a project

Each project tool takes the project in one of two shapes:

ArgumentWhat goes in it
filesThe text files by their path inside the project, each with its whole text: the .tex files, and any .bib, .bbl, .sty or .cls of your own.
binary_filesFigures by path, each in base64.
archiveInstead of the two above: the whole project as one .zip or .tar.gz, in base64.
mainOptional. The main .tex file, when the project has more than one.

Up to 24 MB for the project. PNG and JPEG figures are placed as they are; a figure in PDF, EPS or SVG is answered, for now, with its name, to be saved as a PNG beside it.

What comes back

Files come inside the answer as embedded resources: the PDF in base64 with its type, the HTML as text. The numbers come as structured content, and every paid call says its pages, cost_cents and credit_cents. A project that cannot be built comes back as a tool error that names the file and the line, and costs nothing. So does a project your credit cannot cover.

Limits

  • Thirty project calls every ten minutes on one key, counted together with the API; six hundred formulas with a key.
  • A build runs for at most five minutes. One that runs longer is stopped, answered with the reason, and costs nothing.
  • A project is read where it arrives and deleted the moment the answer leaves us. We keep the count of pages, for the bill.