portfolio-mcp

A Model Context Protocol (MCP) server for managing portfolio posts and projects. Allows Claude and other AI assistants to create, edit, and delete blog posts and projects, with Git integration for committing and pushing changes to GitHub.

Features

• Post Management: Create, read, update, and delete MDX blog posts

• Project Management: Manage projects in projectsData.js

• Git Integration: View status and commit/push changes with confirmation

• MCP Protocol: Full MCP server implementation for Claude integration

• REST API: Standalone REST API for web-based management

Setup

1. Copy the config file:

   cp portfolio-mcp.config.json.example portfolio-mcp.config.json

2. Update portfolio-mcp.config.json with your portfolio path:

   { "portfolioPath": "/path/to/your/suthar-portfolio", "postsDir": "data/posts", "projectsFile": "data/projectsData.js", "git": { "remote": "origin", "branch": "main", "requireConfirmation": true }, "api": { "port": 3333, "host": "localhost" } }

3. Install dependencies:

   npm install

4. Build TypeScript:

   npm run build

Running

MCP Server (for Claude Desktop)

REST API Server

Development

Watch mode for MCP:

Watch mode for REST API:

MCP Tools

REST API Endpoints

• GET /health - Health check

• GET /api/posts - List posts

• GET /api/posts/:slug - Get post

• POST /api/posts - Create post

• PUT /api/posts/:slug - Update post

• DELETE /api/posts/:slug - Delete post

• GET /api/projects - List projects

• POST /api/projects - Create project

• PUT /api/projects/:title - Update project

• DELETE /api/projects/:title - Delete project

• GET /api/git/status - Git status

• POST /api/git/commit-push - Commit and push

Post Format

Posts are MDX files with YAML frontmatter:

Optional fields: pinned, pinnedtext

Project Format

Projects are managed in projectsData.js:

Git Workflow

The git_commit_push tool implements a two-step confirmation workflow:

1. First call (no confirmed param): Returns a dry-run showing what would be committed

2. Second call (with confirmed: true): Executes the actual commit and push

This prevents accidental commits and allows users to review changes before pushing.

Claude Desktop Integration

Local Setup

Add to claude_desktop_config.json:

Deployment to Vercel (Recommended for Always-On Access)

This is the most secure approach since Vercel uses HTTPS and you already have sohumsuthar.com there.

Step 1: Push to GitHub

Step 2: Connect to Vercel

Option A: Standalone Vercel Project

Option B: Add to existing sohumsuthar.com project

1. Go to https://vercel.com/dashboard

2. Select your sohumsuthar project

3. Settings → Integrations → Add integration

4. Deploy from portfolio-mcp directory

Step 3: Set Environment Variables

On Vercel dashboard, go to Settings → Environment Variables:

Step 4: Update Claude Desktop Config

For remote Vercel access:

Or better yet, use a simple proxy wrapper:

Create vercel-client.js:

Security Features

• ✅ HTTPS via Vercel

• ✅ API Key authentication (Bearer token)

• ✅ CORS restricted to your domain

• ✅ Environment variables for secrets (never in git)

• ✅ Request logging

• ✅ Rate limiting ready (can add)

• ✅ GITHUB_TOKEN for private repo access

Generating a GitHub Token

If your portfolio repo is private:

1. Go to https://github.com/settings/tokens

2. Click "Generate new token (classic)"

3. Give it repo scope

4. Copy and add to Vercel env vars

License

MIT