pulse-mcp
Pulse's document-extraction API as an MCP server — turn PDFs, Office documents, images, and spreadsheets into clean markdown, structured JSON, and tables from Claude Desktop, Cursor, or any MCP client.
Quickstart
You need a Pulse API key (from the Pulse dashboard). Add to your MCP client config (Claude Desktop, Cursor, …):
{
"mcpServers": {
"pulse": {
"command": "uvx",
"args": ["pulse-mcp@latest"],
"env": { "PULSE_API_KEY": "<your-pulse-api-key>" }
}
}
}
Instead of the env var, the key can live in ~/.pulse/config.toml:
api_key = "<your-pulse-api-key>"
Tools
| Tool | What it does |
|---|---|
extract |
Document → markdown (chunking, HTML, figure descriptions optional) |
apply_schema |
Structured JSON from an extraction, against your JSON schema |
generate_schema |
AI-draft or refine an extraction schema from a prompt |
extract_tables |
Pull tables (HTML/markdown) out of an extraction |
split_document |
Partition a document into topic page-ranges |
batch_extract |
Many documents in one asynchronous batch |
run_pipeline |
Run a pipeline saved in the Pulse dashboard |
get_job |
Poll any asynchronous job |
extract takes a file_url — or, because this server runs on your machine, a local
file_path: the server process reads the file and uploads it out-of-band, so file
bytes never pass through the model. Up to 50 MB; pdf, png, jpg, jpeg, bmp, tiff, docx,
pptx, xlsx, xlsm, csv, txt, html.
Hosted alternative
Don't want a local process? The same tools are served hosted at
https://mcp.runpulse.com/mcp (Streamable HTTP) — authenticate with your API key as an
x-api-key header.
Links
1 maintainer
Metadata
1 maintainer
Release files for pulse-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulse_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / pulse_mcp-0.1.2-py3-none-any.whl
| Download URL | pulse_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 40.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00747b06ef0ed8cf11082ba633232b1c90d15b016e41f62577d09fd2d99297dd
|
|
BLAKE2b-256 checksum How to use checksums |
419d011f17c0f9efad0738b645a4a90349c6f4ce4ffd95a15456625ec71844c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency log
