opendata_plugins_draft
Build a validated plugin YAML spec from structured inputs. Takes id, baseurl, tool definitions (name, endpoint, params), and registry metadata. Validates id/tool-name casing, path-placeholder/param consistency, and parameter types, then emits a YAML string ready to feed into opendatapluginscreate. U
How to use it
opendata_plugins_draft is exposed by the Meta Data MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the opendata_plugins_draft tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL META DATA MCP LISTINGOther tools in Meta Data MCP (12)
Enumerate the controlled domain vocabulary (health, legal, finance, earth-science, …).
Show the scoring breakdown for a search (useful for debugging routing decisions).
Return per-provider health scores used by discovery health badges and routing context.
Autonomously create a new plugin. Takes a YAML spec (typically produced by opendatapluginsdraft), runs the generator, imports the new module, registers it in the live registry, and hot-loads its tools onto the running server. Use this when opendataprovidersfind returns no match.
Activate one provider so its tools become callable in this session.
Remove an activated provider's tools from the current session catalog.
Full metadata for one plugin by id — title, description, domains, regions, keywords, homepage, required env vars.
Free-text search over the plugin registry. Returns ranked matches. When nothing matches the response carries a nomatch: true flag and a nextstep hint pointing at opendatapluginsdraft + opendatapluginscreate.
Paginated dump of the whole registry.
List currently active providers and the tool names each contributes.
Enumerate the controlled region vocabulary (us, eu, uk, global, …).
Proxy-call an activated plugin tool by name for environments that cannot directly invoke dynamically added tools.