Claude Demographic and Health Surveys connectorWhat Claude can do in your Demographic and Health Surveys account.
The Claude Demographic and Health Surveys connector exposes 14 tools. All 14 read, 0 write and 0 are undocumented. Below: which public health indicators Claude can pull, how it narrows a question before fetching numbers, and what stays out of reach.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query DHS indicators
The DHS Program covers more than 90 countries and 450+ nationally representative household surveys on population, health and nutrition. With this connector you ask a question in plain words, and Claude finds the right indicator, checks which surveys hold it, then fetches the aggregate figures with a citation of survey, country and year.
From a topic to the right indicator. You know you want the total fertility rate but not its code: search_dhs_indicators_by_text suggests likely indicator IDs, and get_dhs_indicator_profile shows the metadata of the one you pick.
Check before you pull. get_dhs_data_availability summarizes which countries, surveys, years and breakdowns exist, so Claude does not ask for rows that are not there.
Figures you can cite. search_dhs_indicator_data then returns bounded results, which can be split by sex, age, residence or wealth.
What it does not do. No individual survey record is ever exposed: access to microdata still goes through DHS's own registration process. Everything here is aggregate and read-only, according to ICF, the publisher. And Claude only works while it answers you; no report refreshes itself when DHS publishes new data. A recurring extract belongs to an automation tool, which does a different job, and the Integrations hub covers that side. For a connector that writes into a business tool, compare with the Claude agility-cms connector.
Five words before your first query
Claude's vocabulary for this connector, in a minute.
- Connector
- The link you set up once between Claude and a service, so Claude can draw on it while it answers your questions.
- Tool
- One named task the connector lets Claude perform. Claude picks the tools it needs by itself; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use. It is given once per person and can be withdrawn.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation at that moment.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude query an outside service such as the DHS Program.
Connect the DHS Program to Claude in three steps
- 01
Open the connector list
In Claude's settings, go to Customize, then Connectors, and find Demographic and Health Surveys. On a Team or Enterprise workspace, an Owner or Primary Owner enables a connector before members can each connect to it.
- 02
Start the connection
Click Connect on its row and, if the service opens a window of its own, complete the sign-in there. If the link breaks later, Disconnect and connect again; the same switch removes the access.
- 03
Check the authorization
When an authorization screen appears, read it before accepting. It belongs to the service, not to Claude, and it is what sets what the access covers. You can take that access back later from the same place.
The 14 tools, all for reading public data
Demographic and Health Surveys gives Claude 14 tools: 14 that read your account, 0 that change something in it.
Grouped by what they do. Tool names stay exactly as Claude shows them.
- 14 read
What Claude reads (14)
14 toolsFourteen tools that look up DHS metadata and aggregate figures, and change nothing.
list_dhs_countries
Gives Claude the countries covered by the DHS Program, one of the three core filters every data request is built on.
list_dhs_surveys
Returns the surveys Claude can filter on, the second of the core filters alongside countries and indicators.
list_dhs_indicators
Lays out the indicators available, the third core filter, so Claude can pick a valid ID from the list rather than guess one.
search_dhs_indicators_by_text
Turns a plain-language description into likely indicator IDs, which is how Claude bridges your wording and DHS codes.
get_dhs_indicator_profile
Opens the metadata of an indicator whose ID is already known, so you see exactly what a figure measures before it lands in a report.
list_dhs_tags
Part of the set ICF describes only as discovering supporting resources. The publisher's workflow advice does mention tag IDs among what discovery tools help settle, but it never says which tool returns them, so this page does not either.
list_dhs_survey_characteristics
Another of the supporting-resource tools in the publisher's grouping. ICF gives it no individual description beyond that, so this page does not detail what each entry contains.
resolve_dhs_filters
Normalizes the names and IDs you mention (country names, survey types, survey IDs, indicator IDs) into values the data tools accept.
search_dhs_indicator_data
Retrieves the actual DHS figures for normalized filters, kept within bounds so results stay readable, each with its survey, country and year.
get_dhs_data_availability
Summarizes the countries, surveys, years and breakdowns that hold an indicator before any detailed rows are requested, which saves empty answers.
list_dhs_datasets
One of six tools ICF groups under supporting resources, with nothing more said about its output. The name is all the documentation gives, and this page draws no content from it.
list_dhs_publications
Sits in the same supporting-resource family. The documentation names it and stops there, so this page leaves its exact fields alone rather than guessing them from the name.
list_dhs_geometry
The one supporting-resource tool whose subject ICF touches on: request geometry only when your workflow needs geographic metadata.
list_dhs_data_updates
Closes the supporting-resource set. No source tells what an entry in it looks like, and nothing says Claude watches it for you: Claude only calls it when you ask a question.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account on someone's behalf. These fourteen tools only read, and no source describes a confirmation attached to any one of them.
ICF's own advice is to leave approval prompts on until you have verified the server and the exact tools your work uses. On Team and Enterprise, owners decide whether members may let some actions through without a prompt, and they can restrict what a connector does for the whole organization, for example by leaving reading open and closing writing; that setting applies to everyone. Claude works with the access of the person who connected, nothing beyond.
Which plans can use it
None of the 819 sheets in the official directory shows plan availability. For this connector, as for all the others, that answer is published nowhere.
What is documented is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. The current state of this one is on its sheet in the official directory, the only place kept up to date.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing runs when a new survey is released.
ICF describes all fourteen tools as read-only, but a reading-only list is still an observed floor rather than a guarantee: an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor vouches for how they behave. Everything on this page comes from ICF's documentation; no Claude help article covers this connector.
Need help connecting Demographic and Health Surveys to Claude?
A person reads every message.
