BidSkim vs India Tenders — MCP Server Comparison | AllMCPs
BidSkim vs India Tenders
A side-by-side look at the BidSkim and India Tenders MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BidSkim for search & data extraction work over a hosted endpoint; choose India Tenders for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BidSkim when
You need dedicated capabilities in the Search & Data Extraction domain.
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.
BidSkim is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. India Tenders belongs to Search & Data Extraction and uses a local stdio subprocess. Pick BidSkim for search & data extraction work and India Tenders for search & data extraction.
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.
BidSkim is listed as a paid service. Auth: oauth 2.0. India Tenders is listed as free. Auth: no auth required. 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 bidskim and india-tenders as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BidSkim has a quality signal of 72/100 (Great) with 5 views, 0 installs and 0 GitHub stars. India Tenders has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.