gigbid-portfolio-mcp
A read-only MCP server that lets an AI assistant (Claude Desktop, Cursor, VS Code, or any MCP host) search a freelancer's portfolio and cite real evidence: case studies, repositories, client reviews, past proposals and the CV.
Use it to answer screening questions or write proposals where every claim points to something you actually did. It is the portfolio server from GigBid, a multi-agent freelancer copilot.
Install and run
pip install gigbid-portfolio-mcp
gigbid-portfolio-mcp # serves the bundled sample portfolio over stdio
Or without installing, with uv:
uvx gigbid-portfolio-mcp
Point it at your own portfolio:
PORTFOLIO_DIR=/path/to/my-portfolio gigbid-portfolio-mcp # PowerShell: $env:PORTFOLIO_DIR="C:\path"
Claude Desktop / Cursor / VS Code
Add to the host's MCP configuration (Claude Desktop: claude_desktop_config.json):
{
"mcpServers": {
"portfolio": {
"command": "uvx",
"args": ["gigbid-portfolio-mcp"],
"env": { "PORTFOLIO_DIR": "/path/to/my-portfolio" }
}
}
}
Leave out env to try it on the sample portfolio first.
What it offers
| Kind | Name | What it does |
|---|---|---|
| Tool | search_evidence(requirement, k, types, outcomes, since) |
Ranked evidence for one requirement, with type, project, skills, date, client industry and outcome |
| Tool | get_case_study(evidence_id) |
Full text of one evidence item |
| Tool | list_skills() |
Skills and how many evidence items back each one |
| Resource | portfolio://case/{id} |
A case study as Markdown |
| Resource | portfolio://proposal/{id} |
A past proposal with its outcome |
| Resource | portfolio://profile |
Headline, rate, skills |
| Prompt | Answer a screening question from my portfolio | Grounded answer that cites [evidence_id] |
| Prompt | Find my best proof for a job | Requirement → strongest evidence table, gaps marked |
All tools are read-only (readOnlyHint: true, idempotentHint: true); the server never writes anywhere.
Retrieval is BM25+ (keyword ranking): no model download, millisecond latency. In GigBid's evaluation it gave better end-to-end bid
decisions than hybrid dense retrieval, even though hybrid had higher recall.
Portfolio folder format
All parts are optional; use what you have.
my-portfolio/
├── cv.md
├── profile.json {"headline": "...", "hourly_rate": 40, "skills": ["Python", "..."]}
├── case_studies/
│ └── churn-model.md front matter, then the story (see below)
├── repos/
│ └── my-repo/ README.md and any source files
├── reviews.json [{"id": "...", "rating": 5, "project": "...", "text": "...", "date": "2026-01-31"}]
└── proposals.json [{"id": "...", "job_title": "...", "text": "...", "outcome": "replied", "job_skills": [...]}]
Case study front matter:
---
id: "me-case-01"
title: "Churn prediction for a telecom client"
project: "Churn model"
skills: ["Python", "scikit-learn"]
date: "2026-02-14"
client_industry: "telecom"
outcome: "delivered"
---
Problem, what you built, and the measured result.
Privacy
Everything stays on your machine: the server reads local files only and makes no network calls. The bundled sample portfolio is synthetic.
Development
pip install -e ".[test]"
pytest
License: MIT.
Metadata
Release files for gigbid-portfolio-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gigbid_portfolio_mcp-0.1.0.tar.gz | 18.5 kB | Without provenance | Details for gigbid_portfolio_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gigbid_portfolio_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for gigbid_portfolio_mcp-0.1.0-py3-none-any.whl |
Total release size: 51.9 kB
Release files / gigbid_portfolio_mcp-0.1.0.tar.gz
| Download URL | gigbid_portfolio_mcp-0.1.0.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4acb7cc12612e41c15ebc7b5c4918113632e53ecf09580a077de0500d0975012
|
|
BLAKE2b-256 checksum How to use checksums |
0f8158808e96e84915c1f1c673c9c53817c9b338943f49e31ed934b1737c341a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / gigbid_portfolio_mcp-0.1.0-py3-none-any.whl
| Download URL | gigbid_portfolio_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 33.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96ad8d73041b888d4b42f3a27c6acc52b210fb54814961d237e831b16764c5f0
|
|
BLAKE2b-256 checksum How to use checksums |
eaf6f45434e87d51e3660e5c8ee20f3e6e4ed0fe44c75b52eee69cd2cc314a46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for gigbid-portfolio-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.