Portfolio MCP Server
A dual-stack Model Context Protocol (MCP) server for Srikanth Karthikeyan's portfolio data, available in both Node.js and Python implementations with containerized deployment options.
Features
The server provides the following tools:
🔍 search_portfolio
Search through portfolio data by keywords, category, or content.
Parameters:
query(required): Search query to find relevant informationcategory(optional): Filter by specific categorylimit(optional): Maximum results to return (default: 10)
📂 get_portfolio_categories
Get all available categories in the portfolio data.
🎯 get_portfolio_item
Get a specific portfolio item by ID.
Parameters:
id(required): The ID of the portfolio item
📞 get_contact_info
Get all contact information.
💻 get_tech_stack
Get detailed information about technical skills and tools.
Parameters:
type(optional): Filter by specific tech type
🚀 Installation & Deployment
Package Registries
Node.js Packages (Both Registries)
# From npmjs.com (public)
npm install srikanth-mcp-portfolio-server
# From GitHub Packages
npm install @srikanth-karthi/srikanth-mcp-portfolio-server
Python Package
# From PyPI (public)
pip install srikanth-mcp-portfolio
Docker Deployment (Multiple Registries)
From Docker Hub (Public)
# Node.js version
docker run -it srikanthkarthi/mcp-portfolio-server:nodejs-latest
# Python version
docker run -it srikanthkarthi/mcp-portfolio-server:python-latest
# Multi-runtime version
docker run -it srikanthkarthi/mcp-portfolio-server:multi-latest
From GitHub Container Registry
# Node.js version
docker run -it ghcr.io/srikanth-karthi/mcp-portfolio-server:nodejs-latest
# Python version
docker run -it ghcr.io/srikanth-karthi/mcp-portfolio-server:python-latest
# Multi-runtime version
docker run -it ghcr.io/srikanth-karthi/mcp-portfolio-server:multi-latest
Using Docker Compose (Local Development)
# Choose one:
docker compose up mcp-portfolio-nodejs # Node.js only
docker compose up mcp-portfolio-python # Python only
docker compose up mcp-portfolio-multi # Both runtimes
Development Setup
Node.js Development
npm install
npm run dev
Python Development
pip install -e .
python -m mcp_portfolio_server.server
🔧 Claude Desktop Integration
Using Docker Hub (Public)
{
"mcpServers": {
"portfolio": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"srikanthkarthi/mcp-portfolio-server:latest"
]
}
}
}
Using GitHub Container Registry
{
"mcpServers": {
"portfolio": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"ghcr.io/srikanthkarthi/mcp-portfolio-server:latest"
]
}
}
}
Using npm Package (Public Registry)
{
"mcpServers": {
"portfolio": {
"command": "npx",
"args": ["srikanth-mcp-portfolio-server"]
}
}
}
Using npm Package from GitHub Packages
{
"mcpServers": {
"portfolio": {
"command": "npx",
"args": ["@srikanth-karthi/srikanth-mcp-portfolio-server"]
}
}
}
Using Python Package
{
"mcpServers": {
"portfolio": {
"command": "python",
"args": ["-m", "mcp_portfolio_server.server"]
}
}
}
Development Mode
{
"mcpServers": {
"portfolio": {
"command": "node",
"args": ["/path/to/mcp-portfolio/src/index.js"],
"cwd": "/path/to/mcp-portfolio"
}
}
}
📦 Automated Building & Publishing
GitHub Actions Workflows
The repository includes automated CI/CD workflows:
- Triggers: Git tags (
v*) or manual workflow dispatch - Builds: Multi-architecture Docker images (AMD64/ARM64)
- Publishes:
- Node.js package to GitHub Packages
- Python package to PyPI
- Docker images to GitHub Container Registry
Manual Building
Docker Build Commands
# Build Node.js image
docker build --target nodejs -t mcp-portfolio:nodejs .
# Build Python image
docker build --target python -t mcp-portfolio:python .
# Build multi-runtime image
docker build --target multi -t mcp-portfolio:multi .
Configuration Options
| Environment Variable | Description | Default |
|---|---|---|
NODE_ENV |
Node.js environment | production |
PYTHONUNBUFFERED |
Python output buffering | 1 |
DATA_PATH |
Portfolio data file path | /app/sample-data.json |
Switch between Node.js and Python in multi-runtime container:
# In docker-compose.yml, uncomment to use Python:
command: ["python3", "-m", "mcp_portfolio_server.server"]
Data Categories
The server provides access to the following portfolio categories:
- Profile Summary: Overview and introduction
- Current Position: Job title, company, duration
- Current Work: Responsibilities and projects
- Experience: Work history and achievements
- Education: Academic background
- Tech Stack: Programming languages, frameworks, tools
- Certifications: Professional certifications
- Volunteerism: Community service and activities
- Contact: Social media and professional links
- Languages: Language proficiency
Example Queries
- Search for cloud experience:
search_portfolio("cloud", "Experience") - Get all tech stack info:
get_tech_stack() - Find contact information:
get_contact_info() - Search for certifications:
search_portfolio("aws certification")
License
MIT
Metadata
Release files for srikanth-mcp-portfolio 1.5.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 |
|---|---|---|---|---|
| srikanth_mcp_portfolio-1.5.0.tar.gz | 12.3 kB | With provenance | Details for srikanth_mcp_portfolio-1.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| srikanth_mcp_portfolio-1.5.0-py3-none-any.whl | Python 3 | none | any | Details for srikanth_mcp_portfolio-1.5.0-py3-none-any.whl |
Total release size: 24.5 kB
Release files / srikanth_mcp_portfolio-1.5.0.tar.gz
| Download URL | srikanth_mcp_portfolio-1.5.0.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40c4b908183968889965ae9479e541676267b8834682c69d4b0c3897885a6d0b
|
|
BLAKE2b-256 checksum How to use checksums |
260bab91808c6ae6349e39393831368ca4f6c83ceeb15f5ac673316c7a91e13d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2025.
Transparency logRelease files / srikanth_mcp_portfolio-1.5.0-py3-none-any.whl
| Download URL | srikanth_mcp_portfolio-1.5.0-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f32e3de0fe262bc2a7e1add44effb1ed8c92ab9abb10f40941e910873f714b9b
|
|
BLAKE2b-256 checksum How to use checksums |
a3462e5b165df074512d631dfe270d3e37a1b9fe9a8c112da777a587d584e536
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2025.
Transparency logSecurity for srikanth-mcp-portfolio 1.5.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for srikanth_mcp_portfolio-1.5.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2025.
Transparency logA 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.