{
  "markdown": "# mcp-dados-pt\n\ndados.gov.pt MCP — Portugal's national open data portal.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1481+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `search_datasets` | Search datasets on dados.gov.pt, Portugal's national open data portal (Portuguese government open data). Returns matching datasets with title, description, publishing organization, and downloadable-resource counts. |\n| `get_dataset` | Fetch a single dataset from dados.gov.pt (Portuguese government open data) by its id or slug, including full description, license, update frequency, tags, and the list of downloadable resources (files) with formats and URLs. |\n| `list_organizations` | List or search the organizations (Portuguese government bodies and other publishers) that publish open data on dados.gov.pt, with their dataset counts and portal pages. |\n| `recent_datasets` | Get the most recently published datasets on dados.gov.pt, Portugal's national open data portal (Portuguese government open data), sorted newest first. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"dados_pt\": {\n      \"url\": \"https://gateway.pipeworx.io/dados_pt/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/dados_pt/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1481+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Dados Pt data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3125,
  "sha": "eb4d8b53a9e16db257489275d9c9b630b7b2b277269d8fa2c9c5a503b5671130",
  "repo_slug": "pipeworx-io/mcp-dados-pt",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_dados_pt_2f6c4000/readme"
}