Skip to main content
Glama

QoutaMCP

MCP server for inspecting and analyzing project structures. Detects languages, frameworks, entry points, and dependencies.

🌐 Live API: https://mcp.qouta.id

Installation

npx qoutamcp

Via NPM

npm install -g qoutamcp
qoutamcp

Manual

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

Related MCP server: Smart Code Reviewer

MCP Client Configuration

Method 1: Local (via NPX) - Full Filesystem Access

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

Method 2: Local (Manual Install)

{
  "mcpServers": {
    "qoutaMcp": {
      "command": "node",
      "args": ["C:/path/to/qoutaMcp/index.js"]
    }
  }
}

Method 3: Remote (via SSE) - Cloud Hosted

{
  "mcpServers": {
    "qoutaMcp": {
      "type": "sse",
      "url": "https://mcp.qouta.id/sse"
    }
  }
}

⚠️ Note: Remote mode has limited filesystem access (serverless). For full project inspection, use local mode.

Remote API Usage

Health Check

curl https://mcp.qouta.id/

Call Tools via REST API

# Detect Stack
curl -X POST https://mcp.qouta.id/ \
  -H "Content-Type: application/json" \
  -d '{"tool": "detect_stack", "params": {"path": "/tmp/myproject"}}'

# Inspect Project
curl -X POST https://mcp.qouta.id/ \
  -H "Content-Type: application/json" \
  -d '{"tool": "inspect_project", "params": {"path": "/tmp/myproject", "maxDepth": 3}}'

# List Key Files
curl -X POST https://mcp.qouta.id/ \
  -H "Content-Type: application/json" \
  -d '{"tool": "list_key_files", "params": {"path": "/tmp/myproject"}}'

Available Tools

1. inspect_project

Complete project snapshot - the primary tool for understanding a project.

Input:

{
  "path": "/path/to/project",
  "maxDepth": 3,
  "includeHidden": false
}

Output:

{
  "project": {
    "language": ["Node.js", "Python"],
    "type": "Web API",
    "confidence": 0.92
  },
  "frameworks": [
    { "name": "FastAPI", "confidence": 0.95 }
  ],
  "entryPoints": ["main.py"],
  "structureSummary": {
    "app": ["routes", "models"],
    "config": ["settings.py"]
  },
  "dependencies": {
    "primary": ["fastapi", "uvicorn"],
    "dev": ["pytest"]
  },
  "configFiles": [".env.example", "pyproject.toml"]
}

2. detect_stack

Lightweight and fast stack detection.

Input:

{
  "path": "/path/to/project"
}

Output:

{
  "runtime": ["Python"],
  "framework": ["FastAPI"],
  "databaseHints": ["PostgreSQL"],
  "frontend": null
}

3. list_key_files

List key files categorized by purpose.

Input:

{
  "path": "/path/to/project"
}

Output:

{
  "entry": ["main.py"],
  "config": ["pyproject.toml", ".env.example"],
  "docs": ["README.md"]
}

Supported Languages

Language

Signature Files

Frameworks Detected

Node.js/TS

package.json, tsconfig.json

React, Next.js, Express, Vite, NestJS

Python

requirements.txt, pyproject.toml

Flask, FastAPI, Django, Streamlit

PHP

composer.json

Laravel, Symfony

Go

go.mod

Gin, Fiber, Echo

Java

pom.xml, build.gradle

Spring Boot

Rust

Cargo.toml

Actix, Rocket, Axum

Error Handling

All errors are returned as JSON:

{
  "error": {
    "code": "PATH_NOT_FOUND",
    "message": "Specified path does not exist"
  }
}

Self-Hosting

Run as HTTP/SSE Server

# Local development
npm run server

# With custom port
PORT=8080 node server.js

Deploy to Railway

  1. Push to GitHub

  2. Connect Railway to your repo

  3. Set start command: node server.js

  4. Deploy!

Deploy to Render

  1. Create new Web Service

  2. Connect to GitHub repo

  3. Build command: npm install

  4. Start command: node server.js

Deploy to Vercel (Serverless)

Already configured! Just connect your GitHub repo to Vercel.

License

ISC

Available Tools

3 tools
detect_stackDetect StackA

Quickly detect the technology stack of a project. Faster and lighter than inspect_project, returns runtime, framework, database hints, and frontend info.

Inputs: path (required).

inspect_projectInspect ProjectA

Analyze a project directory and return a complete snapshot including detected languages, frameworks, entry points, structure summary, and dependencies. This is the primary tool for understanding a project.

Inputs: path (required), maxDepth, includeHidden.

list_key_filesList Key FilesC

List key files in a project, categorized by purpose: entry points, config files, and documentation.

Inputs: path (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools have mostly distinct purposes: detect_stack is for quick tech stack detection, inspect_project provides a comprehensive analysis, and list_key_files focuses on categorizing key files. However, there is some overlap between detect_stack and inspect_project, as both involve analyzing project components, which could cause mild confusion about when to use each.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (detect_stack, inspect_project, list_key_files), using snake_case throughout. The verbs (detect, inspect, list) are clear and descriptive, making the naming predictable and easy to understand.

    Tool Count4/5

    With 3 tools, the count is reasonable for a project analysis server, covering key aspects like tech detection, detailed inspection, and file listing. It is slightly lean but well-scoped, as each tool serves a distinct function without unnecessary bloat, though a few more tools might enhance coverage.

    Completeness3/5

    The toolset covers analysis and listing functions well, but there are notable gaps for a project management domain. For example, it lacks tools for modifying or updating projects (e.g., add_dependency, update_config), which could limit agent workflows. The surface is functional for inspection but incomplete for broader project operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Analyzes codebases to generate dependency graphs and architectural insights across multiple programming languages, helping developers understand code structure and validate against architectural rules.
      6
      49 npm
      20
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.
      5
      9 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and developers to analyze code for language-specific best practices and idiomatic patterns across programming languages, CI automation, and configuration formats.
      16
      2
      MIT