Zovo Genogram MCP

Generates standard genogram charts from family lists, supporting symbols for sex, deceased status, relationships, and emotional connections. Outputs vector PDF, SVG, and CSV files with geometry checks and data validation for parent cycles and unknown IDs.

Visit Zovo

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-08Published by Zovo

You need:No sign-in is needed

MCP endpoint (Streamable HTTP)

https://genogram.zovo.one/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 8, 2026, 2:47 AM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Draw a genogram from a list of people and relationships
Check family data for mistakes before drawing
Generate an A3 genogram of multiple generations
Export family tree data to CSV and SVG

Source and maintenance

Community listingRegistry 1.0.0

mcp-registry: io.github.theluckystrike/genogram@1.0.0 Project website

Protocol and capabilities

Server: genogram 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 2 advertised
Resources: 1 advertised
Resource templates: 1 advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Zovo Genogram draws a family genogram with standard symbols from a list of people and their family and emotional relationships, with PDF, SVG and CSV downloads. Use make_genogram to draw it and check_genogram to check the family data without drawing (unknown ids, parent cycles, more than 2 biological parents, impossible years, generation count). Relationships only: it has no health or medical fields. Files of large charts are kept for 1 hour so the download links work, then deleted.

Tools

2 advertised

make_genogram — Make genogram

Advertised by the server during the last successful anonymous check.

Advertised read-only

Use this when the user wants a genogram or family diagram with standard symbols drawn from people and their relationships, for example "draw a genogram of my family" or "make a three-generation genogram for my social work class". Takes people (id, name, sex, birth and death years, deceased, index person; no label or notes), relations (couple: married, divorced, separated, cohabiting, engaged; parent_child: biological, adopted, foster; twins: identical, fraternal; emotional: close, distant, conflict, cut_off, hostile), an optional household, a title and a page size. Returns counts, each person's generation number, a geometry check (overlapping symbols or names, family lines through a name), the legend of symbols used, an interactive chart, and PDF, SVG, people CSV and relationships CSV downloads. An emotional relationship is drawn as a line only between two people next to each other in the same row; all others, including any between a parent and a child, are listed in a "Relationships not drawn" table and are not in the legend. Refuses unknown ids, parent cycles, more than 2 biological parents and impossible years, naming the problem. Up to 150 people, 12 generations and 100 emotional relationships. Relationships only: does not take health or medical details. Download links of large charts expire after about 1 hour.

make_genogram input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "people"
  ],
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 400,
      "description": "Title printed on the chart and used in file names, up to 80 characters, e.g. \"Kowalski family\"."
    },
    "people": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "name"
        ],
        "properties": {
          "id": {
            "type": "string",
            "maxLength": 400,
            "description": "Short unique id, up to 40 characters, used in relations, e.g. \"p1\" or \"maria\"."
          },
          "sex": {
            "enum": [
              "M",
              "F",
              "X",
              "unknown"
            ],
            "type": "string",
            "description": "M (square), F (circle), X (diamond) or unknown (diamond with ?). Default unknown."
          },
          "name": {
            "type": "string",
            "maxLength": 400,
            "description": "Name shown under the symbol, up to 60 characters, e.g. \"Maria Kowalska\"."
          },
          "index": {
            "type": "boolean",
            "description": "true for the index person (the person the genogram is about); drawn with a double line. At most one."
          },
          "deceased": {
            "type": "boolean",
            "description": "true draws an X through the symbol when the death year is not known."
          },
          "birth_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "4-digit birth year, e.g. 1958."
          },
          "death_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "4-digit death year, e.g. 2019. Marks the person as deceased."
          }
        },
        "additionalProperties": {}
      },
      "maxItems": 2000,
      "description": "The people, up to 150. Example: [{\"id\":\"p1\",\"name\":\"Jan\",\"sex\":\"M\",\"birth_year\":1950},{\"id\":\"p2\",\"name\":\"Ewa\",\"sex\":\"F\",\"birth_year\":1952},{\"id\":\"p3\",\"name\":\"Ola\",\"sex\":\"F\",\"birth_year\":1980,\"index\":true}]."
    },
    "household": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 400
      },
      "maxItems": 2000,
      "description": "Ids of the people who live together; drawn with a dashed outline, e.g. [\"p2\",\"p3\"]."
    },
    "page_size": {
      "enum": [
        "letter",
        "a4",
        "tabloid",
        "a3",
        "a2"
      ],
      "type": "string",
      "description": "PDF page: letter (default), a4, tabloid, a3 or a2. One page when the whole chart fits with text of at least 6 pt; else the chart prints in overlapping parts at full size."
    },
    "relations": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type",
          "a",
          "b"
        ],
        "properties": {
          "a": {
            "type": "string",
            "maxLength": 400,
            "description": "Person id. For parent_child this is the parent, e.g. \"p1\"."
          },
          "b": {
            "type": "string",
            "maxLength": 400,
            "description": "Person id. For parent_child this is the child, e.g. \"p3\"."
          },
          "kind": {
            "type": "string",
            "maxLength": 40,
            "description": "couple: married (default), divorced, separated, cohabiting, engaged. parent_child: biological (default), adopted, foster. twins: identical, fraternal (default). emotional: close (default), distant, conflict, cut_off, hostile."
          },
          "type": {
            "enum": [
              "couple",
              "parent_child",
              "twins",
              "emotional"
            ],
            "type": "string",
            "description": "couple, parent_child (a is the parent, b the child), twins, or emotional."
          },
          "end_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "Year a couple divorced, separated or ended, e.g. 1995."
          },
          "start_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "Year a couple married or began, e.g. 1981."
          }
        }
      },
      "maxItems": 5000,
      "description": "The relationships, up to 600 (at most 150 couples and 100 emotional). Example: [{\"type\":\"couple\",\"a\":\"p1\",\"b\":\"p2\",\"kind\":\"married\",\"start_year\":1975},{\"type\":\"parent_child\",\"a\":\"p1\",\"b\":\"p3\"},{\"type\":\"parent_child\",\"a\":\"p2\",\"b\":\"p3\"}]."
    }
  }
}

