# Alberto Giacomel — professional portfolio

> Official portfolio of Alberto Giacomel, Engineering Consulting Senior Manager. Public professional information is available in English and Italian.

## Content
- [Portfolio](https://www.giacomel.info/): Biography, expertise, experience and projects.
- [Blog](https://www.giacomel.info/blog): Technical articles.
- [Complete portfolio text](https://www.giacomel.info/llms-full.txt): Profile, career history and projects in both languages, readable without JavaScript or MCP.

## AI access
- [Connection instructions](https://www.giacomel.info/llms.txt): Public MCP and browser WebMCP access.
- [MCP server description](https://www.giacomel.info/.well-known/mcp): Tool schemas and endpoint metadata (discovery convention).
- [MCP JSON alias](https://www.giacomel.info/.well-known/mcp.json): Same server description as JSON.
- [WebMCP description](https://www.giacomel.info/.well-known/webmcp.json): Browser tool metadata (discovery convention).

MCP endpoint: https://www.giacomel.info/api/mcp
Transport: Streamable HTTP. Protocol: 2026-07-28. Authentication: none; public read-only data.
Legacy protocol versions: 2025-11-25, 2025-06-18, 2025-03-26 (initialize handshake retained).
Tools: get_profile, get_experience, get_projects.
Resources: giacomel://profile/en, giacomel://profile/it, giacomel://experience/en, giacomel://experience/it, giacomel://projects/en, giacomel://projects/it.
Use resources/list and resources/read for the six bilingual JSON resources; resource templates and subscriptions are not offered.
Prompts: summarize_profile, prepare_interview.
Use prompts/list and prompts/get to retrieve a user-selected template with attached portfolio context. No LLM is invoked by the server.
summarize_profile accepts lang and audience (recruiter, client or technical); prepare_interview accepts lang and a required role label.
Each tool accepts an optional lang parameter: en (default) or it.
An MCP-capable client must explicitly connect to the endpoint. Reading this file does not connect a client.
Modern MCP is stateless: call server/discover (optional), tools/list or tools/call directly, without initialize or ping.
Every modern request must include params._meta with io.modelcontextprotocol/protocolVersion and io.modelcontextprotocol/clientCapabilities.
Send MCP-Protocol-Version and Mcp-Method HTTP headers matching the body; tools/call and prompts/get require Mcp-Name matching params.name, resources/read matching params.uri.
Accept must list application/json and text/event-stream. Successful modern results include resultType: complete.
Browser WebMCP registers the same tools when document.modelContext or legacy navigator.modelContext is available.
WebMCP is a separate browser API and does not use the remote MCP protocol's version or handshake.
Use a browser agent with WebMCP support; browser flags or an origin trial may be required.
For Italian tool responses, pass {"lang":"it"}. For English, pass {"lang":"en"} or omit lang.
These discovery files do not guarantee search indexing or automatic tool execution.