Opendatasoft MCP Server

Created By
Mark-Friesea year ago
Overview

What is Opendatasoft MCP Server?

The Opendatasoft MCP Server is a Model Context Protocol (MCP) server that facilitates interaction with the Opendatasoft Explore API v2.1, enabling AI assistants to search, query, and analyze open datasets.

How to use Opendatasoft MCP Server?

To use the Opendatasoft MCP Server, install it from source, configure it with your environment variables, and integrate it with an MCP-compatible client like Claude for Desktop.

Key features of Opendatasoft MCP Server?

  • Dataset Discovery: Search and browse datasets by keywords, publishers, and themes.
  • Dataset Exploration: View schemas, metadata, and sample records.
  • Data Querying: Execute ODSQL queries with filtering, sorting, and aggregation.
  • Data Analysis: Generate statistics, analyze fields, and visualize distributions.
  • Data Export: Generate export URLs for various formats (CSV, JSON, GeoJSON, etc.).

Use cases of Opendatasoft MCP Server?

  1. Searching for datasets related to specific topics.
  2. Analyzing data distributions and statistics.
  3. Exporting datasets in various formats for further analysis.

FAQ from Opendatasoft MCP Server?

  • What is the ODSQL?

ODSQL is the Opendatasoft Query Language used for filtering, aggregating, and sorting data.

  • What are the requirements to run the server?

You need Python 3.10 or later and the Model Context Protocol (MCP) SDK 1.2.0 or later.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Mark-Friese
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago