Firecrawl MCP Server vs Paxa Labs
A side-by-side look at the Firecrawl MCP Server and Paxa Labs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Firecrawl MCP Server for search & data extraction work as a local process; choose Paxa Labs for text-to-speech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Firecrawl MCP Server when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIRECRAWL_API_KEY, HTTP_STREAMABLE_SERVER. - You want tools like
firecrawl_scrape, firecrawl_map, firecrawl_search.
Choose Paxa Labs when
- You need dedicated capabilities in the Text-to-Speech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PAXA_API_KEY. - You want tools like
speak, queue_speech, control_playback.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Text-to-Speech |
| Quality signal | 90/100 · Excellent | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | FIRECRAWL_API_KEYHTTP_STREAMABLE_SERVER | PAXA_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 7,669 | 10 |
| Directory activity | 14 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 25 | 14 |
| Full listing | View Firecrawl MCP Server | View Paxa Labs |
Tools & capabilities
Firecrawl MCP Server tools 25
firecrawl_scrapeRetrieve and extract content from one supplied URL through Firecrawl. Use this when the request identifies a page and needs its content or defined fields. It can return markdown, HTML, links, screenshots, branding data, a targeted answer, or JSON matching a supplied schema; JSON is useful when the requested result has defined fields, while markdown preserves readable page content. This tool operates on a known page. For a set of pages use `firecrawl_crawl`, and to discover page URLs use `firecrawl_map` or `firecrawl_search`. Options include JavaScript render delay, cache age, main-content filtering, PII redaction, and lockdown cache-only retrieval. Browser actions may change the live page when interactive actions are enabled. Firecrawl may reuse recently indexed content instead of refetching the page, and the reuse window varies by domain. Set `maxAge: 0` to force a live fetch, or a smaller `maxAge` to bound how stale reused content may be. A successful response does not by itself confirm that the state it describes is still current. Returns the selected content formats and page metadata.firecrawl_mapEnumerate URLs indexed under one website through Firecrawl without fetching each page's content. Use this when the request asks for a site's URL inventory, when several relevant pages must be located, or when the desired page URL is unknown. An optional `search` term narrows the URL list, while sitemap, subdomain, query-parameter, and result-limit options control coverage. Returns matching URLs rather than page bodies. Retrieve one page with `firecrawl_scrape`; collect content across multiple pages with `firecrawl_crawl`.firecrawl_searchSearch web, news, or image sources and return ranked results. Operators include quoted phrases, `-term`, `site:host`, `inurl:term`, `intitle:term`, and `related:host`; the set is non-exhaustive. `includeDomains` and `excludeDomains` are mutually exclusive hostname filters; categories limit results to GitHub, research, PDF, or developer sources. For a programming question, add `categories: ["developer"]`. It searches an index of GitHub issues, merged pull requests, repository READMEs, and curated documentation sites, and returns the hits in `data.developer` beside the web results. `categories: ["research"]` restricts these web results to research-affiliated websites and returns page snippets. The `firecrawl_research_*` tools are a separate surface that searches paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature. `scrapeOptions` can attach extracted page content; pages fetched this way use a fixed reuse window and ignore `maxAge`, so use `firecrawl_scrape` when a live fetch is required. Returns source-type result groups and usage metadata. Authenticated responses can include an `id` for optional search feedback.firecrawl_crawlStart a multi-page crawl at a website URL, poll it to a terminal state, and return the final status and collected data. Scope can be bounded with include/exclude paths, depth, page limit, subdomain/external-link controls, sitemap handling, delay, and scrape options. Crawl results can be large; use conservative limits when full-site coverage is unnecessary. Webhooks and interactive scrape actions are unavailable in safe mode. Returns the crawl ID, status, and page data.firecrawl_check_crawl_statusRetrieve the current status, progress, and available results for an existing crawl ID. This only reads Firecrawl job state and does not start or modify the crawl.firecrawl_extractDeprecated compatibility entry point. Use firecrawl_scrape once per known URL with formats: ["json"] and jsonOptions containing the prompt and schema. Use firecrawl_search or firecrawl_agent before Scrape when URLs are not known.firecrawl_agentStart an asynchronous web research job from a prompt, optional seed URLs, and an optional JSON schema. Use this for a requested synthesis across multiple sources when the task can wait for asynchronous completion. The agent can search, navigate, read pages, and assemble a structured result. This call returns only a job ID, not the research result. Read the job with `firecrawl_agent_status` until it reaches `completed` or `failed`; research commonly takes several minutes. If the job cannot finish within the task's available time, `firecrawl_search` and `firecrawl_scrape` can gather evidence synchronously.firecrawl_agent_statusRetrieve progress or final results for a `firecrawl_agent` job ID. A `processing` response is non-terminal and does not contain the final research result. Check again after 15–30 seconds until the status is `completed` or `failed`; complex jobs can take several minutes. If the job cannot finish within the task's available time, use `firecrawl_search` and `firecrawl_scrape` to complete the requested output. Returns job status, progress information, and result data when completed.firecrawl_interactOpen or reuse a live browser session to navigate a page, click controls, fill fields, or run browser code. Provide either `url` or `scrapeId`, and either a natural-language `prompt` or executable `code`; code can run as Bash, Python, or Node with a bounded timeout. This acts on the live site, so actions such as form submission can create persistent external side effects. Returns execution output, stdout/stderr, exit status, and session viewing URLs.firecrawl_interact_stopStop the live interact session associated with a `scrapeId` and release its resources. Returns a success confirmation.firecrawl_parseParse one supported document into markdown, HTML, links, summary, targeted answers, or JSON matching a schema. Supported inputs include common HTML, PDF, Word, RTF, OpenDocument, and spreadsheet files; PDF parsing can be bounded with `pdfOptions.maxPages`. Local MCP reads `filePath` from the server filesystem. Hosted MCP uses two calls: first provide `filePath` to receive upload instructions, upload locally, then call again with the returned `uploadRef`; do not send both fields together. Remote web URLs belong in `firecrawl_scrape`. Set `redactPII` to request redaction of personally identifiable information in the returned content. `zeroDataRetention` requires an eligible authenticated account; omit it for anonymous keyless use. Returns upload instructions for hosted phase one or parsed document content for the final call.firecrawl_monitor_createCreate a recurring scrape, crawl, or search monitor that compares each check with its retained predecessor. The simple form accepts `page`/`pages` or `queries` plus a plain-language `goal`; the advanced `body` form controls targets, schedule, change-tracking formats, judging, retention, webhook, and notifications. In the simple form, a `goal` is required. If `queries` contains one or more non-empty values and is supplied with `page`/`pages`, `queries` create the search target and page targets are ignored. A monitor schedules future network checks and can send configured email or webhook notifications. Returns the created monitor.- +13 more on the listing page
Paxa Labs tools 14
speakSynthesize a short line with Paxa TTS and play it through this machine's speakers. Blocks until playback finishes. Waits for the currently playing audio but jumps ahead of queued long-form segments. For long content use queue_speech. Costs 10 credits per 1000 characters. Direction tags (paxa-tts-flash-v2, every voice): words in square brackets written into the text set the delivery from that point on, in English, Thai, or Chinese, e.g. [whispering], [speaking slowly, close to the microphone], [sad:0.5], or a blend [happy:0.7+sad:0.3]; [neutral] returns to the voice's own delivery. Sounds such as [laughs], [sighs], [gasps] play where written; [um] and [hmm] are spoken; <emph>...</emph> and <whisper>...</whisper> mark a span. Nothing in brackets is spoken, tag characters bill as text, and a tag the model cannot do is refused before any charge. On paxa-tts-flash-v1 only khanomchan and kaprao read tags, from a fixed emotion list.queue_speechRead long content aloud (stories, articles, books). Splits the text into segments, synthesizes ahead while playing, and returns immediately; segments play in order after anything already queued. Monitor and control with the control_playback tool. Costs 10 credits per 1000 characters. Direction tags (paxa-tts-flash-v2, every voice): words in square brackets written into the text set the delivery from that point on, in English, Thai, or Chinese, e.g. [whispering], [speaking slowly, close to the microphone], [sad:0.5], or a blend [happy:0.7+sad:0.3]; [neutral] returns to the voice's own delivery. Sounds such as [laughs], [sighs], [gasps] play where written; [um] and [hmm] are spoken; <emph>...</emph> and <whisper>...</whisper> mark a span. Nothing in brackets is spoken, tag characters bill as text, and a tag the model cannot do is refused before any charge. On paxa-tts-flash-v1 only khanomchan and kaprao read tags, from a fixed emotion list.control_playbackInspect and control the shared audio queue. status reports what is playing, what is queued, and any synthesis failures. pause and resume halt and continue playback (not supported on Windows). skip drops the current segment. clear stops playback and empties the queue.play_audioPlay a local audio file through this machine's speakers, for example a file produced earlier by text_to_speech. Blocks until playback finishes. Free (no API call).text_to_speechSynthesize speech with Paxa TTS and save it as an audio file without playing it: voiceovers, narration, audiobooks. Text beyond 5000 characters is split at paragraphs and sentences and the parts are joined into one file (needs ffmpeg). With subtitles set, an srt or vtt caption file that matches the voice word for word is written next to the audio. Costs 10 credits per 1000 characters, 12.5 with subtitles. Direction tags (paxa-tts-flash-v2, every voice): words in square brackets written into the text set the delivery from that point on, in English, Thai, or Chinese, e.g. [whispering], [speaking slowly, close to the microphone], [sad:0.5], or a blend [happy:0.7+sad:0.3]; [neutral] returns to the voice's own delivery. Sounds such as [laughs], [sighs], [gasps] play where written; [um] and [hmm] are spoken; <emph>...</emph> and <whisper>...</whisper> mark a span. Nothing in brackets is spoken, tag characters bill as text, and a tag the model cannot do is refused before any charge. On paxa-tts-flash-v1 only khanomchan and kaprao read tags, from a fixed emotion list.translate_to_thaiTranslate text from any language into Thai with Paxa Translate. Accepts a single string or up to 200 segments that share context. Costs 25 credits per 1000 text characters (minimum 2 credits); context and glossary characters bill at 8 per 1000.ocr_documentRun Paxa OCR on a local PDF, PNG, JPEG, or WebP file and return its content as GitHub-flavored Markdown (or structured blocks). Up to 50 pages and 10 MiB per file. Costs 6.5 credits per page.extract_fieldsExtract typed fields from a local PDF, PNG, JPEG, or WebP document (up to 20 pages and 10 MiB) with Paxa Document Extraction. You write a schema of fields; every value returned is text printed in the document, read as the field's type, or null with the reason. Nothing is inferred or looked up. Built for Thai documents (receipts, tax invoices, forms, IDs) and fine on English ones. Costs 13 credits per page for a schema of up to 50 leaf fields and 19.5 per page for 51 to 100; the page reading and the evidence spans cost nothing extra. A schema the API refuses costs nothing and names the field and reason. The schema parameter summarizes the dialect; https://paxalabs.com/docs/extraction has every type and key.transcribe_audioTranscribe a local recording or video of speech, Thai or any other language, code-switching included (mp3, wav, flac, ogg, m4a, aac, webm; or mp4, mov, mkv, avi and other video files, whose sound track is extracted locally with ffmpeg; up to 60 minutes and 25 MiB) with Paxa STT. The transcript comes back inline, so nothing needs to be read from disk afterwards; optionally it is also saved as txt, json (with word timings and segments), srt, or vtt, named after the recording. Existing files are never overwritten. Detects the language, handles code-switching, and can label speakers. Terms configured in PAXA_VOCABULARY or PAXA_VOCABULARY_FILE are pinned on every call. Costs 8.33 credits per minute of audio (0.1 minimum); subtitles and word timings cost nothing extra. Long recordings take minutes to process.listenRecord one spoken turn from this machine's microphone and return its transcript (Thai, English, or other languages, code-switching included). Paxa's realtime transcription detects when the user starts and stops talking, so the call returns as soon as the turn ends; the audio goes straight to the API and nothing is written to disk. Waits for any speech this server is playing to finish first. Use it after speak when you asked the user a question and want their spoken answer. Returns an empty transcript when nobody spoke within wait_seconds. Costs 12.5 credits per minute of audio sent, silence included (a few seconds of listening costs well under one credit). Needs a microphone recorder on this machine (ffmpeg or sox; parecord or arecord on Linux) and Node 22 or newer; the host app must have microphone permission.send_feedbackReport a wrong or poor output, an API problem, or a platform issue to the Paxa Labs team, tied to the request ids the other tools print ("Request id: ..."). A rating alone on at least one request id is a complete report. For a wrong output, add an example with the exact input, the output received, and the output expected. Free, no credits. Use it when the user says an output was wrong, or asks to report a problem; do not file reports the user did not ask for.list_voicesList the Paxa TTS voice roster: ids, names, gender, language, and character notes. Free.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Firecrawl MCP Server
{
"mcpServers": {
"firecrawl-firecrawl-mcp-server": {
"command": "npx",
"args": [
"-y",
"firecrawl-mcp"
],
"env": {
"FIRECRAWL_API_KEY": "YOUR_FIRECRAWL_API_KEY_HERE",
"HTTP_STREAMABLE_SERVER": "YOUR_HTTP_STREAMABLE_SERVER_HERE"
}
}
}
}
Paxa Labs
{
"mcpServers": {
"paxa-labs": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
],
"env": {
"PAXA_API_KEY": "YOUR_PAXA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Firecrawl MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. Paxa Labs belongs to Text-to-Speech and uses a local stdio subprocess. Pick Firecrawl MCP Server for search & data extraction work and Paxa Labs for text-to-speech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Firecrawl MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. Paxa Labs has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add firecrawl-firecrawl-mcp-server and paxa-labs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Firecrawl MCP Server has a quality signal of 90/100 (Excellent) with 14 views, 0 installs and 7,669 GitHub stars. Paxa Labs has 64/100 (Good) with 1 views, 0 installs and 10 GitHub stars.