Skip to main content
Glama
Desearch MCP Server

Desearch MCP Server

Official

Desearch MCP Server

npm version GitHub stars As seen on Open Source Alternatives

If Desearch is useful, a star helps others find it.

Remote: https://mcp.desearch.ai/mcp with header Authorization: Bearer <DESEARCH_API_KEY>.

Local: npx -y desearch-mcp-server@latest with env DESEARCH_API_KEY.

Get a key.

Find Desearch on

Related MCP server: grok-mcp-server

Demo

Prompt: Search the web for latest news on AI.

web-search takes query (required) and start (optional pagination offset: 0, 10, 20, ...).

{
    "name": "web-search",
    "arguments": {
        "query": "latest news on AI"
    }
}

Example output:

{
    "data": [
        {
            "title": "Example result",
            "link": "https://example.com/page",
            "snippet": "Short preview text."
        }
    ]
}

The tool returns that JSON as pretty-printed text: { "content": [{ "type": "text", "text": "<json above>" }] }.

AI search, X search and web search for AI agents, plus the Search API (ranked pages with the best-matching passage), page extraction, X data tools, public TikTok, Facebook, Instagram, YouTube (videos, transcripts, comments, channels), Reddit, and Threads data, People Search (find people and creators on X, YouTube, LinkedIn, and TikTok), and Company Search (find companies on the web, or enrich domains you have, with their public contacts and leaders). Bring your own Desearch API key. Version 0.10.0 exposes 39 tools.

Tools

The Desearch MCP server includes the following tools.