make_genogram output schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title",
    "counts",
    "generation_rule",
    "people",
    "checks",
    "pdf",
    "legend",
    "warnings",
    "downloads"
  ],
  "properties": {
    "pdf": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "shown": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "title": {
      "type": "string"
    },
    "checks": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "counts": {
      "type": "object",
      "required": [
        "people",
        "relationships",
        "couples",
        "parent_links",
        "twin_links",
        "emotional",
        "generations",
        "errors",
        "warnings"
      ],
      "properties": {
        "errors": {
          "type": "number"
        },
        "people": {
          "type": "number"
        },
        "couples": {
          "type": "number"
        },
        "warnings": {
          "type": "number"
        },
        "emotional": {
          "type": "number"
        },
        "twin_links": {
          "type": "number"
        },
        "generations": {
          "type": "number"
        },
        "parent_links": {
          "type": "number"
        },
        "relationships": {
          "type": "number"
        }
      },
      "additionalProperties": false
    },
    "legend": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "people": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    },
    "warnings": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "downloads": {
      "type": "object",
      "properties": {
        "csv": {
          "type": "string"
        },
        "pdf": {
          "type": "string"
        },
        "svg": {
          "type": "string"
        },
        "relations_csv": {
          "type": "string"
        }
      },
      "additionalProperties": false
    },
    "generation_rule": {
      "type": "string"
    }
  },
  "additionalProperties": false
}

make_genogram annotations

{
  "title": "Make genogram",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

check_genogram — Check genogram data

Advertised by the server during the last successful anonymous check.

Advertised read-only

Use this when the user wants a family list checked before drawing a genogram, for example "check my genogram data for mistakes" or "which generation is each person in". Takes the same people, relations and household as make_genogram. Returns the problems found (unknown or duplicate ids, a person who is their own ancestor with the cycle named, more than 2 biological parents, a parent who is not older than the child, couple years outside a partner's life, twins with different parents, too many generations; above 150 people it checks the first 150 and names the people left out), warnings, and each person's generation number when the data is consistent. Draws nothing and makes no files. Relationships only: it does not take health or medical details.

check_genogram input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "people"
  ],
  "properties": {
    "people": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "name"
        ],
        "properties": {
          "id": {
            "type": "string",
            "maxLength": 400,
            "description": "Short unique id, up to 40 characters, used in relations, e.g. \"p1\" or \"maria\"."
          },
          "sex": {
            "enum": [
              "M",
              "F",
              "X",
              "unknown"
            ],
            "type": "string",
            "description": "M (square), F (circle), X (diamond) or unknown (diamond with ?). Default unknown."
          },
          "name": {
            "type": "string",
            "maxLength": 400,
            "description": "Name shown under the symbol, up to 60 characters, e.g. \"Maria Kowalska\"."
          },
          "index": {
            "type": "boolean",
            "description": "true for the index person (the person the genogram is about); drawn with a double line. At most one."
          },
          "deceased": {
            "type": "boolean",
            "description": "true draws an X through the symbol when the death year is not known."
          },
          "birth_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "4-digit birth year, e.g. 1958."
          },
          "death_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "4-digit death year, e.g. 2019. Marks the person as deceased."
          }
        },
        "additionalProperties": {}
      },
      "maxItems": 2000,
      "description": "The people, up to 150. Example: [{\"id\":\"p1\",\"name\":\"Jan\",\"sex\":\"M\",\"birth_year\":1950},{\"id\":\"p2\",\"name\":\"Ewa\",\"sex\":\"F\",\"birth_year\":1952},{\"id\":\"p3\",\"name\":\"Ola\",\"sex\":\"F\",\"birth_year\":1980,\"index\":true}]."
    },
    "household": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 400
      },
      "maxItems": 2000,
      "description": "Ids of the people who live together; drawn with a dashed outline, e.g. [\"p2\",\"p3\"]."
    },
    "relations": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type",
          "a",
          "b"
        ],
        "properties": {
          "a": {
            "type": "string",
            "maxLength": 400,
            "description": "Person id. For parent_child this is the parent, e.g. \"p1\"."
          },
          "b": {
            "type": "string",
            "maxLength": 400,
            "description": "Person id. For parent_child this is the child, e.g. \"p3\"."
          },
          "kind": {
            "type": "string",
            "maxLength": 40,
            "description": "couple: married (default), divorced, separated, cohabiting, engaged. parent_child: biological (default), adopted, foster. twins: identical, fraternal (default). emotional: close (default), distant, conflict, cut_off, hostile."
          },
          "type": {
            "enum": [
              "couple",
              "parent_child",
              "twins",
              "emotional"
            ],
            "type": "string",
            "description": "couple, parent_child (a is the parent, b the child), twins, or emotional."
          },
          "end_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "Year a couple divorced, separated or ended, e.g. 1995."
          },
          "start_year": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991,
            "description": "Year a couple married or began, e.g. 1981."
          }
        }
      },
      "maxItems": 5000,
      "description": "The relationships, up to 600 (at most 150 couples and 100 emotional). Example: [{\"type\":\"couple\",\"a\":\"p1\",\"b\":\"p2\",\"kind\":\"married\",\"start_year\":1975},{\"type\":\"parent_child\",\"a\":\"p1\",\"b\":\"p3\"},{\"type\":\"parent_child\",\"a\":\"p2\",\"b\":\"p3\"}]."
    }
  }
}

