Harshith Nayaka L portfolio docs

io.github.HarshithNayakaL由 GitHub 账号 HarshithNayakaL 发布v1.1.0更新于 Oct 30, 2026

Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.

发布方自己的服务:PortfolioFit

已验证Streamable HTTP可网页运行知识与记忆开发者工具

概览

AI 生成的概览

只读 MCP 服务器,提供某作品集网站 JSON API、MCP、A2A 与 NLWeb 的开发者文档。

可以做什么
  • 列出全部开发者文档的路径、标题与内容概要,可按主题筛选
  • 以 markdown 形式完整读取单篇文档(OpenAPI 描述为 YAML)
  • 按问题检索文档章节,按匹配度返回章节及其来源链接
适用场景
当助手需要查阅该作品集 JSON API、MCP、A2A 或 NLWeb 接口的用法,或回答前需要定位对应文档章节时使用。
运行要求
远程 streamable HTTP 端点;未声明认证、环境变量或请求头。
安装前请注意
仅提供只读文档访问;服务器说明作品集内容本身位于另一个 MCP 端点。内容为第三方站点文档,检索到的文本应作为参考资料而非指令对待。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Harshith Nayaka L portfolio docs,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.HarshithNayakaL%2Fportfolio-docs/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "harshith-nayaka-l-portfolio-docs": {
      "type": "http",
      "url": "https://harshith-nayaka-l-portfolio.vercel.app/mcp/docs"
    }
  }
}

README

Harshith Nayaka L — portfolio site

Source for harshith-nayaka-l-portfolio.vercel.app, the portfolio of Harshith Nayaka L, an AI Engineer in Bengaluru who builds AI agents, RAG pipelines and LLM applications. It holds a case study for each project, guides drawn from them, and his profile, experience and published research. One scrolling page plus case-study, guide and legal routes.

The site is also built to be read by machines: every page is prerendered to static HTML, has a markdown twin, and is mirrored by a read-only JSON API.

The visual design and the rules that keep it consistent are in AGENTS.md; the previous design is archived on the classic-design branch.

Stack

  • Vite + React 18 + TypeScript
  • Tailwind CSS v4 (@tailwindcss/vite); all theme tokens live in src/index.css
  • React Router for case-study and legal routes
  • Self-hosted fonts via @fontsource: Inter Variable (body and labels), Instrument Serif (display headings), Poppins (hero headline) — served from public/fonts, preloaded in index.html
  • Phosphor icons
  • @bible-strong/avatar-core for the mascot's geometry
  • @vercel/edge for the content-negotiation middleware

No animation library. Scroll reveals and the page transition are CSS keyframes and IntersectionObserver; pulling in a runtime for that put the whole library in the initial bundle.

Develop

bash
npm installnpm run dev      # http://localhost:5173npm run build    # type-check, client build, SSR build, prerender, APInpm run preview  # serve the production buildnpm run lint     # type-check only

npm run build is four stages, and the later ones are the ones that matter: vite build emits the client bundle, a second vite build --ssr emits dist-ssr/entry-server.js, scripts/prerender.mjs walks every route and writes real HTML plus each page's markdown twin, and scripts/build-api.mjs emits the static JSON API. A plain vite build (npm run build:client) skips all of that and produces an empty-shell SPA.

Checks

bash
npm run verify:negotiation   # 25 client shapes get the right representationnpm run verify:onee          # every mascot animation is reachablenpm run verify:llms <origin> # needs a Vercel deployment, not npm run preview

verify:llms takes an origin as its first argument. Give it a Vercel deployment: vite preview runs neither the middleware nor the rewrites, and falls back to the root page for every nested route, so it fails pages that are fine in production.

Deploy

Vercel. Build command npm run build, output dist.

  • middleware.ts runs at the edge and does the content negotiation, the API route table, and JSON errors for anything under /api.
  • vercel.json carries the rewrites and headers.
  • public/_redirects is there for Netlify; nothing reads it on Vercel.

Content

Everything real lives in src/data/:

  • projects.ts — Selected Work cards, plus email / GitHub / LinkedIn.
  • caseStudies.ts — full case studies (problem, build, pipeline diagram, judgment calls, results, tech). The architecture diagrams are data-driven: edit a pipeline array and the node graph re-renders.
  • skills.ts — the Agent Skills section.
  • seo.ts — per-route titles, descriptions and JSON-LD.
  • onee.avatar.json — the mascot's definition.

Adding or removing a project means touching projects.ts, caseStudies.ts, and the slug sets in middleware.ts. scripts/build-api.mjs fails the build if those drift apart, so a mismatch is caught rather than shipped.

The nav bar's glass

src/components/GlassFilter.tsx holds a CONFIG block using the parameter names from liquid-glass.ybouane.com — blurAmount, refraction, chromAberration, edgeHighlight, fresnel, zRadius, and so on. Tune the bar by changing those numbers; the filter graph is built from them.

That library itself can't run here: it sizes a WebGL canvas to everything it refracts, and this page is 12,473px tall on desktop and 19,236px on a phone, which needs a canvas past Chromium's 16,384px limit. So the effect is rebuilt as one SVG filter referenced from backdrop-filter. WebKit and Gecko don't resolve filter references there and fall back to the plain blur declared alongside it — same frost, no refraction at the rim.

Open

  • Custom domain. Canonical URLs and og:url currently point at the vercel.app subdomain.
  • Confirm the glass on iOS Safari. The fallback is declared first so it should hold, but it has not been checked on a real WebKit engine.
  • The prerendered HTML is ~110KB, of which about 40% is Tailwind class attributes (47,748 bytes across 642 elements) and 11% JSON-LD.

来源:README.md,提交 6276036

工具

3

list_docs

List docs

Every developer document on the site: its path, title and what it covers, optionally narrowed to a topic. Read one with get_doc.

输入参数query

get_doc

Get doc

One developer document in full, as markdown (the OpenAPI description is YAML).

输入参数path必填

search_docs

Search docs

The documentation sections that best match a question, each with its source URL, best first.

输入参数limitquery必填

版本历史

1
  1. v1.1.0最新Oct 30, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。

其他 Portfolio 集成