BeauticsLab vs Codegraphcontext

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

BeauticsLab logoBeauticsLabDeveloper Tools · Remote HTTP/SSESearch Korean cosmetics (Olive Young, Daiso, Naver, Coupang) with EWG ingredient analysis.37FairAuth: not declaredCodegraphcontext logoCodegraphcontextDeveloper Tools · Local subprocess (stdio)An MCP server that indexes local code into a graph database to provide context to AI assistants with a graphical code visualizations for humans.59GoodAuth: no auth required

Verdict: choose BeauticsLab for developer tools work over a hosted endpoint; choose Codegraphcontext for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

BeauticsLab logoChoose BeauticsLab when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
Explore BeauticsLab

Codegraphcontext logoChoose Codegraphcontext when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Codegraphcontext

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBeauticsLab logoBeauticsLabCodegraphcontext logoCodegraphcontext
CategoryDeveloper ToolsDeveloper Tools
Quality signal37/100 · Fair59/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars04,346
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

BeauticsLab tools

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

Codegraphcontext tools

No tool names declared yet. Check the project README from 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.

BeauticsLab

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "beauticslab": {
      "url": "https://mcp.beauticslab.com/mcp"
    }
  }
}

Codegraphcontext

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shashankss1205-codegraphcontext": {
      "command": "uvx",
      "args": [
        "kuzu"
      ]
    }
  }
}

Frequently asked questions

BeauticsLab is categorized under Developer Tools and uses a remote HTTP/SSE transport. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick BeauticsLab for developer tools work and Codegraphcontext 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.

BeauticsLab has no declared pricing — check the project's own site. Codegraphcontext 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 beauticslab and shashankss1205-codegraphcontext as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, BeauticsLab has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Codegraphcontext has 59/100 (Good) with 5 views, 0 installs and 4,346 GitHub stars.