life.ayushrai.site product MCP

site.ayushrai.lifePublished by life.ayushrai.siteOfficial publisherv1.0.0Updated Oct 31, 2026

Read-only public profile, projects, contact, search, and booking links for Ayush Rai.

The publisher's own server: life.ayushrai.site docs MCP

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Read-only remote MCP server exposing Ayush Rai's public profile, contact details, site search and booking links to an assistant.

What you can do
  • Retrieve a public profile summary for Ayush Rai
  • Get public email, phone and booking links
  • Search public site pages with a short query
  • Return booking links so the caller can schedule a conversation
When to use it
Useful when an assistant needs background on Ayush Rai, his public contact details or booking links, or wants to look up facts published on his personal site. It is a narrow, read-only lookup rather than a general-purpose tool.
Requirements
A remote streamable HTTP endpoint at life.ayushrai.site; no packages, environment variables, headers or authentication are declared. Network access to that host is needed.
Before you install
The server returns personal contact information such as email and phone, so results may be shared onward by the assistant. Booking is only a link handoff; no scheduling is performed by the server. All tools are described as read-only, so no data is written or changed.

Installation

In SourceWeft

  1. Open life.ayushrai.site product MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/site.ayushrai.life%2Fproduct/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "life-ayushrai-site-product": {
      "type": "http",
      "url": "https://life.ayushrai.site/mcp/product"
    }
  }
}

README

Personal Knowledge Base (PKB)

This repository is a long-term personal knowledge system. The website is one optional consumer; not the source of truth.

Start here

  1. docs/KNOWLEDGE_SYSTEM.md
  2. docs/FILE_STRUCTURE.md
  3. docs/ENTITY_MODEL.md
  4. docs/RELATIONSHIP_MODEL.md
  5. docs/CONTENT_WORKFLOW.md

Layout

PathRole
/knowledgeCanonical facts, narratives, identity, media, graph
/docsOperating manuals
/data/importsOriginal spreadsheets/exports (provenance)
/scripts/knowledgeValidate + import
/sitesWebsite consumer (presentation only)
/discoveryAgent docs served at root URLs via vercel.json rewrites (/auth.md, /openapi.json, /pricing.md, ...)
/api, /agent, middleware.jsServerless endpoints, negotiation, agent mode

Principles

  • One fact, one place
  • Reference by entity id; never duplicate
  • Evidence over marketing language
  • Uncertain identity data → /knowledge/review, never silent delete

Commands

bash
npm run validate       # knowledge validation (Node)
npm run build:site     # generate resumes, portfolios, domains from data/site-catalog.json
npm run qa             # static QA (em dashes, viewport, catalog coverage); exits 1 on failure
npm run check:agent    # agent surface checks (negotiation, discovery, jobs, trust pages)
npm run local            # full local site on http://localhost:3000 (vercel dev: middleware, rewrites, api/)
npm start              # static-only preview (Python http.server; no rewrites or api/)
node scripts/build-home.js   # regenerate homepage from knowledge/_system/homepage.yaml
npm run build:collections    # work index, books, influences from knowledge/{work,books,influences}/*.json

Adding work, books, people, essays, and policy case studies: docs/workflows/ADDING_LIFE_CONTENT.md.

Browse the homepage at / under npm run local. Public site: https://life.ayushrai.site/. Developer portal: https://life.ayushrai.site/developers/.

Agent skills (skills.sh)

bash
npx skills add ayushrai-hub/LifeOS

See skills/README.md.

SDK / CLI packages

Publish with owner registry auth (npm publish / python -m build && twine upload).

Website consumer

The site is a knowledge graph in HTML: no mega-menu, inline blue links, multiple resumes and portfolios, domain pages, certifications, and media entities. Edit data/site-catalog.json, then run npm run build:site.

Deploy (Vercel)

  • middleware.js rewrites / → sites/www/ and 308s /sites/www → /
  • vercel.json maps root agent URLs to files in discovery/
  • Content chronology lives in knowledge entities + knowledge/_system/site-status.yaml
bash
npx vercel

Identity spreadsheet

Drop the master online-presence file into data/imports/ and run the import script.

Filling personal data

Provide biography facts, work dates, certifications, and resume details. Until then, entity sections stay empty on purpose; nothing is invented.

Source: README.md at commit 8813f7c

Tools

4

get_profile

Return Ayush Rai's public profile summary.

Parametersinclude_contact

get_contact

Return public email, phone, and booking links.

Parameterschannel

search_public_facts

Search public site pages by a short query.

Parametersqueryrequired

book_a_conversation

Return Ayush Rai's public booking links so the caller can schedule time.

Parameterstopicrequired

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Ayushrai integrations