MCP

This site runs a Model Context Protocol server. Connect it once and Claude Code, Cursor or any other MCP client can answer questions about my work straight from the source, instead of you reading every page or me sending a PDF.

Claude Code

One command:

claude mcp add --transport http oussama https://oelhaidi.com/.well-known/mcp

Add --scope user to make it available in every project.

Cursor, and everything else

Add it to your MCP config file: .cursor/mcp.json for Cursor, .mcp.json for Claude Code, or wherever your client keeps its servers.

{
  "mcpServers": {
    "oussama": {
      "type": "http",
      "url": "https://oelhaidi.com/.well-known/mcp"
    }
  }
}

Then ask

What it exposes

get_profile

Get the profile of Elhaidi Oussama: role, location, years of experience, services, availability and contact channels.

list_projects

List selected products, design systems, plugins and case studies with links.

list_topics

List published write-ups with their descriptions, dates and tags.

get_topic

Get the full markdown of one published write-up by its slug.

search_site

Keyword search across the profile, projects and published writing.

get_contact_info

Get how to contact Elhaidi Oussama, and what an enquiry should include.

The endpoint

https://oelhaidi.com/.well-known/mcp

Streamable HTTP transport, stateless, with no authentication and no API key. POST JSON-RPC to it. A plain GET returns the server card, which lists the same tools as above.

Without an MCP client

If your tool can't speak MCP, /llms.txt is a plain-text summary of everything here: the work, the roles, the outcomes and the links. Any tool that can fetch a URL can read it. There is also a guide for agents covering every machine-readable endpoint on the site.

What it will not tell you

Everything the server returns is already public on this site. It is read-only: it can't send me a message, book a call or see anything private. To get in touch, email [email protected] or use the contact page.