tencentcloudbase/cloudbase-mcp

0

/ 100

Documentation95
Engineering59
Health83
TypeScript1,036MIT1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

CloudBase MCP - Connect CloudBase to your AI Agent. Go from AI prompt to live app.

Documentation

95

Contributing guide5pt89

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

59

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

Tests18pt35

Test files detected (mcp/src/auth.test.ts).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/build-zips.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

83

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 132
    Forks
  • 31
    Releaseslatest 4mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,036
    Watchers

Responsiveness

  • 12h
    Median issue response
  • <1h
    Median PR merge time
  • 28
    Open issues
Repository files40 root entries
  • .agents
  • .claude
  • .claude-plugin
  • .codebuddy
    Issue: Build artifacts or local files may be committed (.codebuddy/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/build-zips.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • .workbuddy
  • config
  • doc
  • docs
  • mcp
    Good: Test files detected (mcp/src/auth.test.ts).
    Good: Environment pinned via mcp/Dockerfile.
  • plugin
  • scripts
  • skills
  • specs
  • tests
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .versionrc
  • AGENTS.md
  • CHANGELOG.md
  • cloudbaserc.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • gemini-extension.json
  • glama.json
  • LICENSE
    Good: Licensed under MIT.
  • marketplace.json
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • README-EN.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README-ZH.md
  • README.md
  • renovate.json
  • tsconfig.json
  • vitest.config.js