Skip to main content
Glama

portfolio-mcp

A remote MCP server for publishing to ashutoshverma.dev from any Claude client — including a phone.

Six tools that move bytes. The model does the writing; the server reads content, serves skills, saves drafts, and opens a pull request. It never merges. The merge button is the gate, and it is somewhere the model cannot reach.

Status: no server code yet. The site side is done; this repo is at Slice 1.


Where things live

This repo is the server only. Two other repos are involved and neither is worked on from here:

Repo

Holds

This server's access

portfolio

The public site, published MDX

Opens PRs. Never commits to main

workshop (private)

Drafts, skills, templates, social post archive

Commits straight to main

portfolio-mcp

The server. This repo

No repo is ever cloned. Every read and write goes through the GitHub API, because a checkout on disk means stale state and surprise conflicts.


Related MCP server: memoh-mcp

Read these first

File

What it holds

CONTEXT.md

The problem, the domain words, what we are not building

docs/adr/mcp-design.md

The full design: six tools, publish gate, idempotency, and everything rejected

docs/adr/001-server-runtime-and-shape.md

Why TypeScript on Bun and not Python

CLAUDE.md

Agent entry point — an index to the rules

tech-stack.yaml

The approved dependency menu

The rejected-alternatives table in mcp-design.md is the most useful page in the repo. It is cheaper to read than to re-argue.


Stack

Bun · TypeScript strict · Elysia · Zod · Biome · bun:test · the MCP TypeScript SDK. Reasoning in ADR-001; the short version is that publish has to parse MDX, and MDX only parses in JavaScript.

No database, no accounts, no queue. Auth is an unguessable secret in the URL path — there is exactly one user, which is the one case OAuth adds nothing to.


Build order

Plumbing before anything interesting.

Slice

Ships

State

0

Site prep: the five JSON routes, OG images

done — in portfolio

1

Skeleton, secret path, /health, get_skill only. Deployed

next

2

Reads: list_content, get_content

3

Cheap writes: save_draft, discard_draft

4

publish: validation, branch, PR, idempotency

5

Polish: lazy reconciliation, response nudges, Claude Project

Slice 1 is deliberately almost nothing. The riskiest unknown in the plan is whether a custom connector behaves properly in the mobile app, and that cannot be tested locally. Find out with 80 lines, not after six tools exist.


Working in this repo

Feature work follows SPEC-WORKFLOW.md: an accepted ADR, then a sliced spec, then the red-green loop, one slice per PR.

bun install
bun test
bun run docs:sync    # regenerates GENERATED blocks; CI fails on drift

SETUP.md is install notes for the agent scaffold this repo started from. Safe to delete once you stop needing them.

F
license - not found
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • Markdown-first MCP server for Notion API with 8 composite tools and 39 actions.

  • A MCP server built for developers enabling Git based project management with project and personal…

  • Augments MCP Server - A comprehensive framework documentation provider for Claude Code

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ashutosh6393/Portfolio-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server