portfolio-mcp
Reports which scanned projects have Docker deployment configuration as part of the deployment map.
Inspects git repository state for each project, including uncommitted work, missing remotes, stale repositories, and days since the last commit.
Detects GitHub presence and remotes for projects, enabling filtering and reporting by GitHub status.
Reports which scanned projects have Netlify deployment configuration as part of the deployment map.
Checks project dependencies against the npm registry using npm outdated and npm audit to find outdated packages and vulnerabilities.
Checks Python project dependencies against the PyPI registry using pip list --outdated to find outdated packages.
Reports which scanned projects have Railway deployment configuration as part of the deployment map.
Reports which scanned projects have Vercel deployment configuration as part of the deployment map.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@portfolio-mcp which of my projects are closest to earning money?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
portfolio-mcp
An MCP server that reads a directory full of projects and tells you what is in there: what each one is built with, whether it is in git, where it is deployed, what has gone stale, and which ones are closest to earning money.
It is read-only. It never writes to, moves, or deletes anything it scans.
Install
npx portfolio-mcp --root /path/to/your/projectsRegister it with Claude Code:
claude mcp add --scope user portfolio \
-e PORTFOLIO_ROOT=/path/to/your/projects \
-- npx -y portfolio-mcpOr in any client that reads mcpServers:
{
"mcpServers": {
"portfolio": {
"command": "npx",
"args": ["-y", "portfolio-mcp"],
"env": { "PORTFOLIO_ROOT": "/path/to/your/projects" }
}
}
}Related MCP server: Charlie Work
Configuration
Nothing is hardcoded. The scan root is resolved in this order:
--root <path>(or--root=<path>) on the command linethe
PORTFOLIO_ROOTenvironment variablethe process working directory
Variable | Default | Purpose |
| working directory | Directory holding the projects to scan |
| unset | Hostname or address that marks a self-hosted deployment. While unset, no |
| unset | Set to |
_archive, _backups, node_modules, .git, and dotted directories are skipped.
Tools
Inventory
Tool | What it does |
| Every project, filterable by stack, deployment status, platform, or GitHub presence |
| One project in depth: stack, dependencies, git, deployment, readiness, line count |
| Match on name, description, framework, dependency, or category |
Deployment
Tool | What it does |
| Everything grouped by platform: Vercel, Netlify, Railway, Docker, self-hosted, local-only |
| What deployment configuration one project carries, plus its git state |
| Uncommitted work, missing remotes, repos stale past 90 days, directories with no git at all |
Revenue
Tool | What it does |
| Scores one project 1 to 10 on auth, payments, landing page, deployment, API, README |
| Ranks every project, and separates the quick wins |
| Concrete next steps for one project, in priority order |
| Aggregate view: preferred frameworks, recurring stacks, strengths |
Maintenance
Tool | What it does |
|
|
| Projects sorted by days since the last commit |
What it touches
Being clear about this, because the server reads a directory you care about:
Reads only. No tool writes, moves, renames, or deletes a file.
Path containment. A project name is one directory entry. Separators,
.., absolute paths, drive letters, null bytes, and Windows device names are rejected, and the resolved path is then checked to be inside the configured root. There is no way to make it read a sibling directory.No shell. Every subprocess runs through
execFileSyncwith an argument array. Directory names are never concatenated into a command string.Subprocesses.
gitfor repository state, andnpm/piponly insideoutdated_deps.Network.
outdated_depsalone reaches the npm and PyPI registries, because that is whatnpm outdated,npm audit, andpip list --outdateddo. SetPORTFOLIO_OFFLINE=1and it refuses instead. Every other tool is local.No credentials. The server reads no tokens and sends nothing anywhere.
Scoring
revenue_scan and find_opportunities produce a 1 to 10 score from signals that
are cheap to detect: deployment configuration, an auth library, a payment library,
a landing page entry point, a README, a git remote, an API framework, then a
category multiplier. It is a triage heuristic for sorting a large directory, not a
valuation. Treat the ranking as "look at these first", not as a number that means
anything on its own.
Development
npm ci
npm run build
npm test # builds, then runs node --test
npm pack --dry-runLicense
MIT. See LICENSE.
Available Tools
12 toolscheck_healthB
Check if a deployed project is reachable. Pings known URLs for Vercel/Netlify projects.
Inputs: name (required).
deployment_mapA
Full deployment overview: what's on Vercel, VPS, Netlify, Railway, Docker, or local-only. Grouped by platform.
Inputs: no named parameters.
find_opportunitiesA
Rank ALL projects by revenue potential. Returns top opportunities with scores, what's ready, what's missing, effort estimate, and suggested pricing.
Inputs: no named parameters.
get_projectB
Get deep info about one project: stack, deps, git, deployment, revenue readiness, LOC.
Inputs: name (required).
git_overviewA
Scan all projects for git state: uncommitted changes, no remote, stale repos (90+ days without commits).
Inputs: no named parameters.
learn_patternsA
Scan ALL projects to learn the developer's patterns: preferred frameworks, common stacks, architecture choices, strengths. Claude uses this to build better.
Inputs: no named parameters.
list_projectsB
List all projects with optional filters. Returns name, stack, deployment, github, last modified.
Inputs: stack, status, platform, hasGithub.
outdated_depsB
Check a project for outdated npm/pip dependencies and security vulnerabilities.
Inputs: name (required).
revenue_scanA
Analyze a project's monetization readiness. Checks auth, payments, landing page, deployment, API, README. Returns score 1-10 and suggested path.
Inputs: name (required).
search_projectsA
Search across project names, READMEs, package descriptions, and dependency names.
Inputs: query (required).
stale_projectsB
Find projects with no git commits in 90+ days, sorted by staleness.
Inputs: no named parameters.
suggest_actionsB
For a project, generate concrete monetization steps in priority order.
Inputs: name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Several tools have overlapping boundaries. git_overview and stale_projects both identify projects with no commits in 90+ days, and deployment_map and list_projects both provide project lists with deployment information. This creates real ambiguity for an agent choosing between them.
Most tools follow a clear verb_noun pattern like list_projects, get_project, search_projects, check_health, and find_opportunities. The exceptions are deployment_map and git_overview, which are noun phrases rather than verb-led names, but the naming remains largely predictable and readable.
Twelve tools is within a reasonable range for a portfolio analysis server and each tool serves a distinct functional area overall. The count is slightly higher than necessary due to redundant stale-project logic and the partial overlap between deployment_map and list_projects, but it is not excessive.
The tool surface covers project discovery, deep inspection, deployment status, health checks, git hygiene, dependency vulnerabilities, revenue analysis, and opportunity ranking. Minor gaps exist, such as no bulk dependency scan across all projects and no direct action/deploy tools, but these are workable within the server's apparent analysis-focused purpose.
Maintenance
Related MCP Connectors
Check in on projects' uptime: monitors, servers, sites, incidents, status pages and notices.
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and security.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Read a repository's to-do list, production issues and calls, and pull request reports on evalship.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceScans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.5 npmMIT
- AlicenseAqualityCmaintenanceScans a repository for maintenance toil (flaky tests, expiring certificates, TODO rot, dead flags, etc.) and returns a prioritized queue with a credit ledger to track who cleared what.71MIT
- AlicenseNot gradedqualityDmaintenanceScans repositories to produce a readiness score and actionable fixes across positioning, tryability, community, MCP, and monetization, plus generates launch assets and sponsor-tier ideas.5 npmMIT
- AlicenseBqualityCmaintenanceScores local git repositories for README substance, license, package description, TypeScript config, tests, and GitHub Actions, providing a numbered hygiene report.2MIT