# Winquill Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Winquill

Find public sector contract opportunities and manage bids across the UK, US, Canada and EU.

- Record: https://musedirectory.ai/connector/winquill
- Category: Shopping & Commerce
- Developer: Eshmere (https://winquill.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 240ms, checked 2026-10-29T11:45:58Z
- Endpoint: https://mcp.tenda.eshmere.ai/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T01:16:44Z)
- Source: Found in the official MCP Registry (ai.eshmere/tenda) https://registry.modelcontextprotocol.io/v0/servers?search=ai.eshmere%2Ftenda

Searches open tenders, frameworks and contract awards from government buyers, councils, NHS, schools and universities. Helps assess bid fit, check readiness requirements, draft bid responses and track pipeline status across multiple jurisdictions.

Example request: "Find all open cleaning contracts from UK councils in the North West closing within 30 days that are suitable for small businesses."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Winquill to help me. It is a free service with an MCP server at https://mcp.tenda.eshmere.ai/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- search_tenders: Use this to find public sector contracts to bid for in the UK, Canada, the United States, Germany, France and the rest of the EU: open tenders, frameworks and upcoming notices from any public buyer. Searches the user's own countries unless they name one; get_coverage lists every 
- get_tender_details: Use this when the user asks about one tender, framework or standing offer, by notice ID, buyer reference or from earlier results: the deadline, the portal to submit through, lots, value, conditions, award criteria and what the buyer wants, in plain English. It also reads the comp
- search_contract_awards: Use this to find who won public contracts in the UK, Canada, the United States, Germany, France and the rest of the EU, what a buyer paid last time, and which contracts end soon and may be re-tendered. Searches the user's own countries unless they name one. Answers give the total
- assess_tender_fit: Use this when the user asks whether their business should bid for a public contract, or which open tenders suit them best. Compares the tender's conditions of participation (turnover, insurance levels, experience and certifications), location and lot sizes with the company's prof
- check_bid_readiness: Use this when the user wants to know what they're missing before bidding, for one tender or in general: registrations, certifications, insurance, policies and each country's own documents, such as Cyber Essentials in the UK, SAM.gov registration in the US or the DUME in France. A
- draft_bid_response: Use this when the user wants help writing part of a response to a public tender: a quality question answer, social value response, method statement, case study, company overview, cover letter or clarification question. Returns a drafting brief built from the tender's award criter
- review_bid_draft: Use this when the user has a draft answer for a public tender and wants it checked before submission, the way an evaluator would: word limit, every part of the question answered, specific evidence, firm commitments, no unfinished placeholders or empty superlatives, and what the s
- watch_tenders: Use this when the user wants alerts for new tenders or upcoming notices that match a search, or for changes to one tender they follow (clarifications, new deadlines, the award). Saves a watch and gives its watchId: matches show in get_tender_updates and, with notify, in the works
- list_watches: Use this when the user asks which Winquill watches they have, or to find the one to stop: each watch with its ID, what it watches for, its countries and whether it posts to Slack or Teams. Needs a Winquill account. Do not use for what the watches found (use get_tender_updates). E
- stop_watch: Use this when the user wants to stop one of their Winquill watches, by the watchId that watch_tenders or list_watches gave. It finds nothing new after that; what it already found still shows in get_tender_updates. Needs a Winquill account. Example: {"watch_id":"wch_abc123"}
- get_tender_updates: Use this when the user asks what's new from their Winquill watches: new matching tenders, pipeline notices, deadline changes, clarifications, cancellations and awards. Without since, it gives the updates not shown before and marks them seen. Agents that check on a schedule pass s
- add_tender_documents: Use this when the user shares text from a tender's documents, or wants Winquill to read the files the buyer published with the notice (read_published, signed in). Returns a checklist of everything the bid must include, each with its file, page and the buyer's own words, and the r
- save_company_profile: Use this when the user wants Winquill to remember their business for searches, fit and readiness checks and drafting. Fill in only company facts the user has told you, leaving out anything unsure and any personal details, and show the user what you'll save so they can confirm or 
- get_pipeline_status: Use this when the user asks how their team's bids are going, for a status report, or what is due: how many tenders are in each stage of their Winquill pipeline, which bids are running with their next step and due date, which tenders still need the bid or no-bid call, and which bi
- add_to_pipeline: Use this when the user wants to save a tender to their team's pipeline to consider bidding, e.g. "add this to our pipeline" or "let's track the Falkirk cleaning framework". Adds it in Watching, ready for the bid or no-bid call, and says which e-tendering portal the tender is run 
- record_portal_account: Use this when the user says whether their company has an account on the e-tendering portal a tender is run on, where suppliers get the tender pack and bid, often after Winquill asked as a tender joined the pipeline: "yes, we have an EU-Supply account" or "no, we're not on Atamis 
- record_bid_call: Use this when the user's team has decided whether to bid: records the bid or no-bid call, the team's answers to Winquill's five questions and the reason. A bid moves the tender to Bidding and plans a six-step sprint back from the deadline; a tender not in the pipeline is added fi
- update_bid_sprint: Use this when the user says a step of a bid their team is running is done, or not done after all: decode the pack, assign questions, draft answers, review and score, final checks or submit. Ticks it off with who did it and when, and says what is next and when it is due. Ticking s
- assign_task: Use this when the user gives work on a team bid to someone, or takes it on: "give the Bristol bid call to Sam". The work is the bid call while a tender waits in Watching or Qualifying, or a sprint step, the next one unless named. Says who has it and whether they heard in Slack. W
- move_in_pipeline: Use this when the user wants to change where a tender stands in their team's Winquill pipeline: to Qualifying while they look into it, back to Watching, to Submitted, or to Won or Lost when the buyer announces the result. Moving to Bidding or No bid takes the bid or no-bid call (
- remove_from_pipeline: Use this when the user wants a tender taken off their team's Winquill pipeline, for good or until a change brings it back: "remove it until it gets a value". It deletes the tender's bid call, sprint and the files the team added; for one in Bidding, Submitted, Won or Lost the answ
- choose_alerts: Use this when the user wants to change which Slack and Teams channels get Winquill's alerts, or asks where they go: "stop the morning summary in Slack". Change only what the user asked for; with neither send nor stop it changes nothing and says where alerts go now. Owners and adm
- start_bid_draft: Use this when the user wants Winquill to write a whole bid for their team: it asks a few questions, drafts every answer from the company's evidence, then marks and revises them. Relay Winquill's questions as they are. A whole bid uses one of the month's full bids, so first call i
- continue_bid_draft: Use this to carry on a bid draft Winquill started with start_bid_draft: give it the buyer's questions it asked for, the team's answers to the questions Winquill asked, or the go-ahead to draft now with what it has (Winquill marks the gaps [TO CONFIRM]). Drafting starts once Winqu
- get_bid_draft: Use this when the user asks how a bid Winquill is drafting is going, or wants to read it: its progress in steps and answers written, each question with its word count and Winquill's mark out of 5, what's left for the team to confirm, and the check of the whole bid. Give question 
- rewrite_bid_answer: Use this when the user wants Winquill to rewrite one answer in a bid it drafted, e.g. "make Q3 shorter" or "use the Glasgow contract as the example in 2.1". Winquill rewrites it in the background, marks it again and says when it's done. A bid's first ten rewrites are included; af
- add_winning_bid: Use this when the user shares a bid their company won, for Winquill to learn from, e.g. after Winquill offers to learn from winning bids. Winquill keeps it in the workspace's Library and learns what worked in it (structure, tone, the evidence it uses) for the bids it drafts. Pass
- list_automations: Use this when the user asks what Winquill does on its own for their team: the workspace's automations, each with its rules as sentences, whether it's on and what it last did, and the ones Winquill suggests. Needs a Winquill account and workspace. Not for making one (use add_autom
- get_automation_library: Use this when the user wants to know which automations Winquill can run for them, before making one with add_automation. Returns each one in Winquill's library, what it does and whether the workspace has it already. Needs a Winquill account and workspace.
- add_automation: Use this when the user wants Winquill to do something on its own, again and again: add strong fits to the pipeline, remind people of sprint steps, check a bid before it closes, say what a buyer changed, or send a morning shortlist or a report. Makes one from the library, saved of
- turn_on_automation: Use this only after you have read an automation's rules back to the user in plain words and they said yes to turning it on. From then on it runs as the user, outside quiet hours, and acts on the team's pipeline as its rules say. Automations never submit a bid, send anything to a 
- turn_off_automation: Use this when the user wants one of the workspace's automations to stop. It stops running and keeps its rules and history, so it can be turned on again. Needs a Winquill account; owners, admins and bid leads turn them off.
- get_automation_history: Use this when the user asks what Winquill's automations did lately: the last 10 things they did, newest first, for one automation or all of them. Needs a Winquill account and workspace.
- share_tender: Use this when the user wants to share a tender or send someone its link. Returns a link anyone can open without signing in: it shows what the public notice says, and chat apps preview it with the tender's name, value and closing date. Give the link as it is. Nothing about the use
- get_coverage: Use this to know where Winquill looks: the countries and sources it reads, how many open, upcoming and awarded notices each holds, and when each was last read. Use it before telling the user a tender isn't published anywhere Winquill reads, or to say how fresh results are. Not fo
- open_tenda: Opens Winquill's own app from ChatGPT's sidebar: Today, the team's board, Find and each tender, with the bid call. The app moves between its pages itself.
- open_bid_panel: Opens the team's live bids beside a chat: each bid's steps and questions, what scores, and a way to work on one in the chat.
- tenda_changes: Says when the team's work in a workspace last changed, for Winquill's app to keep its page up to date.
- search_mentions: Finds the team's tenders and people by name, for @ mentions in ChatGPT.
- get_tenda_settings: Use this when the user asks which Winquill workspace ChatGPT uses, or which countries' tenders it shows: returns Winquill's settings in ChatGPT, the workspace (for someone in more than one) and the workspace's countries. Needs a Winquill account. Do not use for the company profil

Screening checks:
- MCP handshake: pass (Answered in 991ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.tenda.eshmere.ai, tenda.eshmere.ai not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (33 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)