check_genogram output schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ready",
    "counts",
    "generation_rule",
    "issues",
    "people",
    "limits"
  ],
  "properties": {
    "ready": {
      "type": "boolean"
    },
    "shown": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "counts": {
      "type": "object",
      "required": [
        "people",
        "relationships",
        "couples",
        "parent_links",
        "twin_links",
        "emotional",
        "generations",
        "errors",
        "warnings"
      ],
      "properties": {
        "errors": {
          "type": "number"
        },
        "people": {
          "type": "number"
        },
        "couples": {
          "type": "number"
        },
        "warnings": {
          "type": "number"
        },
        "emotional": {
          "type": "number"
        },
        "twin_links": {
          "type": "number"
        },
        "generations": {
          "type": "number"
        },
        "parent_links": {
          "type": "number"
        },
        "relationships": {
          "type": "number"
        }
      },
      "additionalProperties": false
    },
    "issues": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    },
    "limits": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "people": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    },
    "generation_rule": {
      "type": "string"
    },
    "people_left_out": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "people_left_out_count": {
      "type": "number"
    }
  },
  "additionalProperties": false
}

check_genogram annotations

{
  "title": "Check genogram data",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

1 advertised

genogram-widget — Zovo Genogram view

Advertised by the server during the last successful anonymous check.

Interactive view for Zovo Genogram.

genogram-widget URI

ui://widget/genogram-v1-1.0.0-e77000d4e961d4c9e70483558dafe8886025b4a02702d58db8a0afbbff868b5a.html

MIME type: text/html;profile=mcp-app

genogram-widget-legacy — Zovo Genogram view (previous versions)

Advertised by the server during the last successful anonymous check.

genogram-widget-legacy URI template

ui://widget/genogram-{version}.html

MIME type: text/html;profile=mcp-app

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 1342 ms
95th percentile latency: 1342 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 8, 2026, 2:47 AM UTC · probe · passed · 1342 ms · metadata changed · 2 tool(s), 1 resource(s), 1 resource template(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http zovo-genogram-mcp https://genogram.zovo.one/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add zovo-genogram-mcp --url https://genogram.zovo.one/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable zovo-genogram-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "zovo-genogram-mcp": {
      "url": "https://genogram.zovo.one/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "zovo-genogram-mcp": {
      "type": "streamableHttp",
      "url": "https://genogram.zovo.one/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start zovo-genogram-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "zovo-genogram-mcp": {
      "type": "http",
      "url": "https://genogram.zovo.one/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http zovo-genogram-mcp https://genogram.zovo.one/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://genogram.zovo.one/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "zovo-genogram-mcp": {
      "serverUrl": "https://genogram.zovo.one/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Zovo Genogram MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 6,072

Zovo Genogram MCP

Endpoint and access

What its tools do

Read-only (2)

Checks and signals

What you can do with it

Source and maintenance

Protocol and capabilities

Server-provided instructions

Tools

Prompts

Resources

30-day availability

Maintenance history

Connect from your client

Claude Code

Codex

Cursor

Cline

VS Code

Gemini CLI

Claude Desktop

Windsurf

Let your agent find its tools

Other productivity and knowledge servers