EPC Tender Screening MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@EPC Tender Screening MCPScreen the current tender and generate a bid/no-bid memo."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
EPC Tender Screening MCP
An MCP-only server for evidence-based EPC tender screening.
This project lets MCP-compatible AI agents:
run a full
screen_tenderworkflow,extract tender requirements from uploaded tender text,
match requirements against a company profile,
generate compliance matrices,
produce bid/no-bid advisory memos,
search explicit public tender source URLs,
search local historical proposal examples for grounding.
The project is designed as a clean public MCP repository. It does not include private company documents, credentials, UI pages, or production tender archives.
Why This Exists
Tender teams spend significant time reading long procurement documents, checking eligibility, finding supporting evidence, and deciding whether to bid. This MCP server gives AI agents a structured tool layer for that workflow while keeping the final decision human-reviewed.
Related MCP server: Tri-Tender Pricing MCP
Tools
Tool | Purpose |
| Run the full screening workflow end to end |
| Save uploaded/extracted company profile text as local context |
| Save uploaded/extracted tender text as current tender |
| Allowlist public tender source URLs for discovery |
| Search explicit source URLs without crawling the whole internet |
| Show connected data sources and fallback state |
| Extract tender requirements |
| Match requirements against company capabilities |
| Generate requirement-level compliance rows |
| Generate advisory fit/risk scores and recommendation |
| Search local historical proposal examples |
Quick Start
npm install
npm run devOpen:
http://localhost:3000The root URL returns JSON metadata only. There is no UI.
The Streamable HTTP MCP endpoint is:
http://localhost:3000/api/mcpThe root URL returns JSON metadata only:
curl http://localhost:3000For local connector testing without auth:
MCP_REQUIRE_AUTH=false npm run devOn Windows PowerShell:
$env:MCP_REQUIRE_AUTH="false"
npm run devStdio MCP
npm run mcp:stdioExample Claude Desktop style config:
{
"mcpServers": {
"epc-tender-screening": {
"command": "npm",
"args": ["run", "mcp:stdio"],
"cwd": "/absolute/path/to/epc-tender-screening-mcp-showcase"
}
}
}Remote Connector Auth
The repo includes a demo OAuth shim for hosted connector experiments.
Set:
MCP_PUBLIC_BASE_URL=https://your-domain.example
MCP_API_KEY=replace-this-tokenConnector values:
MCP URL: https://your-domain.example/api/mcp
Authorization URL: https://your-domain.example/oauth/authorize
Token URL: https://your-domain.example/oauth/token
Client ID: epc-tender-demo-client
Client Secret: epc-tender-demo-secret
Scope: mcp tender:read tender:screenFor production, replace the demo OAuth shim with real OAuth and per-user authorization.
Demo token auth is disabled by default in production. For temporary hosted demos only, set:
MCP_ALLOW_DEMO_AUTH=true
MCP_DEMO_ACCESS_TOKEN=replace-this-demo-tokenDo not use the default demo token for a public deployment.
ChatGPT Upload Workflow
Upload company profile and tender files to ChatGPT, then ask:
Extract text from the uploaded company profile and tender files.
Call screen_tender with tender_text and company_profile_text.
Summarize the recommendation, red flags, missing documents, and next human actions.For one-shot analysis without saving:
Extract text from both uploaded files, then call generate_bid_no_bid_memo with tender_text and company_profile_text.Public Tender Discovery
This project does not crawl the open internet. It searches explicit sources only.
connect_tender_source_urls
search_public_tendersUse search_public_tenders for discovery leads only. Upload or connect the actual tender document before screening.
Data Files
Safe example files:
data/company-profile.example.json
data/sample-tender.md
data/historical-proposals.example.jsonPrivate local files are ignored by git:
data/company-profile.local.json
data/current-tender.local.md
data/tender-sources.local.jsonExample fallback is disabled by default. To demo with bundled example files:
MCP_ALLOW_EXAMPLE_FALLBACK=true npm run devOn Windows PowerShell:
$env:MCP_ALLOW_EXAMPLE_FALLBACK="true"
npm run devSafety
The bid/no-bid memo is advisory only. Every output should be reviewed by tender, finance, legal, HSE, and management owners before submission.
Do not use this project to automatically submit tenders or make binding commercial decisions.
Development
npm run lint
npm run build
npm run evalThe eval suite runs through the real MCP stdio transport and checks tool exposure, safe failure behavior, screening outputs, and evidence traces.
Docs
CI
GitHub Actions runs:
npm ci
npm run lint
npm run build
npm run evalLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Shiverion/epc-tender-screening-mcp-showcase'
If you have feedback or need assistance with the MCP directory API, please join our Discord server