list_dealsLABSCO SUMMARY
Read-only on purpose, and the drafting still happens in your assistant.
The connector pulls deal context — compliance items, approved answers, question routing, competitor analysis — and never writes back, so pointing an agent at a live bid risks a wrong draft rather than a corrupted deal record. The pairing that makes it worth wiring up is the tender corpus sitting next to your own pipeline: find the public tenders closing soon, then draft a section grounded in the compliance items and answers your team has already approved instead of in invention. Two things to know before connecting: tender search works on a free account while personal deal data needs a personal token, and the tool and prompt list is discovered from the server, so it grows without a package update.
What it is
A small local connector that runs over stdio and proxies tool calls to the qlows API. It brings two things into a conversation: your own RFP and bid deals with their compliance items, question routing and intelligence, and the public tender corpus across 35 WTO-GPA countries. It stores nothing but your token, holds no backend logic of its own, and is read-only — an assistant can pull deal context and never write back.
What you get
- list_deals returns your RFP and bid deals as lightweight metadata, and get_deal_snapshot returns the whole picture: RFP summary, compliance, Q-routing and intelligence
- search_compliance_items runs keyword search across compliance items, and get_q_routing_state returns sections, questions, answers and assignment state
- get_intelligence_summary gives the AI summary with tailoring detection, list_questions the flat question list, and list_competitors the per-deal competitor analysis
- search_tenders searches the public corpus with full text and filters, search_tenders_for_my_company runs a personalised semantic search, and get_tender_detail returns one enriched record
- Three prompts appear as slash-commands — find_matching_tenders, draft_rfp_section and weekly_pipeline_review — each driving the read-only tools behind it
- The connector discovers tools and prompts live from the server, so new qlows capabilities appear without updating the package
- The tender tools work on a free account; the personal-data tools need a personal token
Requirements
Runs over stdio as npx -y @qlows/mcp. npx @qlows/mcp login opens the browser and takes the token back, npx @qlows/mcp test prints the available tools, and npx @qlows/mcp config prints the snippet for your client — or set QLOWS_TOKEN directly with a qlw_live_ token minted at app.qlows.com/mcp. QLOWS_BASE_URL overrides the API host, which defaults to https://app.qlows.com. MIT.
Setup effort
One command plus a key — npx @qlows/mcp login, then supply credentials
USE CASES
01
Finding tenders worth bidding on
Full-text search with filters across the public corpus, or a semantic search tuned to your own company, with the enriched record for anything promising.
02
Drafting a section that survives review
Pull the deal snapshot and the compliance items, and ground every claim in an answer your team already approved rather than in a plausible sentence.
03
Working out where a bid is stuck
Sections, questions, answers and who they are assigned to, so the gap is visible before the deadline rather than after it.
04
Reviewing the pipeline on a Monday
Your open deals with their metadata, and the intelligence summary — including tailoring detection — on the ones that are closest.
05
Understanding who else is bidding
The per-deal competitor analysis alongside the RFP summary, so the positioning decision is made against the field rather than in isolation.
10 tools
Listed in project docs. Your client may show a different list.
get_deal_snapshotsearch_compliance_itemsget_q_routing_stateget_intelligence_summarylist_questionslist_competitorssearch_tenderssearch_tenders_for_my_companyget_tender_detailBEFORE YOU INSTALL
What to know first
Tools you get
0 tools when we connected; the project documents 10.
Requires
- npx on PATH
- QLOWS_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @qlows/mcp loginMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"qlows": {
"command": "npx",
"args": [
"-y",
"@qlows/mcp"
],
"env": {
"QLOWS_TOKEN": "qlw_live_…"
}
}
}
}Cursor
CURSOR
cursor://anysphere.cursor-deeplink/mcp/install?name=qlows&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBxbG93cy9tY3AiXX0=VS Code
VS CODE
vscode:mcp/install?%7B%22name%22%3A%22qlows%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40qlows%2Fmcp%22%5D%7D
