Domus vs Context7

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

D
DomusHome Automation · Remote HTTP/SSE
Homeowner's AI: view & update appliances, warranties, documents & maintenance for your home.39FairAuth: oauth 2.0
Context7 logoContext7Developer ToolsUp-to-date code documentation for LLMs and AI code editors.55GoodAuth: api key required

Verdict: choose Domus for home automation work over a hosted endpoint; choose Context7 for developer tools. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

D
Choose Domus when

  • You need dedicated capabilities in the Home Automation domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Domus

Context7 logoChoose Context7 when

  • You need dedicated capabilities in the Developer Tools domain.
  • Its auth model fits you: API key required.
  • You want tools like resolve-library-id, query-docs.
Explore Context7

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
D
Domus
Context7 logoContext7
CategoryHome AutomationDeveloper Tools
Quality signal39/100 · Fair55/100 · Good
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthOAuth 2.0API key required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—63,579
Directory activity 1 views 0 installs 0 upvotes 14 views 0 installs 0 upvotes
ToolsNot listed2

Tools & capabilities

Domus tools

No tool names declared yet. Check the project README from the listing page.

Context7 tools 2

  • resolve-library-idResolves a general library name into a Context7-compatible library ID.
  • query-docsRetrieves documentation for a library using a Context7-compatible library ID.

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.

Domus

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "domus": {
      "command": "npx",
      "args": [
        "-y",
        "domus"
      ]
    }
  }
}

Context7

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

Frequently asked questions

Domus is categorized under Home Automation and uses a remote HTTP/SSE transport. Context7 belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Domus for home automation work and Context7 for developer tools.

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

Domus has no declared pricing — check the project's own site. Auth: oauth 2.0. Context7 is listed as free. Auth: api key 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 domus and upstash-context7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Domus has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Context7 has 55/100 (Good) with 14 views, 0 installs and 63,579 GitHub stars.