Lookup tools, including search and fetch, set readOnlyHint: true, destructiveHint: false, and openWorldHint: true. search-api, tiktok, facebook, instagram, youtube, reddit, threads, people-search-status, people-search-tasks, people-profiles, and people-search-export are lookups too. people-search starts a paid job billed to the user's Desearch balance, so readOnlyHint is false; it creates a new task and does not delete or overwrite anything, so destructiveHint is false. people-search-pause and people-search-resume change a task's state and undo each other, so readOnlyHint and destructiveHint are false and idempotentHint is true. Pausing loses no data (people found so far stay readable and the search keeps its progress) and changes no billing (nothing is charged or refunded; the reservation stays until the search ends), and resume continues from where the search stopped with no new charge. The caveat: the API cancels a search paused for more than 7 days, and a cancelled search cannot be resumed, so a pause is reversible only within those 7 days. people-search-cancel cannot be undone, so readOnlyHint is false and destructiveHint and idempotentHint are true. The Company Search tools follow the same rules: company-search and company-enrich start paid jobs (readOnlyHint: false, destructiveHint: false, idempotentHint: false), company-search-status and company-search-tasks are lookups, company-search-pause and company-search-resume set destructiveHint: false and idempotentHint: true (with the same 7-day caveat), and company-search-cancel sets destructiveHint: true and idempotentHint: true. openWorldHint is true on every tool because the call reaches a live external source.

  • AI Search (ai-search): Performs AI Twitter and web searches with relevant links and summary. tools uses short source ids (web, twitter, arxiv, wikipedia, hackernews, reddit). Older labels such as Web Search, ArXiv Search, Wikipedia Search, Hacker News Search, and Reddit Search are still accepted and sent as the short id. youtube is not accepted. Default is ["web", "twitter"].

  • X Search (x-search): Tweet search on X. Arguments: query (required), count (optional, default 20). Sort stays Top. Optional filters: user, start_date, end_date (YYYY-MM-DD), lang, verified, blue_verified, is_quote, is_video, is_image, min_retweets, min_replies, min_likes.

  • Search (search): Web search that returns { results: [{ id, title, url }] }. Argument: query (required). id is the result URL.

  • Fetch Page (fetch): Read a public page as text. Argument: id (required, an http or https URL from search).

  • Web Search (web-search): SERP-style web search. Arguments: query (required), start (optional pagination offset).

  • Search API (search-api): Ranked web pages, each with its title, URL, publication date when known, and the passage that best matches the query (POST /search). Arguments: query (required, 1–2000 characters), mode (optional, fast or balanced, API default balanced), count (optional, 10, 15, or 20), start_date and end_date (optional, YYYY-MM-DD), highlights (optional, default true), page_text (optional, default false; adds each page's full text). Returns results plus cost_usd, usage_count, service, and currency.

  • Web Links Search (web-links-search): Web link search. Arguments: prompt (required), tools (optional, only web, default ["web"]; Web Search is accepted and rewritten to web), count (optional, 10–200). The links/web API rejects other sources, so they are not in the enum.

  • Extract (extract): Read a public URL as text or HTML. Preferred over crawl. Arguments: url (required), format (optional, text, markdown or html), js (optional), wait (optional milliseconds), full_page (optional, text only: every visible section of the page instead of its main content). Errors carry an error_code: js_required (retry with js: true), blocked (the site refused or showed a bot check), page_not_found.

  • Web Crawl (web-crawl): Same arguments as extract, on the legacy /web/crawl route. The SDK marks webCrawl deprecated in favor of extract; this tool stays so that route remains reachable. Prefer extract for new integrations.

  • X Links Search (x-links-search): AI search for X post links. Arguments: prompt (required), count (optional, 10–200).

  • X Posts By URLs (x-posts-by-urls): Full posts for a list of URLs. Argument: urls (required).

  • X Post By ID (x-post-by-id): One post by ID. Argument: id (required).

  • X Posts By User (x-posts-by-user): Posts by a user. Arguments: user (required), query (optional), count (optional, 1–100).

  • X Post Retweeters (x-post-retweeters): Users who retweeted a post. Arguments: id (required), cursor (optional).

  • X User Posts (x-user-posts): A user's timeline. Arguments: username (required), cursor (optional).

  • X User Replies (x-user-replies): Posts and replies by a user. Arguments: user (required), count (optional, 1–100), query (optional).

  • X Post Replies (x-post-replies): Replies to a post. Arguments: post_id (required), count (optional, 1–100), query (optional).

  • X Trends (x-trends): Trending topics for a location. Arguments: woeid (required), count (optional, 30–100).

  • TikTok (tiktok): Public TikTok data. action (required) picks the route: search (query; optional count, sort, cursor), post (id), profile (username), profile_posts (username; optional count, cursor), comments (video_id; optional count, cursor), hashtag (tag; optional count, cursor), trending (optional region, count). See TikTok, Facebook, and Instagram.

  • Facebook (facebook): Public Facebook data. action (required): search (query; optional count, cursor) and hashtag (tag; optional count, cursor) return Meta Ad Library ads, not organic posts; post (id), profile (profile_id, a page or profile ID or public handle), profile_posts (profile_id; optional count, cursor), comments (post_id; optional count, cursor).

  • Instagram (instagram): Public Instagram data. action (required): search (query; optional count; profiles, one page, no cursor), media (id: shortcode, numeric ID, or URL), profile (username), profile_posts (username; optional count, cursor), comments (shortcode, the code in the post URL; optional count, cursor), hashtag (tag; optional count, cursor).

  • YouTube (youtube): Public YouTube data. action (required): search (query; optional type, upload_date, sort_by, duration, cursor; videos, Shorts, live streams, channels, and playlists, each with a type), video (id: video or Short ID or URL), transcript (video_id; optional language), comments (video_id; optional order, cursor), channel (handle, with or without @, or a UC... channel ID), channel_videos (handle; optional sort, cursor). See YouTube, Reddit, and Threads.

  • Reddit (reddit): Public Reddit data. action (required): search (query; optional sort, timeframe, cursor), subreddit (name, case-sensitive), subreddit_posts (name; optional sort, timeframe, cursor), post (id: post ID or URL), comments (post_id; optional cursor).

  • Threads (threads): Public Threads data. action (required): search (query; optional start_date, end_date), search_users (query), profile (username), profile_posts (username), post (id: post URL or shortcode). One page each; no cursor.

  • People Search (people-search): Start a paid job billed to the user's Desearch balance: a search for people who match a plain-language description. Arguments: platform (required: x, youtube, linkedin, or tiktok), query (required, 3–1000 characters), count (optional, 5–200, API default 25), min_score (optional, 0–100), exclude (optional handles), metadata (optional labels, below), idempotency_key (optional), and that platform's filters (below). Returns the task_id, status, and reserved_cost_usd (count times the platform's per-person price at the time of the call; prices at https://desearch.ai/pricing); the ended task carries final_cost_usd. Public data only: public X posts and profile fields, public YouTube channel pages plus the creator's own website for publicly listed contact details, public LinkedIn posts and profiles, and public TikTok videos and profiles. Contacts are only those the person lists publicly.

  • People Search Status (people-search-status): A task's status, progress, and cost, plus a page of the people found so far. Arguments: task_id (required), cursor (optional, next_cursor from the previous call), limit (optional, 1–100, default 25), include_people (optional, default true). Free; it reads a search you already started (people come from public profiles and posts).

  • Pause People Search (people-search-pause): Pause a task. A queued search pauses at once; a running one finishes its current batch first. No data is lost and billing does not change; people-search-resume continues where it stopped with no new charge. A search paused for more than 7 days is cancelled by the API and can no longer be resumed. Argument: task_id (required). Free.

  • Resume People Search (people-search-resume): Resume a paused task from where it stopped, with no new charge. Works only on a paused search within 7 days of pausing (409 otherwise). Argument: task_id (required). Free.

  • Cancel People Search (people-search-cancel): Stop a task for good. You pay only for the people it already delivered; the rest of the reservation is returned. Cannot be undone. Argument: task_id (required). Free.

  • List People Search Tasks (people-search-tasks): Your searches, newest first. Arguments: platform (optional), status (optional list, for example ["running", "paused"]), limit (optional, 1–100), cursor (optional), metadata (optional, up to 3 labels a task must have, for example {"campaign": "q4-outbound"}). Free; lists tasks, not the people they found.

  • List People Found (people-profiles): Everyone your own searches found on one platform, one entry per person, with the search that found them. Runs no new search and queries no outside source. Arguments: platform (required), q (optional text in name, handle, bio, or location), sort (optional: score, recent, or audience), limit (optional, 1–200, default 25), cursor (optional), and the filters has (channels every person must have: email, website, x, linkedin, instagram, youtube, tiktok), min_audience, max_audience, min_score, location, verified. Free.

  • Export People Found (people-search-export): The people your searches found as CSV or JSON Lines text. Pass task_id to export one search, or platform (without task_id) to export everyone found on that platform, with the same q, sort, and filters as people-profiles. Arguments: task_id or platform, format (optional, csv or jsonl, default csv), has, min_audience, max_audience, min_score, location, verified, q and sort (platform export only), max_rows (optional, 1–1000, default 100). The reply is a note, then the file text cut at a row boundary to max_rows rows and 50,000 characters; the note says how many rows were cut. Free.

  • Company Search (company-search): Start a paid job billed to the user's Desearch balance: find companies on the web that match a plain-language description and collect each one's public contact data. Arguments: query (required, 3–1000 characters), count (optional, 5–200, API default 25), min_score (optional, 0–100), exclude (optional domains or URLs, up to 1000), countries (optional ISO 3166-1 alpha-2 codes or names, up to 20), require (optional: email, phone, linkedin, leader, leader_email), roles (optional, below), infer_emails (optional, default true), verify_emails (optional, default true), metadata (optional labels, as on people-search), idempotency_key (optional), max_cost_usd (optional search budget in USD, more than 0 and up to 100; set it only with the user's agreement), continue_from (optional task_id of an ended Company Search, to find only new companies). countries and require are sent as the API's filters. Returns the task_id, status, and reserved_cost_usd (count times the Company Search per-company price at the time of the call, or the whole max_cost_usd; prices at https://desearch.ai/pricing); the ended task carries final_cost_usd. A query that names companies with their websites ("Restrict this search to Acme (acme.com.au) and Beta (beta.co.uk). Return only those.") checks only those domains. Public data only: each company's own website, public web search results, and public LinkedIn profiles of its leaders.

  • Company Enrich (company-enrich): Start a paid job billed to the user's Desearch balance: the same public contact data for companies you already know. Arguments: domains (required, 1–200 domains or URLs; reduced to the host without www., lowercased, deduplicated), roles, infer_emails, verify_emails, metadata, idempotency_key (all optional). One company per domain, with score: null. Reserves one company per domain sent at the Company Enrich per-company price; duplicates and companies it does not deliver are returned when the task ends.

  • Company Search Status (company-search-status): A Company Search or Company Enrich task's status, progress, and cost, plus a page of the companies delivered so far. Arguments: task_id (required), cursor (optional, next_cursor from the previous call), limit (optional, 1–100, default 10), include_companies (optional, default true). Free.

  • Pause Company Search (company-search-pause): Pause a task. No data is lost and billing does not change; company-search-resume continues where it stopped with no new charge. A task paused for more than 7 days is cancelled by the API. Argument: task_id (required). Free.

  • Resume Company Search (company-search-resume): Resume a paused task from where it stopped, with no new charge (409 when it is not paused). Argument: task_id (required). Free.

  • Cancel Company Search (company-search-cancel): Stop a task for good. You pay only for the companies it already delivered (a search with max_cost_usd: its search effort so far when that is more, up to the budget); the rest of the reservation is returned. Cannot be undone. Argument: task_id (required). Free.

  • List Company Search Tasks (company-search-tasks): Your Company Search and Company Enrich tasks, newest first. Arguments: type (optional, search or enrich), status (optional list), limit (optional, 1–100), cursor (optional), metadata (optional, up to 3 labels, exact match). Free; People Search tasks are not listed here.

Cost of each call

Every tool result from a billed Desearch API call carries that call's cost in the result's _meta: cost_usd (USD) and usage_count (billed units), from the API's X-Desearch-Cost-Usd and X-Desearch-Usage-Count response headers. This holds for every result shape, including tools whose result is a list or plain text (x-search, x-posts-by-user, extract). The result content and structuredContent are unchanged. A free call reports cost_usd: 0; a failed call and a call with no cost headers carry no _meta cost. Example tools/call result:

{
  "content": [{ "type": "text", "text": "[ ... posts ... ]" }],
  "_meta": { "cost_usd": 0.0015, "usage_count": 10 }
}

The full SDK method → endpoint → MCP tool map is in docs/API_MCP_PARITY.md. Every public desearch-js 1.5 method is a tool. latestTweets was removed from the SDK (GET /twitter/latest in 1.0.1) and is not exposed. People Search, Company Search, the TikTok, Facebook, Instagram, YouTube, Reddit, and Threads routes, and POST /search are not in desearch-js 1.5; those tools call the routes directly (/desearch/people/*, /desearch/companies/*, and the rest), and the parity doc lists them too. The network stats routes (/network/stats) are not MCP tools.

TikTok, Facebook, and Instagram

tiktok, facebook, and instagram each take an action that picks one public route, plus that route's arguments. A missing argument, or one the action does not take, is refused before any request, with a message that lists what the action takes:

TikTok error: tiktok action "comments" needs video_id. comments takes: video_id (required), count, cursor. No request was sent.

post, profile, and media return the item as the API sends it. List actions return { "results": [...], "next_cursor": ..., "next": ... }. next_cursor is the API's x-desearch-next-cursor header; it is null on the last page. count (1–100) is a maximum: one page may hold fewer.

Prompt: show me the latest TikTok videos tagged #ai, then the next page.

{ "name": "tiktok", "arguments": { "action": "hashtag", "tag": "ai", "count": 2 } }
{
    "results": [
        { "id": "7620891413932166433", "url": "https://www.tiktok.com/@tiktok/video/7620891413932166433", "text": "caption text", "hashtags": ["ai"] }
    ],
    "next_cursor": "eyJ2IjoxLCJyb3V0ZSI6...",
    "next": "More results: call tiktok again with action \"hashtag\", the same tag, and cursor set to next_cursor, unchanged. A cursor works for 24 hours."
}
{ "name": "tiktok", "arguments": { "action": "hashtag", "tag": "ai", "count": 2, "cursor": "eyJ2IjoxLCJyb3V0ZSI6..." } }

The cursor is opaque: send it back unchanged, on the same action with the same target (query, username, profile_id, video_id, post_id, shortcode, or tag), within 24 hours. Any other value returns HTTP 422 and is not charged. TikTok trending and Instagram search return one page and take no cursor. Facebook search and hashtag read the Meta Ad Library (ads), not organic posts. Instagram comments takes the post shortcode (DeuOR-CjKE9 in https://www.instagram.com/p/DeuOR-CjKE9/); a numeric media ID returns 404. A leading @ on a username and # on a tag are removed.

YouTube, Reddit, and Threads

youtube, reddit, and threads work the same way: action picks one public route, and the action's arguments are checked before any request. Each call is billed per request, including an empty page; a 404, a 422, and a 5xx are not charged (prices at https://desearch.ai/pricing).

Tool

Actions that page (take cursor)

Single items

One page, no cursor

youtube

search, comments, channel_videos

video, transcript, channel

—

reddit

search, subreddit_posts, comments

subreddit, post

—

threads

—

profile, post

search, search_users, profile_posts (the latest posts only)

Paging is the same as on TikTok: a list action returns { "results": [...], "next_cursor": ..., "next": ... }, where next_cursor is the x-desearch-next-cursor response header. Send it back unchanged as cursor, on the same action with the same target, within 24 hours.

Prompt: find recent YouTube videos about bittensor, then read the transcript of the first one.

{ "name": "youtube", "arguments": { "action": "search", "query": "bittensor", "type": "videos", "upload_date": "this_month" } }
{ "name": "youtube", "arguments": { "action": "transcript", "video_id": "dQw4w9WgXcQ", "language": "en" } }

The transcript comes back as { "videoId", "language", "text", "segments": [{ "text", "startMs", "endMs", "startText" }] }; a video without captions returns 404 (not charged). video, transcript, and comments take a video ID or a full YouTube URL; reddit post and comments take a post ID (with or without t3_) or URL; threads post takes a post URL or shortcode. Reddit subreddit names are case-sensitive (AskReddit); a leading r/ is removed. Reddit sort values depend on the action: relevance, new, top, or comment_count for search, and best, hot, new, top, or rising for subreddit_posts (timeframe applies to top there). reddit comments returns a tree: top-level comments with the replies Reddit loaded and hasMoreReplies when there are more.

People Search finds X profiles, YouTube creators, LinkedIn members, or TikTok creators who match a plain-language description. Each person comes back with a fit score, one line on why they matched, their audience (followers, or subscribers on YouTube), location, and the public contacts and links the search found.

A search is a background task:

  1. people-search starts a paid job billed to the user's Desearch balance and returns a task_id at once. It is the only billed People Search call. It reserves count people at the platform's per-person price (reserved_cost_usd). When the search ends you pay only for the people it delivered (a per-search minimum applies when it finds anyone; a search that finds no one is free), and the rest of the reservation is returned. Send the same idempotency_key to retry a call without starting, or paying for, a second search.

  2. The search usually runs for 1 to 5 minutes. people-search-status returns its status, progress, cost, and the people found so far. People arrive while it runs: pass next_cursor back as cursor to get only the new ones. When done is true and has_more is false, you have everyone it found.

  3. people-search-pause, people-search-resume, and people-search-cancel pause, resume, or cancel it. A cancelled search bills only the people it already delivered.

People found stay readable for 30 days after a search ends. people-profiles lists them per platform across all your searches, with filters such as has: ["email"].

Search filters depend on the platform. A filter that does not apply is rejected before the billed call.

Platform

Filters

x

min_followers, max_followers, verified_only, countries, keywords, exclude_keywords

youtube

min_subscribers, max_subscribers, countries, require_contact, keywords, exclude_keywords

linkedin

min_followers, max_followers, countries, keywords, exclude_keywords

tiktok

min_followers, max_followers, require_contact, keywords, exclude_keywords

require_contact keeps only creators with a public email (on TikTok, in the bio). keywords and exclude_keywords take up to 20 words each.

metadata labels a search with your own keys, for example {"campaign": "q4-outbound", "workspace_id": "ws_42"}. A search takes up to 10 keys; keys are 1–40 characters of a-z, 0-9, _, . or -, and values are strings of up to 200 characters. A bad label is rejected before the billed call. The labels come back as metadata on the task, and people-search-tasks with metadata: {"campaign": "q4-outbound"} lists only the searches that carry them (up to 3 pairs, exact match). The search itself does not use them.

Prompt: find 10 TikTok skincare creators with a public email.

{
    "name": "people-search",
    "arguments": {
        "platform": "tiktok",
        "query": "Skincare creators who review skincare products",
        "count": 10,
        "require_contact": true
    }
}

Example output:

{
    "task_id": "3f1c2b9e-8d4a-4c1e-9b7a-2e5f6a7b8c9d",
    "platform": "tiktok",
    "status": "queued",
    "done": false,
    "query": "Skincare creators who review skincare products",
    "count": 10,
    "result_count": 0,
    "reserved_cost_usd": 0.5,
    "created_at": "2026-10-17T10:00:00Z",
    "cost_usd": 0.5,
    "currency": "USD",
    "next": "Searches usually take 1 to 5 minutes. Poll people-search-status with this task_id every 15 to 30 seconds; people appear while it runs."
}

Then poll with {"task_id": "3f1c2b9e-8d4a-4c1e-9b7a-2e5f6a7b8c9d"} on people-search-status:

{
    "task_id": "3f1c2b9e-8d4a-4c1e-9b7a-2e5f6a7b8c9d",
    "platform": "tiktok",
    "status": "running",
    "stage": "processing",
    "done": false,
    "query": "Skincare creators who review skincare products",
    "count": 10,
    "result_count": 4,
    "progress": { "round": 1, "candidates_processed": 40, "qualified": 4 },
    "reserved_cost_usd": 0.5,
    "created_at": "2026-10-17T10:00:00Z",
    "people": [
        {
            "id": "tiktok:example_creator",
            "platform": "tiktok",
            "handle": "example_creator",
            "name": "Example Creator",
            "url": "https://www.tiktok.com/@example_creator",
            "audience": 48200,
            "location": "United States",
            "score": 88,
            "why": "Reviews sunscreens and moisturizers every week.",
            "contacts": [{ "type": "email", "value": "creator@example.com" }],
            "links": [{ "type": "instagram", "url": "https://instagram.com/example_creator" }],
            "evidence_url": "https://www.tiktok.com/@example_creator/video/1"
        }
    ],
    "next_cursor": "4",
    "has_more": false,
    "next": "Still searching. Wait 15 to 30 seconds, then call people-search-status again with cursor \"4\" to get only the people found since this call."
}

The output above is shortened to one person. people-search-export returns the same people as CSV or JSON Lines text (GET /desearch/people/tasks/{task_id}/export), cut to max_rows rows (default 100) and 50,000 characters, with a note first that says how many rows were cut:

CSV export of task 3f1c2b9e-8d4a-4c1e-9b7a-2e5f6a7b8c9d: 250 rows. Showing the first 100 rows; 150 rows were cut by max_rows 100. For the whole file, call GET https://api.desearch.ai/desearch/people/tasks/3f1c2b9e-8d4a-4c1e-9b7a-2e5f6a7b8c9d/export?format=csv (plus the same filters) with your API key, or page through people with people-search-status or people-profiles.

When the search has ended, the task also says why and how complete it is, and each person says what their own profile confirms (0.3.2 and later):

{
    "status": "completed",
    "done": true,
    "completion_reason": "cost_limit",
    "coverage_limited": true,
    "warnings": [
        { "code": "partial_enrichment", "platform": "linkedin", "attempted": 20, "failed": 7, "by_reason": { "not_found": 7 } }
    ],
    "people": [
        {
            "handle": "example_engineer",
            "score": 74,
            "fully_verified": false,
            "unverified_criteria": ["Profile fit: Software Engineer based in Georgia (unknown)"],
            "enrichment": "failed",
            "enrichment_error": "not_found"
        }
    ],
    "next": "Finished early: a budget stopped it (cost_limit) before it found 10 people, so more people may match. You have every person it found."
}
  • completion_reason is one of count_reached, rounds_exhausted, no_candidates, zero_qualified, candidate_budget, cost_limit, time_limit, cancelled, or failed. It is left out while the search runs.

  • coverage_limited appears (as true) only when a budget stopped the search before it found count people. The status is still completed.

  • warnings lists what made part of the search less reliable. partial_enrichment: failed of attempted profiles could not be read after search, so those people were scored on the search hit and show enrichment: "failed" with enrichment_error.

  • fully_verified is true when every criterion is confirmed by the person's own profile or posts. unverified_criteria lists up to five that are not: (unknown), (not met), or a disqualifier that (applies). Both are information only: the person still qualified. Results scored before 2026-10-20 have neither.

Company Search finds companies on the web that match a plain-language description. Company Enrich starts from domains you send. Both collect each company's public contact data: emails, phones, social profiles, and its leaders (roles: CEO, founders, CTO, and CFO by default) with their LinkedIn profiles and emails. Every contact keeps the page it came from (source_url). Company Search also scores how well each company fits (0–100); Company Enrich has no score (score: null).

A task runs in the background, like a People Search:

  1. company-search or company-enrich starts a paid job billed to the user's Desearch balance and returns a task_id at once. Company Search reserves count companies at its per-company price, Company Enrich one company per domain sent at its own price (prices at https://desearch.ai/pricing). When the task ends you pay only for the companies it delivered (a minimum of 1 when it delivers any; a task that delivers none is free), and the rest of the reservation is returned. A company left out by min_score or require is not billed. Send the same idempotency_key to retry a call without starting, or paying for, a second task.

  2. company-search-status returns the task's status, progress, cost, and a page of companies. Each company goes through stages: profile (its homepage, and the fit score), contacts (its contact, about, team, and imprint pages), people (its leaders), email_patterns (inferred leader emails), and email_check (every email checked: valid, invalid, risky, or unknown). A company is delivered as soon as the stages the request needs have run, with enrichment.status: "partial", and later stages fill it in until it is complete. Pass next_cursor back as cursor to get only new companies; call without cursor to read every company in its latest version. stage: "enriching" means every company is delivered and only later stages are left. The next hint says which to do, and reminds you to read once more without cursor after the task ends if you read companies while it ran.

  3. company-search-pause, company-search-resume, and company-search-cancel pause, resume, or cancel it. company-search-tasks lists your tasks, filtered by type (search or enrich), status, or metadata.

A People Search task_id is a 404 on the company tools, and a company task_id is a 404 on the People Search tools. Companies stay readable for 30 days after a task ends.

Without a budget, a Company Search stops once it costs more than the companies it found pay for (completion_reason: "cost_limit", coverage_limited: true). max_cost_usd is the user's search budget in USD (more than 0, up to 100, and at least what count reserves; less is an HTTP 422 that gives the minimum). The whole budget is reserved, the search goes on until it delivers count or spends the budget, and its search effort is billed where the companies delivered do not cover it, up to the budget, even when it finds few companies or none. The unused part is returned. Agents must set it only when the user agreed to that amount. The task then shows max_cost_usd, and progress.effort_units once it ended.

continue_from takes the task_id of an ended Company Search: the new search leaves out every company that one delivered, held for review, or was told to exclude, so it finds only new ones. Send the same query and filters with the count still wanted. The API answers 409 while that task has not ended and 404 when it is not your Company Search. When a limit stopped a search before count, the next hint says how to continue it.

A query that names the only companies wanted, with their websites ("Restrict this search to Acme (acme.com.au) and Beta (beta.co.uk). Return only those."), checks only those domains against the rest of the description, with no web search: the task lists them as only_domains and ends with completion_reason: "all_domains_processed". Companies named without their websites do not restrict the search, and the task has warning scope_not_applied.

require keeps only companies that have all of the listed contacts: email, phone, linkedin (the company's LinkedIn page), leader (one of roles), leader_email (a leader with an email). A company that does not have them once the stage that can show them has run is not delivered and not billed. roles takes any of ceo, founder, cto, cfo, coo, cmo, president, owner, managing_director; a managing director (Geschäftsführer) counts as ceo when ceo is asked for. infer_emails: false skips the inferred leader emails and verify_emails: false skips the email checks.

Prompt: find 25 Series A fintech startups in Berlin with a leader's email.

{
    "name": "company-search",
    "arguments": {
        "query": "Series A fintech startups in Berlin building payment infrastructure",
        "count": 25,
        "countries": ["DE"],
        "require": ["leader_email"]
    }
}

Then poll with {"task_id": "5b33f3ee-168b-4780-9c8e-63a626781872"} on company-search-status:

{
    "task_id": "5b33f3ee-168b-4780-9c8e-63a626781872",
    "search_type": "company_search",
    "status": "running",
    "stage": "processing",
    "done": false,
    "query": "Series A fintech startups in Berlin building payment infrastructure",
    "count": 25,
    "result_count": 3,
    "progress": {
        "candidates_found": 140,
        "candidates_processed": 60,
        "qualified": 3,
        "filtered": { "not_a_company": 9, "below_min_score": 3 },
        "enrichment": { "published": 3, "complete": 1, "pending": 2, "failed": 0 },
        "email_checks": { "checked": 6, "valid": 3, "invalid": 1, "risky": 1, "unknown": 1 }
    },
    "reserved_cost_usd": 2.25,
    "created_at": "2026-10-28T10:00:00Z",
    "companies": [
        {
            "domain": "example.com",
            "name": "Example Payments",
            "url": "https://example.com/",
            "industry": "Fintech",
            "location": { "country": "DE", "city": "Berlin" },
            "description": "Payment infrastructure for marketplaces.",
            "score": 86,
            "why": "Berlin payments infrastructure startup, Series A in 2025.",
            "reasons": ["Payments infrastructure for marketplaces", "Based in Berlin"],
            "fully_verified": false,
            "unverified_criteria": ["Stage: Series A (unknown)"],
            "primary_email": {
                "value": "anna.schmidt@example.com",
                "type": "personal",
                "source": "inferred",
                "person": "Anna Schmidt",
                "confidence": "high",
                "pattern": "first.last",
                "verification": "valid"
            },
            "primary_contact": {
                "name": "Anna Schmidt",
                "title": "Co-founder & CEO",
                "email": "anna.schmidt@example.com",
                "linkedin_url": "https://www.linkedin.com/in/example-anna",
                "reason": "CEO, email inferred from the company's pattern and verified"
            },
            "contact_coverage": { "email": true, "phone": true, "linkedin": true, "leader": true, "leader_email": true },
            "emails": [
                {
                    "value": "hello@example.com",
                    "type": "general",
                    "source": "website",
                    "source_url": "https://example.com/impressum",
                    "verification": "valid"
                }
            ],
            "phones": [{ "value": "+493012345678", "type": "main", "source_url": "https://example.com/impressum" }],
            "socials": [
                {
                    "type": "linkedin",
                    "url": "https://www.linkedin.com/company/example-payments",
                    "source_url": "https://example.com/"
                }
            ],
            "leaders": [
                {
                    "name": "Anna Schmidt",
                    "title": "Co-founder & CEO",
                    "roles": ["ceo", "founder"],
                    "verified": true,
                    "linkedin_url": "https://www.linkedin.com/in/example-anna",
                    "emails": [
                        {
                            "value": "anna.schmidt@example.com",
                            "type": "personal",
                            "source": "inferred",
                            "confidence": "high",
                            "pattern": "first.last",
                            "verification": "valid"
                        }
                    ],
                    "evidence_url": "https://example.com/impressum"
                }
            ],
            "enrichment": {
                "status": "complete",
                "stages": { "profile": "done", "contacts": "done", "people": "done", "email_patterns": "done", "email_check": "done" }
            }
        }
    ],
    "next_cursor": "3",
    "has_more": false,
    "next": "Still running. Wait 15 to 30 seconds, then call company-search-status again with cursor \"3\" to get only the companies delivered since this call. Companies with enrichment status \"partial\" are still being filled in; when the task is done, call company-search-status without cursor to read every company in its latest version."
}

The output above is shortened to one company.

  • score is the fit score (0–100) for Company Search and null for Company Enrich. why and up to three reasons say why it matched; fully_verified and unverified_criteria say what the company's own pages confirm (information only: the company still qualified).

  • Each email has type (personal, leadership, sales, general, press, support, careers, legal, other), source (website, search, linkedin, inferred), source_url (none for inferred ones), and verification (valid, invalid, risky, unknown; left out until the email checks ran). Inferred emails carry confidence (high: the pattern was learned from this company's own addresses; low: a common pattern) and pattern.

  • primary_email is never a support, legal, careers, press, or other address, and an inferred one only when valid. primary_contact is the leader to reach first, with why.

  • Each leader has roles (from the request's roles), verified (a quote on the company's own site or their current LinkedIn position shows the role), and evidence_url (the page that shows it).

  • completion_reason adds all_domains_processed (Company Enrich, or a search restricted to the domains its query names, read every domain) to People Search's values. warnings keep their code and message, for example enrichment_time_limit when some companies were not fully enriched before the task's time limit.

CSV and JSON Lines downloads (GET /desearch/companies/tasks/{task_id}/export) are not MCP tools; call the API directly for a file.

Prerequisites 📋

Installation 🛠️

NPM Installation

The package name is desearch-mcp-server. The current version is on npm. See CHANGELOG.md for release notes. The stdio entry is the desearch-mcp-server bin (build/index.js), which requires DESEARCH_API_KEY.

npm install -g desearch-mcp-server

Or run it without a global install:

npx -y desearch-mcp-server@latest

Cursor or Claude can start that bin directly:

{
    "mcpServers": {
        "desearch": {
            "command": "npx",
            "args": ["-y", "desearch-mcp-server@latest"],
            "env": {
                "DESEARCH_API_KEY": "your-api-key"
            }
        }
    }
}

command: "desearch-mcp-server" (no args) is the same entry after the global install above.

Gemini CLI

Install the extension from this repository. Gemini CLI asks for your Desearch API key (stored as a sensitive setting) and connects to the hosted server https://mcp.desearch.ai/mcp:

gemini extensions install https://github.com/Desearch-ai/mcp-desearch

To change the key later, run gemini extensions config desearch. AI agents such as Cline can follow llms-install.md to set up the server.

Using Smithery

To install the Desearch MCP server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install desearch/desearch --client claude

Or for Cursor IDE:

npx -y @smithery/cli install desearch/desearch --client cursor

Windsurf

Windsurf's Cascade agent reads MCP servers from mcp_config.json under the mcpServers key. Open it from the Cascade panel: click the ... (Actions) menu, then Open MCP config file. Windsurf builds use ~/.codeium/windsurf/mcp_config.json (on Windows, %USERPROFILE%\.codeium\windsurf\mcp_config.json). Newer builds may open ~/.config/devin/mcp_config.json instead (Windows: %APPDATA%\devin\mcp_config.json); edit whichever file that action opens.

Hosted server (no local install). Remote servers use serverUrl with headers:

{
    "mcpServers": {
        "desearch": {
            "serverUrl": "https://mcp.desearch.ai/mcp",
            "headers": {
                "Authorization": "Bearer your-api-key"
            }
        }
    }
}

To keep the key out of the file, Windsurf can interpolate an environment variable: "Authorization": "Bearer ${env:DESEARCH_API_KEY}".

Local stdio alternative:

{
    "mcpServers": {
        "desearch": {
            "command": "npx",
            "args": ["-y", "desearch-mcp-server@latest"],
            "env": {
                "DESEARCH_API_KEY": "your-api-key"
            }
        }
    }
}

Save the file, then refresh the MCP servers list in Cascade.

Zed

Zed calls MCP servers context servers. Open your settings file with the zed: open settings file action (or use Settings → AI → MCP Servers → Add Server) and add a context_servers entry.

Hosted server:

{
    "context_servers": {
        "desearch": {
            "url": "https://mcp.desearch.ai/mcp",
            "headers": {
                "Authorization": "Bearer your-api-key"
            }
        }
    }
}

Local stdio alternative:

{
    "context_servers": {
        "desearch": {
            "command": "npx",
            "args": ["-y", "desearch-mcp-server@latest"],
            "env": {
                "DESEARCH_API_KEY": "your-api-key"
            }
        }
    }
}

The server is ready when the dot next to desearch in Settings → AI → MCP Servers turns green ("Server is active").

Configuration ⚙️

1. Configure Cursor IDE to run the Desearch MCP server

Open Cursor IDE, access command palette Cmd+Shift+P or Ctrl+Shift+P, and search for Open MCP Settings. Click on Add new global MCP server to open the mcp.json file.

2. Add the Desearch server configuration:

{
    "mcpServers": {
        "desearch": {
            "command": "desearch-mcp-server",
            "env": {
                "DESEARCH_API_KEY": "your-api-key"
            }
        }
    }
}

Replace your-api-key with your actual Desearch API key from console.desearch.ai/api-keys.

3. Restart Cursor IDE

For the changes to take effect:

  1. Completely quit Cursor IDE

  2. Start Cursor IDE again

1. Configure Claude Desktop to run the Desearch MCP server

Open the Claude Desktop app and enable Developer Mode from the top-left menu bar.

Once enabled, open Settings (also from the top-left menu bar) and navigate to the Developer Option, where you'll find the Edit Config button. Clicking it will open the claude_desktop_config.json file, allowing you to make the necessary edits.

OR (if you want to open claude_desktop_config.json from terminal)

For macOS:

  1. Open your Claude Desktop config:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

For Windows:

  1. Open your Claude Desktop configuration:

code %APPDATA%\Claude\claude_desktop_config.json

2. Add the Desearch server configuration:

{
    "mcpServers": {
        "desearch": {
            "command": "desearch-mcp-server",
            "env": {
                "DESEARCH_API_KEY": "your-api-key"
            }
        }
    }
}

Replace your-api-key with your actual Desearch API key from console.desearch.ai/api-keys.

3. Restart Claude Desktop

For the changes to take effect:

  1. Completely quit Claude Desktop

  2. Start Claude Desktop again

  3. You can verify the server by checking status in Settings > Developer > desearch

Remote Streamable HTTP

The same server can run over MCP Streamable HTTP for a remote client. Local stdio (desearch-mcp-server, Smithery) is unchanged and still reads DESEARCH_API_KEY from the environment.

Remote requests do not use that environment variable. Discovery does not need a key: initialize, notifications/initialized, ping, tools/list, prompts/list, resources/list, and resources/templates/list return 200 so a marketplace scanner can read the tool list. tools/call and every other method still require the caller's own Desearch API key, the same key from console.desearch.ai/api-keys:

  • Authorization: Bearer <DESEARCH_API_KEY> (preferred)

  • x-api-key: <DESEARCH_API_KEY> (also accepted)

  • Authorization: Bearer <oauth access token> after the OAuth sign-in below

A bare Authorization: <DESEARCH_API_KEY> value is also accepted. The key is not read from the query string. There is no shared server secret. A protected call without a valid key or access token returns 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource/mcp. The hosted process forwards the per-request Desearch API key to the Desearch API only when a call needs it. An OAuth access token is opaque: the server looks up the key stored for that token and does not put the raw key in the token.

The MCP endpoint is POST /mcp. Responses are JSON (stateless Streamable HTTP). GET and DELETE on /mcp return 405 because the server does not keep a session or push server-to-client messages. GET /, GET /health, and GET /api/health are unauthenticated health checks.

Hosted endpoint

The public Streamable HTTP endpoint is https://mcp.desearch.ai/mcp. Listing the tools does not need a key. Send your Desearch API key on each tools/call using Authorization: Bearer <DESEARCH_API_KEY> (preferred). The x-api-key header is also accepted. Use the key from console.desearch.ai/api-keys. The server does not read a key from the query string. Remote requests do not use a process-level DESEARCH_API_KEY.

Cursor, or any remote MCP client:

{
    "mcpServers": {
        "desearch": {
            "url": "https://mcp.desearch.ai/mcp",
            "headers": {
                "Authorization": "Bearer your-api-key"
            }
        }
    }
}

OAuth sign-in

Clients that follow the MCP authorization spec (2025-06-18) can sign in instead of sending a key on every request. Discovery documents:

  • GET /.well-known/oauth-protected-resource

  • GET /.well-known/oauth-protected-resource/mcp

  • GET /.well-known/oauth-authorization-server

  • GET /.well-known/openid-configuration (same authorization server document)

POST /register is dynamic client registration. GET /authorize is the Desearch page where the user pastes an API key. POST /token exchanges the authorization code and rotates refresh tokens. PKCE S256 is required. Public clients use token_endpoint_auth_method none.

Allowed callback URLs:

  • https://claude.ai/api/mcp/auth_callback

  • https://claude.com/api/mcp/auth_callback

  • https://chatgpt.com/connector_platform_oauth_redirect

  • https://chatgpt.com/connector/oauth/{callback_id}

  • Loopback http://localhost, http://127.0.0.1, and http://[::1] on any port (host and path must match the registered callback)

The connector URL is https://mcp.desearch.ai/mcp. On the sign-in page, paste a key from console.desearch.ai/api-keys. Leave a client id blank when the client can register itself.

Environment variables for the host:

Variable

Required

Purpose

OAUTH_ISSUER

Production

Canonical origin with no trailing slash, for example https://mcp.desearch.ai. Required when NODE_ENV=production or VERCEL is set. The process refuses OAuth and bearer challenges if it is unset. The issuer is never taken from X-Forwarded-Host. Locally, the request URL is used.

OAUTH_RESOURCE

No

Canonical MCP URL. Default is {OAUTH_ISSUER}/mcp. Access tokens are rejected when their stored audience does not match this resource.

OAUTH_STORE

Production

memory (local default) or redis. Production (NODE_ENV=production or VERCEL) refuses to start unless this is redis.

REDIS_URL

When OAUTH_STORE=redis

Redis connection string (redis:// or rediss://).

OAUTH_ENCRYPTION_KEY

When OAUTH_STORE=redis

32-byte key, base64 or hex. Generate with openssl rand -base64 32. Encrypts stored API keys.

OAUTH_ACCESS_TTL_SEC

No

Access token lifetime. Default 3600. Range 60 to 86400.

OAUTH_REFRESH_TTL_SEC

No

Refresh token lifetime. Default 30 days. Range 300 to 90 days.

OAUTH_CODE_TTL_SEC

No

Authorization code lifetime. Default 300. Range 30 to 600.

OAUTH_CLIENT_TTL_SEC

No

Dynamic client lifetime. Default 90 days. Range 3600 to 5 years.

OAUTH_REGISTER_RATE_LIMIT

No

Registration attempts per IP per window. Default 10. Range 1 to 10000.

OAUTH_REGISTER_RATE_WINDOW_SEC

No

Registration rate-limit window in seconds. Default 3600 (1 hour). Range 1 to 86400.

OAUTH_AUTHORIZE_RATE_LIMIT

No

Sign-in key checks per IP per window. Default 20. Range 1 to 10000.

OAUTH_AUTHORIZE_RATE_WINDOW_SEC

No

Sign-in key-check window in seconds. Default 600 (10 minutes). Range 1 to 86400.

DESEARCH_API_BASE

No

Desearch API host. Default https://api.desearch.ai. Used by the key check and by the routes the server calls directly (People Search, Company Search, search-api, people-search-export, and the social tools), for example to test against a staging API. Tools built on desearch-js always call https://api.desearch.ai.

OAUTH_REQUIRE_AUTH_ON_INITIALIZE

No

Set to true to require a key or access token on initialize. Default is off, so keyless initialize stays public. tools/list stays public either way.

The key check calls GET /twitter/trends?woeid=1&count=1. A real key is authenticated and then rejected as invalid input (HTTP 422), so the check does not run a full trends query. Only 422 counts as a valid key. 401 and 403 reject the key. Any other status, including a 2xx, is a verification error and is not treated as valid.

POST /register allows 10 requests an hour per IP. The sign-in key check allows 20 requests every 10 minutes per IP. A request past the limit returns 429 with Retry-After. On Vercel the address is the first X-Forwarded-For hop. The sign-in page uses Referrer-Policy: same-origin and posts response_type=code with the other authorize fields. The form accepts a same-origin Origin or Referer, and accepts Sec-Fetch-Site: same-origin when Origin is missing or null. It rejects Sec-Fetch-Site cross-site and same-site, a foreign Origin, and a POST that has no origin signal.

Use with Claude (custom connector)

Desearch is not in the Claude Connectors Directory yet. You can add the hosted server as a custom connector with your Desearch API key, or with OAuth sign-in.

Sources: Custom remote MCP connectors and connector authentication. Request-header authentication is a beta feature in Claude.

Claude.ai / Claude Desktop (organization admin)

  1. Open Organization settings > Connectors.

  2. Select Add, then Custom. If asked for the connector type, choose Web.

  3. Server URL: https://mcp.desearch.ai/mcp

  4. Sign-in option: No sign-in.

  5. Under Request headers, add Authorization with Bearer <DESEARCH_API_KEY> as the value, replacing <DESEARCH_API_KEY> with your Desearch API key.

  6. Select Add.

The header value is stored once and shared by everyone in the organization who uses the connector.

OAuth alternative: choose sign-in instead of a request header, leave the OAuth client id empty so the client can register itself, and paste a Desearch API key on the Desearch page. The callback URL for hosted Claude apps is https://claude.ai/api/mcp/auth_callback. Claude Code uses a loopback callback, which this server accepts on any port.

Claude Code

claude mcp add --transport http desearch https://mcp.desearch.ai/mcp \
  --header "Authorization: Bearer your-api-key"

Run locally

npm install
npm run build
npm run start:http

This listens on 0.0.0.0:3000 (PORT and HOST override that). MCP_TRANSPORT=http is the same as --http.

curl -sS http://127.0.0.1:3000/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Authorization: Bearer your-api-key' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"smoke","version":"0.0.1"}}}'

Cursor (or any remote MCP client):

{
    "mcpServers": {
        "desearch": {
            "url": "http://127.0.0.1:3000/mcp",
            "headers": {
                "Authorization": "Bearer your-api-key"
            }
        }
    }
}

The image default is stdio MCP (node build/index.js). Registries such as Glama start the container and speak MCP on stdin/stdout, so the image does not pass --http unless you override it. Stdio requires DESEARCH_API_KEY. Smithery does not use this image command; smithery.yaml starts node build/index.js and injects DESEARCH_API_KEY itself.

Streamable HTTP is an override. Replace the command with --http, or set MCP_TRANSPORT=http and keep the default command. The image still exposes port 3000 for that mode.

docker build -t desearch-mcp .
# stdio (image default)
docker run --rm -e DESEARCH_API_KEY=your-api-key -i desearch-mcp
# Streamable HTTP
docker run --rm -p 3000:3000 desearch-mcp node build/index.js --http
# same HTTP mode via env, without replacing the command
docker run --rm -e MCP_TRANSPORT=http -p 3000:3000 desearch-mcp

Deploy on Vercel

Vercel fits the MCP handler because each JSON-RPC call is one response. vercel.json builds the project, serves POST /mcp, and sets the function duration to 60 seconds. The same file rewrites the public OAuth paths to /api/*. The server accepts those rewritten paths and the public paths, and the metadata documents still advertise the public paths. Hobby plans cap function duration lower than that, so AI Search tool calls need a plan that allows at least 60 seconds. initialize and tools/list are short either way.

OAuth codes and tokens need shared storage. On Vercel set OAUTH_STORE=redis, REDIS_URL, OAUTH_ENCRYPTION_KEY, and OAUTH_ISSUER=https://mcp.desearch.ai. The server refuses OAuth when OAUTH_ISSUER is unset or OAUTH_STORE is not redis, because Vercel sets VERCEL on every function. OAUTH_REQUIRE_AUTH_ON_INITIALIZE=true is optional. Leave it unset unless a client treats public initialize as a reason to skip sign-in.

No server-side Desearch API key is required in the Vercel project. After deploy, the endpoint is:

https://<project>.vercel.app/mcp

https://mcp.desearch.ai/mcp is the public hostname. This repo does not create DNS records. Clients send Authorization: Bearer <DESEARCH_API_KEY> (preferred). The x-api-key header is also accepted.

The same node build/index.js --http process is the fallback if you would rather run a long-lived Node host instead of Vercel. The Docker image defaults to stdio; pass --http or set MCP_TRANSPORT=http to serve Streamable HTTP from it.

OpenAI Apps domain verification

GET https://mcp.desearch.ai/.well-known/openai-apps-challenge serves the exact domain verification token as plain text, with no trailing newline and Cache-Control: no-store. It requires no authentication. HEAD returns the same headers with no body.

The public token from the OpenAI Apps portal (Verify Domain) is set in the OPENAI_APPS_CHALLENGE_TOKEN constant in openai-apps-challenge.ts. Set the OPENAI_APPS_CHALLENGE_TOKEN environment variable in Vercel and redeploy to override it. Environment values are trimmed; unset, empty, whitespace-only or REPLACE_WITH_OPENAI_APPS_CHALLENGE_TOKEN values fall back to the source token.

Troubleshooting 🔧

Common Issues

  1. Server Not Found

    • Check Claude or Cursor Desktop configuration syntax

    • Ensure Node.js is installed

  2. API Key Issues

    • Confirm your DESEARCH_API_KEY is valid

    • Check the DESEARCH_API_KEY is correctly set in the Cursor or Claude Desktop config

    • Verify that there are no spaces around the API key

    • For the remote HTTP server, send Authorization: Bearer <DESEARCH_API_KEY> (preferred); x-api-key is also accepted. A hosted DESEARCH_API_KEY environment variable is not used for those requests.

  3. Connection Issues

    • Restart Claude Desktop or Cursor IDE completely

    • Check Claude Desktop logs:

    # macOS
    tail -n 50 -f ~/Library/Logs/Claude/mcp*.log
    
    # Windows
    type "%APPDATA%\Claude\logs\mcp*.log"

Available Tools

22 tools
extractExtract Page ContentA
Read-only
Inspect

Extract a public URL and return its content as plain text or HTML using Desearch. Preferred over web-crawl for new integrations. API docs: https://www.desearch.ai/docs/api-reference/get-web-extract

Inputs: url (required), js, wait, format.

fetchFetch PageA
Read-only
Inspect

Read a public page as text. Pass a URL returned by search.

Inputs: id (required). Returns: id, url, text, title, +1 more

people-profilesList People FoundA
Read-only
Inspect

Everyone your People Searches found on one platform, one entry per person: their best-scoring result and the search that found them (found_by). Free; it does not run a new search. Search by name, handle, bio, or location with q, filter by contact channels (has), audience, fit score, location, or verification, and sort by score, recent, or audience. People from searches that ended more than 30 days ago are left out.

Inputs: platform (required), q, has, sort, +7 more.

people-search-controlControl People SearchA
DestructiveIdempotent
Inspect

Pause, resume, or cancel a People Search task. Free. pause: a queued search pauses at once; a running one finishes its current batch first (status pausing, then paused). A search paused for more than 7 days is cancelled. resume: continues a paused search where it stopped, with no new charge. cancel: stops the search for good; you pay only for the people it already delivered and the rest of the reservation is returned. People found so far stay readable for 30 days.

Inputs: action (required), task_id (required).

people-search-statusGet People Search StatusA
Read-only
Inspect

Status, progress, and cost of one People Search task, plus a page of the people found so far: name, handle, url, platform, audience, location, fit score, why they matched, contacts, and links. Free. People arrive while the search runs: pass the returned next_cursor as cursor on the next call to get only the people found since then. When done is true and has_more is false you have everyone the search found. An ended task has completion_reason (why it stopped), coverage_limited: true when a budget stopped it before count (more people may match), and warnings such as partial_enrichment (some profiles could not be read, so those people were scored on the search hit; they show enrichment: failed). Each person has fully_verified (every criterion confirmed by their own profile or posts) and unverified_criteria (criteria that are unknown or not met, or a disqualifier that applies). These are information only: the person still qualified.

Inputs: task_id (required), limit, cursor, include_people.

people-search-tasksList People Search TasksA
Read-only
Inspect

Your People Search tasks, newest first, with status, counts, cost, why each ended search stopped (completion_reason, coverage_limited), and the metadata labels set on people-search. Free. Use it to find a task_id (filter by metadata to find the searches of one campaign), or to see which searches are still queued, running, or paused: a new search is refused while too many are active.

Inputs: limit, cursor, status, metadata, +1 more.

web-crawlCrawl Web Page (Legacy)A
Read-only
Inspect

Crawl a public URL and return its content as plain text or HTML on the legacy Desearch /web/crawl route. The SDK marks webCrawl deprecated in favor of extract; this tool stays for parity with that route. Prefer extract for new integrations. API docs: https://www.desearch.ai/docs/guide/apis/extract-api

Inputs: url (required), js, wait, format.

x-post-by-idGet X Post by IDB
Read-only
Inspect

Fetch a single X (Twitter) post by its ID.

Inputs: id (required).

x-post-repliesGet X Post RepliesB
Read-only
Inspect

Fetch replies to an X (Twitter) post, with an optional keyword query.

Inputs: post_id (required), count, query.

x-post-retweetersList X Post RetweetersA
Read-only
Inspect

List users who retweeted an X (Twitter) post. Pass cursor to page through more users.

Inputs: id (required), cursor.

x-posts-by-urlsGet X Posts by URLsB
Read-only
Inspect

Fetch full X (Twitter) posts for a list of post URLs.

Inputs: urls (required).

x-posts-by-userSearch X Posts by UserB
Read-only
Inspect

Search X (Twitter) posts by a specific user, with an optional keyword query.

Inputs: user (required), count, query.

x-user-postsGet X User TimelineC
Read-only
Inspect

Retrieve a user's X (Twitter) timeline posts by username. Pass cursor to page through more posts.

Inputs: username (required), cursor.

x-user-repliesGet X User RepliesB
Read-only
Inspect

Fetch posts and replies by an X (Twitter) user, with an optional keyword query.

Inputs: user (required), count, query.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 22 tools

    Disambiguation2/5

    The set contains many overlapping search and fetch tools: search, web-search, web-links-search, ai-search, x-search, x-links-search, fetch, extract, and web-crawl. Descriptions distinguish some cases, but an agent can easily choose the wrong web-search or page-reading tool.

    Naming Consistency3/5

    All names use kebab-case, which is good, but the patterns are mixed: x-post-by-id, x-posts-by-urls, x-user-posts, web-search, and bare search/fetch/extract do not follow one consistent prefix or verb_noun convention. Readable but not predictable.

    Tool Count3/5

    22 tools is heavy for this scope, largely because multiple search and extraction variants duplicate coverage. The People Search job lifecycle tools are justified, but the overall count feels over-expanded.

    Completeness4/5

    Coverage is broad across web search, X/Twitter posts, extraction, and the People Search lifecycle including status, control, tasks, and profiles. Minor gaps remain, such as no direct X user-profile lookup, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables searching X (formerly Twitter) using xAI's Responses API with support for filtering by handles, date ranges, and media understanding, returning structured results with citations.
      1
      18 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables real-time search of X.com (Twitter) posts, users, threads, and trends via xAI's Grok API, directly from Claude.
      5
      42 PyPI
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables real-time search of X (Twitter) posts, user timelines, and trends using either xAI's Responses API or the official X API v2.
      4
      -