Outdooriq MCP vs Server Everything
A side-by-side look at the Outdooriq MCP and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Outdooriq MCP for environment & nature work; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Outdooriq MCP when
- You need dedicated capabilities in the Environment & Nature domain.
- You want tools like
search_lakes, get_lake_details, get_stocking_data.
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
echo, get-annotated-message, get-env.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Other Tools and Integrations |
| Quality signal | 39/100 · Fair | 73/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 91,512 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 10 | 16 |
| Full listing | View Outdooriq MCP | View Server Everything |
Tools & capabilities
Outdooriq MCP tools 10
search_lakesList of matching lakesget_lake_detailsCoords, acreage, depth, species, facilitiesget_stocking_dataRecent stocking eventsget_fishing_score0-100 score with bucket breakdownget_nearby_lakesLakes near GPS, sorted by scoreget_weather_for_lakeCurrent + 7-day forecast (Open-Meteo)get_top_lakesHighest-scoring lakesget_stocking_scheduleMost-recent matching events as a planning priorsearch_speciesActively-stocked speciesget_fishing_report_summaryNatural-language report
Server Everything tools 16
echoEchoes back the input stringget-annotated-messageDemonstrates how annotations can be used to provide metadata about content.get-envReturns all environment variables, helpful for debugging MCP server configurationget-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.get-resource-linksReturns up to ten resource links that reference different types of resourcesget-resource-referenceReturns a resource reference that can be used by MCP clientsget-structured-contentReturns structured content along with an output schema for client data validationget-sumReturns the sum of two numbersget-tiny-imageReturns a tiny MCP logo image.gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.- +4 more on the listing page
Ready-to-paste client configs
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.
Outdooriq MCP
No confirmed install command for Outdooriq MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Outdooriq MCP is categorized under Environment & Nature and uses an install path we have not confirmed yet. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Outdooriq MCP for environment & nature work and Server Everything for other tools and integrations.
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. Outdooriq MCP has no confirmed install command yet — follow its own setup instructions.
Outdooriq MCP has no declared pricing — check the project's own site. Server Everything 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 outdooriq-mcp and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Outdooriq MCP has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Server Everything has 73/100 (Great) with 9 views, 0 installs and 91,512 GitHub stars.