Yerevan Product Coffee: table dates, remaining seats, seat requests, and the field notes behind it.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
The complete text of a single field note. Use this after search_field_notes or list_field_notes, which return only an excerpt. Accepts the slug, the path, or the full URL — 'what-30-days-of-crawler-logs-showed', '/what-30-days-of-crawler-logs-showed' and 'https://hovhannes.io/what-30-days-of-crawler-logs-showed' all work.
The note's slug, path, or URL
The complete text of a single field note. Use this after search_field_notes or list_field_notes, which return only an excerpt. Accepts the slug, the path, or the full URL — 'what-30-days-of-crawler-logs-showed', '/what-30-days-of-crawler-logs-showed' and 'https://hovhannes.io/what-30-days-of-crawler-logs-showed' all work.
| Argument | Type | Description |
|---|---|---|
| note* | string | The note's slug, path, or URL |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"note"
],
"properties": {
"note": {
"type": "string",
"maxLength": 300,
"minLength": 3,
"description": "The note's slug, path, or URL"
}
}
}What a Clarity Sprint is, what it produces, how long it takes, what it costs, and where to apply. Use this when asked how to work with Hovhannes or what he offers.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}Every published field note with its title, category and date, newest first. Use this to see the full range of what has been written before searching within it, then get_field_note to read one in full.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}The scheduled dates for the private six-person product roundtable in Yerevan, with how many guest seats remain on each. Use this to answer when the next table is or whether a given date still has room, and to get the exact `startsAt` value that request_table_seat needs.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}Ask for one of the five guest seats at a Yerevan Product Coffee table. Call list_upcoming_tables first and pass one of its exact `startsAt` values. This sends a real request to a real person, so it takes two calls: call it once to see exactly what would be sent, show that to the person it is about, then call it again with the same values and confirm: true. A request is not a booking — Hovhannes reads each one himself and replies within 3–5 days, and no seat is held until he does.
| Argument | Type | Description |
|---|---|---|
| email* | string | Their email address. The reply and the confirmation both go here, so it has to be one they read |
| phone* | string | Their phone number with its country code, like +374 11 22 33 44. Used only on the evening itself and deleted if the request is closed |
| confirm | boolean | Leave unset or false to validate and preview without sending anything. Set to true only after the person has seen the preview and agreed to it |
| building | string | What they are building, in their own words. Optional but read |
| fullName* | string | The applicant's full name, as they would write it |
| eventStart* | string | Which table. The exact `startsAt` from list_upcoming_tables is best, but the calendar day on its own ("2026-09-10") or the word "next" also resolve against the real schedule |
Search Hovhannes Hovhannisyan's written field notes on product planning, MVP scope, and building with AI agents. Returns the closest notes with a short excerpt and a link. Use this when asked what he has written or thinks about a product topic, then get_field_note to read one in full.
| Argument | Type | Description |
|---|---|---|
| query* | string | What to look for, in words |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 120,
"minLength": 2,
"description": "What to look for, in words"
}
}
}| motivation | string | Why this table, now. Optional |
| linkedinUrl* | string | Their personal LinkedIn profile URL (linkedin.com/in/…). Required: seats are chosen on who sits together, which cannot be judged from a name. Company pages, posts and shortened links are refused |
| perspective* | string | The perspective they bring: founder (Building or validating a product of your own.); product (Deciding scope, priority, discovery, and delivery.); design-research (Bringing users, flows, and evidence into the room.); engineering (Turning product intent into something real.); growth (Positioning, demand, distribution, retention.); customer (Sales, support, and discovery signals.); hybrid-other (More than one lens, and that is fine.) |
| contribution | string | What they can offer the other five people. Optional |
| discussionQuestion | string | The one real decision or trade-off they are stuck on and want the table's help with. Optional, and the single most useful thing to include |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"fullName",
"email",
"phone",
"linkedinUrl",
"perspective",
"eventStart"
],
"properties": {
"email": {
"type": "string",
"maxLength": 254,
"minLength": 3,
"description": "Their email address. The reply and the confirmation both go here, so it has to be one they read"
},
"phone": {
"type": "string",
"maxLength": 32,
"minLength": 5,
"description": "Their phone number with its country code, like +374 11 22 33 44. Used only on the evening itself and deleted if the request is closed"
},
"confirm": {
"type": "boolean",
"description": "Leave unset or false to validate and preview without sending anything. Set to true only after the person has seen the preview and agreed to it"
},
"building": {
"type": "string",
"maxLength": 1000,
"description": "What they are building, in their own words. Optional but read"
},
"fullName": {
"type": "string",
"maxLength": 80,
"minLength": 2,
"description": "The applicant's full name, as they would write it"
},
"eventStart": {
"type": "string",
"maxLength": 40,
"minLength": 4,
"description": "Which table. The exact `startsAt` from list_upcoming_tables is best, but the calendar day on its own (\"2026-09-10\") or the word \"next\" also resolve against the real schedule"
},
"motivation": {
"type": "string",
"maxLength": 600,
"description": "Why this table, now. Optional"
},
"linkedinUrl": {
"type": "string",
"maxLength": 500,
"minLength": 5,
"description": "Their personal LinkedIn profile URL (linkedin.com/in/…). Required: seats are chosen on who sits together, which cannot be judged from a name. Company pages, posts and shortened links are refused"
},
"perspective": {
"enum": [
"founder",
"product",
"design-research",
"engineering",
"growth",
"customer",
"hybrid-other"
],
"type": "string",
"description": "The perspective they bring: founder (Building or validating a product of your own.); product (Deciding scope, priority, discovery, and delivery.); design-research (Bringing users, flows, and evidence into the room.); engineering (Turning product intent into something real.); growth (Positioning, demand, distribution, retention.); customer (Sales, support, and discovery signals.); hybrid-other (More than one lens, and that is fine.)"
},
"contribution": {
"type": "string",
"maxLength": 600,
"description": "What they can offer the other five people. Optional"
},
"discussionQuestion": {
"type": "string",
"maxLength": 600,
"description": "The one real decision or trade-off they are stuck on and want the table's help with. Optional, and the single most useful thing to include"
}
}
}