What is the key difference between Loopwise MCP Server and Admin?

Loopwise MCP Server belongs to the Developer Tools category with local stdio execution, while Admin belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install Loopwise MCP Server or Admin in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Loopwise MCP Server and Admin free or paid?

Loopwise MCP Server operates under a Free / Open Source model (No auth required). Admin operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Loopwise MCP Server lists 0 tools with 0 views and 0 GitHub stars. Admin lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Loopwise MCP Server and Admin together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Loopwise MCP Server or Admin in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Loopwise MCP Server and Admin free to use, or do they require API keys?

Loopwise MCP Server is listed under a Free / Open Source model with No auth required . Admin operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Loopwise MCP Server and Admin at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both loopwise-mcp-server and admin as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Loopwise MCP Server has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Admin holds a Quality Score of 46 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Loopwise MCP Server vs Admin

In-depth architectural comparison of the Loopwise MCP Server and Admin MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Loopwise MCP Server

Developer Tools · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Admin

Developer Tools · Remote HTTP/SSE

Quality: 46/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Loopwise MCP Server if you need specialized Developer Tools tools running via a local process. Choose Admin if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Loopwise MCP Server when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Loopwise MCP Server Details

Choose Admin when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Admin Details

Feature & Specification Comparison

Specification	L Loopwise MCP Server Developer Tools	A Admin Developer Tools
Summary	Read and manage courses, members, orders, events, posts, and settings for Loopwise-powered sites.	Restaurant management API for meni.ge owners: manage menus, locations, orders, and settings.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Loopwise MCP Server Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Admin Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Loopwise MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "loopwise-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "loopwise-mcp-server"
      ]
    }
  }
}

Admin Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "admin": {
      "url": "https://meni.ge/docs/mcp"
    }
  }
}

Frequently Asked Questions

Loopwise MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Admin belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Loopwise MCP Server when you need capabilities focused on developer tools and Admin when you require tools for developer tools.

More alternatives to Loopwise MCP Server More alternatives to Admin Developer Tools category hub Canonical compare URL