QoutaMCP

QoutaMCP is a lightweight MCP server that inspects and analyzes project structures. It detects languages, frameworks, entry points, and dependencies to help you understand and manage complex codebases quickly.

How to use

To start using the MCP server with an MCP client, choose a local or remote connection method. Local methods run directly on your machine, giving full filesystem access for thorough inspection. Remote methods connect to a cloud-hosted MCP API for on-demand analysis with limited filesystem access.

How to install

Prerequisites: ensure you have Node.js and npm installed on your system. You can verify by running node -v and npm -v.

# Prerequisites check
node -v
npm -v

Option A: Install and run via NPX (recommended) to start instantly without a global install.

npx qoutamcp

Option B: Install globally with npm and run locally.

npm install -g qoutamcp
qoutamcp

Option C: Manual setup (clone repository, install dependencies, and start the server). Ensure you have git and npm available.

git clone https://github.com/QoutaID/qoutaMcp.git
cd qoutaMcp
npm install
npm start

Configuration and client setup

You can configure your MCP client to connect to the QoutaMCP server in different ways. Use one of the following methods to define how your client communicates with the server.

{
  "mcpServers": {
    "qoutamcp": {
      "command": "npx",
      "args": ["-y", "qoutamcp"]
    }
  }
}

Additional notes about remote access

If you prefer cloud-hosted usage, you can connect remotely using the SSE-based endpoint. Remote mode provides limited filesystem access, so for full project inspection you should use a local setup.

Remote API usage and available actions

You can perform actions such as detecting the project stack, inspecting the project snapshot, and listing key files through the API. Each action is invoked with the appropriate tool name and parameters, returning structured results to help you understand the project quickly.

Post-install usage tips

For best results, run the local npm/NPX variants when you need complete filesystem access and deeper analysis. Use the remote option when you want quick checks without mounting the entire filesystem.

Security and troubleshooting

Ensure your analysis runs in trusted environments. If you encounter errors, the server returns JSON-formatted error objects describing the issue, including an error code and message to guide you.

Notes on environment and paths

When using local stdio configurations, provide explicit commands and arguments as shown in the configuration examples. Do not omit required script names or paths.

Examples and common scenarios

Example 1: Start with NPX for quick analysis of a project without a global install.

npx qoutamcp

Example 2: Run a manual local server instance starting from a specific JavaScript entry.

node C:/path/to/qoutaMcp/index.js

Available tools

inspect_project

Generates a complete project snapshot including language, type, frameworks, entry points, structure, dependencies, and configuration files.

detect_stack

Performs lightweight detection of runtime, framework, databases, and frontend hints.

list_key_files

Lists key files categorized by entry, configuration, and documentation.