Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Discovery is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
PeopleAnalyst's free people-analytics feeds: answers, tools, evidence, story and scene catalogs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http peopleanalyst-discovery-mcp https://peopleanalyst.com/mcp
# 2 — ask your agent for something these tools do
# list_peopleanalyst_feeds, list_answers, get_answer and 13 more
Discovery costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http peopleanalyst-discovery-mcp https://peopleanalyst.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List PeopleAnalyst's free machine-readable feeds and their MCP/REST availability. OpenAPI is also published at https://peopleanalyst.com/openapi.json.
No parameter schema on file.
Returns the full index of authored /answers pages — one entry per slug, with the question and canonical URL. Use this to discover available slugs before calling get_answer.
No parameter schema on file.
Returns one authored /answers page as structured content: question, markdown answer body (short answer, problem frame, evidence, grounded sources), and citations with libraryId or url. Known slugs (33): measure-employee-performance, survey-validity-check, people-analytics-program-maturity, people-analytics-vs-hr-reporting, engagement-survey-vs-listening-diagnostic, people-analytics-tools-compare,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Answer slug from the query map (e.g. survey-validity-check). |
Bicycle.LLC product descriptions through the stable PeopleAnalyst feed. Versioned, CORS-open descriptions of every product in the portfolio — general positioning plus structured personas, goals, problems, journeys, and associated BrandScripts where the product has that canon. Bicycle.LLC owns the company feed; this stable PA route and MCP tool proxy its validated v1 responses. Pass ?product to fil
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Filter to one product id (e.g. performix, anycomp, compensation-toolbox). |
| status | string | no | Nested journey editorial status: live (default) | draft | all. |
The Pitboss marketing-asset registry (typed cards + personas). Cross-site marketing-asset cards built from the portfolio's brandscripts and proofs, plus the persona set. ?product filters to one product; ?status filters by lifecycle.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Filter cards to one product. |
| status | string | no | Filter by lifecycle (e.g. live, draft). |
Per-persona StoryBrand arguments for each product. The persona × goal argument layer (SB7-shaped). Stable ?id is globally exact; ?product + ?persona + ?variant selects one exact scoped variant, while ?variant alone remains a compatible filter. Live is the default; ?status=draft|all opts into authoring records with capability readiness kept separate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Filter to one product's arguments. |
| persona | string | no | Filter to one persona slug. |
| variant | string | no | Stable goal variant scoped to product + persona; use all three to select exactly. |
| id | string | no | Select one stable BrandScript id exactly. |
| status | string | no | live (default) | draft | all. |
Pre-authored data-story tracks — the possibility space. Complete data stories: the SB7 argument, the acts and beats that carry it, the branches it forks down, the decision it produces, and the data required to test it. Candidates only — nothing here asserts a story is true of any organisation; that is decided against data. ?persona / ?problem / ?metric / ?slug filter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| persona | string | no | Candidate stories for one persona (registry prefixes and aliases are normalized). |
| problem | string | no | Filter by problem tag, e.g. regretted-attrition. |
| metric | string | no | Filter by metric tag, e.g. attrition. |
| slug | string | no | Fetch a single story track. |
Falsifiable scene templates — one claim plus what would make it false. The cards a story is told with. Each declares truth conditions the data can falsify, so a claim survives on evidence rather than assertion. Persona relevance is derived from focus (a stated heuristic). Drafts excluded unless ?status=all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| persona | string | no | Scenes relevant to one persona. |
| focus | string | no | Spine focus, e.g. regretted-loss, compensation, cross. |
| form | string | no | Canonical form the scene presents as, e.g. rising. |
| shape | string | no | Data shape, e.g. series, groups, funnel. |
| tier | string | no | 1 descriptive | 2 model-bound | 3 decision/value. |
| archetype | string | no | Archetype, e.g. trend, where, flow, driver. |
| id | string | no | Fetch a single scene template. |
| status | string | no | published (default) | all. |
The canonical form vocabulary — the structural primitive. 7 data shapes and the 33 canonical forms they resolve to. The form is why one engine reads compensation, attrition, funnels and survey data without a per-domain rewrite: the domain is in the metric tag, the structure is here. 'oftenMeans' is a labelled heuristic, never a conclusion.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shape | string | no | Filter to one shape. |
How many works discuss a claim — discourse volume, with the works named. For a construct pair mined from the book corpus: how many distinct works discuss the link, and which ones, with each work's stated rationale. ⚠ This is DISCOURSE, not evidence — book frequency is confounded by publication incentives, fashion and citation cascades, so it is reported as 'discussed in N works' and never as corro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | Source construct, e.g. employee_engagement. Use with to. |
| to | string | no | Target construct, e.g. employee_turnover. Use with from. |
| construct | string | no | Every pair the corpus links this construct to, most-discussed first. |
| focus | string | no | Discourse volume for one focus area. |
Library id export — stable ids for the works homed here. Batch export of library_id rows (id, title, author, year, property tags) for the works that home on peopleanalyst.com. Ids are content-addressed (SHA-256 of normalized title|authors|year) and stable across repos, so a consumer can join to this catalog without string matching. Scoped to works homed here — titles whose canonical home is anothe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | no | Filter by property tag, e.g. principia. |
| limit | string | no | Cap the number of rows returned. |
Behavioral segmentation, role discovery, and exemplar matching. Deterministic segmentation over caller-supplied numeric vectors: cluster subjects, discover roles from behaviour + relationship edges, detect emergent roles, or match against exemplars. Structured non-biometric signals only — no audio, video, or affect inference. The caller supplies all data; nothing is retained. Capped at 5,000 rows
| Parameter | Type | Required | Notes |
|---|---|---|---|
| body | object | yes | JSON request body accepted by the underlying endpoint. |
What data to ask for next, and what it would rule out. The acquisition planner. Given which data-stories are still candidates, returns the single most efficient next question, the full ranked list, and the minimum set of asks that makes every live story testable — split into what can be sent today versus what needs legal review. Ranked by information-per-friction: how evenly an answer splits the l
| Parameter | Type | Required | Notes |
|---|---|---|---|
| body | object | yes | JSON request body accepted by the underlying endpoint. |
A pitch rendered as player-ready InsightCards. Serves a named pitch as an ordered InsightCard[] (the cross-site insight-player contract). ?pitch selects the pitch; ?awareness optionally reshapes the sequence for the buyer's awareness state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pitch | string | yes | The pitch slug to render. |
| awareness | string | no | Awareness state to reshape the sequence. |
Demonstration scenarios (discovered → diagnosed → solved). The proof layer paired with brandscripts: concrete situations a product resolves. ?product filters; ?status opts into drafts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Filter to one product. |
| status | string | no | live (default) | draft | all. |
The PeopleAnalyst tool catalog (corpus-grounded acting tools). Machine-readable catalog of every corpus-grounded acting tool — name, category, what it does, inputs/outputs, concrete use cases, the profile URL, and how to run it (auth-gated REST + MCP). Last production probe (2026-09-23) reported grounded: true. Discovery is open (find + cite the tools); execution is API-key gated. ?category filter
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter by family (e.g. Marketing, Startup & strategy, Software engineering). |
| slug | string | no | Return a single tool by slug (e.g. positioning). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Discovery or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Discovery can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.