Server Everything vs Protein MCP Server

A side-by-side look at the Server Everything and Protein MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Server Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol73GreatAuth: no auth requiredProtein MCP Server logoProtein MCP ServerBiology & BioinformaticsFederated protein structure & function across experimental (PDB) and predicted (AlphaFold) models.49FairAuth: no auth required

Verdict: choose Server Everything for other tools and integrations work as a local process; choose Protein MCP Server for biology & bioinformatics. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Server Everything logoChoose 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.
Explore Server Everything

Protein MCP Server logoChoose Protein MCP Server when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • Its auth model fits you: No auth required.
  • You want tools like protein_search_structures, protein_get_structure, protein_find_similar.
Explore Protein MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecServer Everything logoServer EverythingProtein MCP Server logoProtein MCP Server
CategoryOther Tools and IntegrationsBiology & Bioinformatics
Quality signal73/100 · Great49/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars91,5476
Directory activity 10 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools167

Tools & capabilities

Server Everything tools 16

  • echoEchoes back the input string
  • get-annotated-messageDemonstrates how annotations can be used to provide metadata about content.
  • get-envReturns all environment variables, helpful for debugging MCP server configuration
  • get-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 resources
  • get-resource-referenceReturns a resource reference that can be used by MCP clients
  • get-structured-contentReturns structured content along with an output schema for client data validation
  • get-sumReturns the sum of two numbers
  • get-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

Protein MCP Server tools 7

  • protein_search_structuresSearch experimental and predicted structures by text, sequence, or organism/method/resolution, with optional facets
  • protein_get_structureFetch metadata and coordinate URLs for experimental, predicted, or best-available structures
  • protein_find_similarFind sequence homologs (RCSB mmseqs2) or fold homologs (Foldseek)
  • protein_track_ligandsResolve ligands to component IDs, find structures containing one, or map its binding site
  • protein_compare_structuresAlign structures with TM-align or jFATCAT, against a reference or all pairs
  • protein_analyze_collectionProfile the PDB as counts, histograms, timelines, and cross-tabs
  • protein_get_annotationsFetch UniProt features and variants plus InterPro domains with GO terms

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.

Server Everything

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

Protein MCP Server

No confirmed install command for Protein MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Protein MCP Server belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick Server Everything for other tools and integrations work and Protein MCP Server for biology & bioinformatics.

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. Protein MCP Server has no confirmed install command yet — follow its own setup instructions.

Server Everything is listed as free. Auth: no auth required. Protein MCP Server 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 modelcontextprotocol-server-everything and protein-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 10 views, 0 installs and 91,547 GitHub stars. Protein MCP Server has 49/100 (Fair) with 1 views, 0 installs and 6 GitHub stars.