Skip to main content

ayaan33-gigbid-portfolio-mcp

An MCP server that lets Claude Desktop, Cursor or any MCP host search your freelance portfolio for evidence: case studies, code repositories, client reviews and past proposals with their outcomes. The assistant can then write proposals and answer screening questions that cite real work instead of inventing it.

It's part of GigBid, a multi-agent freelancer copilot. It's read-only: it never writes anything anywhere.

Tools, resources and prompts

Name What it does
tool search_evidence(requirement, k, filters) Hybrid (BM25 + embeddings) multi-vector retrieval over your portfolio. Returns items with id, type, source, date and outcome. Filters: type, skills, outcome, client_industry, since.
tool get_case_study(id) The full case study.
tool list_skills() Every skill your portfolio proves, with evidence counts.
resource portfolio://case/{key}, portfolio://proposal/{key}, portfolio://repo/{name}, portfolio://cv, portfolio://profile Load full items.
prompt answer_screening_question, summarise_fit, rewrite_with_evidence, opening_line Ready-made workflows.

Embeddings (nomic-embed-text-v1.5) run locally on CPU. No API key is needed, and your portfolio never leaves your machine.

Portfolio folder

my-portfolio/            <- GIGBID_PORTFOLIO_DIR
  me/                    <- PORTFOLIO_PERSONA=me
    cv.pdf
    case_studies/*.md    (one project per file; '# Title' + sections)
    repos/<repo>/README.md + source files
    reviews.json         [{"id","project","stars","text","date","client_industry"}]   (optional)
    proposals.jsonl      {"id","job_title","text","outcome":"won|replied|ignored", ...} (optional)

manifest.json is generated automatically the first time it runs.

Run it

uvx ayaan33-gigbid-portfolio-mcp            # stdio, for MCP hosts

Or with Docker / HTTP (Streamable HTTP at /mcp, Bearer token required):

MCP_BEARER_TOKEN=change-me uvx ayaan33-gigbid-portfolio-mcp --http

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "portfolio": {
      "command": "uvx",
      "args": ["ayaan33-gigbid-portfolio-mcp"],
      "env": { "GIGBID_PORTFOLIO_DIR": "/Users/you/my-portfolio", "PORTFOLIO_PERSONA": "me" }
    }
  }
}

Cursor (.cursor/mcp.json)

Use the same command, args and env as above.

Configuration

Variable Default Meaning
GIGBID_PORTFOLIO_DIR bundled demo portfolios Folder that contains your portfolio folder(s).
PORTFOLIO_PERSONA ai_ml_engineer Which sub-folder to serve.
RAG_VARIANT from config Retrieval pipeline (v0_naive … v8_corrective).
MCP_BEARER_TOKEN — Required for --http.

MIT licence.

Metadata

Release files for ayaan33-gigbid-portfolio-mcp 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ayaan33-gigbid-portfolio-mcp 1.0.0
File Size Uploaded Provenance Actions
ayaan33_gigbid_portfolio_mcp-1.0.0.tar.gz 32.9 kB Without provenance Details for ayaan33_gigbid_portfolio_mcp-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ayaan33-gigbid-portfolio-mcp 1.0.0
File Interpreter ABI Platform Actions
ayaan33_gigbid_portfolio_mcp-1.0.0-py3-none-any.whl Python 3 none any Details for ayaan33_gigbid_portfolio_mcp-1.0.0-py3-none-any.whl

Total release size: 77.9 kB

Release files / ayaan33_gigbid_portfolio_mcp-1.0.0.tar.gz

Download URL ayaan33_gigbid_portfolio_mcp-1.0.0.tar.gz
Size 32.9 kB
Tags Source
SHA-256 checksum
How to use checksums
80b7d2e4a9072e6f0cbeaab445ac4ce71efcffaefc6ba3783044159c3c67cc6d
BLAKE2b-256 checksum
How to use checksums
b7bff3e8e73cdb68ff2beaa5132e99849365e140d48f9646da086e686d5831ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / ayaan33_gigbid_portfolio_mcp-1.0.0-py3-none-any.whl

Download URL ayaan33_gigbid_portfolio_mcp-1.0.0-py3-none-any.whl
Size 45.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b2dfd65cb58a3e9ad2aa0d48e5374a11107fd2bc93f68188c0e7a63a231c1081
BLAKE2b-256 checksum
How to use checksums
a79a2aa0557058fcdc0527870a9b8527d22e9dc47edd093b31ab7724c23543b3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for ayaan33-gigbid-portfolio-mcp 1.0.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.

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page