Agenten stärken
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
https://api.dataville.com/mcpDie Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
claude mcp add --transport http com.dataville-dataville-mcp https://api.dataville.com/mcpRun in a terminal.
{ "mcpServers": { "com.dataville-dataville-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.dataville.com/mcp" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenMCP server exposing Dataville's data source API as tools for MCP clients (Claude Desktop, Claude Code, etc.).
Dataville is a unified REST API over ten public datasets — Wikipedia, arXiv, Project Gutenberg, US Census, USDA FoodData, Papers with Code, SEC EDGAR, OpenAlex, PyPI, and Stack Exchange — behind one interface and one API key, with CSV/Parquet export and SQL query support. This package lets an MCP client search any of those sources as a tool call.
Requires a Dataville API key — get one from the Dataville dashboard.
Docs: docs.dataville.com · Connect an AI tool · Data sources. Examples: dataville-wikimedia, dataville-sec-edgar, company-intelligence-agent. Live demos: app.dataville.com/demos.
All four only read data. query_dataville covers every stored source except
census and news, which are fetched live per search. It returns at most
1,000 rows per call and is billed per row returned. It reads Dataville's stored
copy: some sources are loaded in bulk, others only hold records fetched before,
so for one specific item search_dataville is the reliable route.
Once connected, ask in plain language and the client picks the source:
requests package on PyPI — what's the latest version and license?"This package is a local (stdio) MCP server: the client launches it on your
machine via npx. If you don't need it running locally, connecting to
Dataville's hosted endpoint instead takes one line and no install.
Dataville also serves MCP directly over HTTP, so a client can connect without running anything locally — no Node, no config file, no restart:
claude mcp add --transport http dataville https://api.dataville.com/mcp
That works with no credentials at all (anonymous limits). Add
--header "Authorization: Bearer dataville_your_key_here" for the full quota.
Cursor and VS Code users can use the install buttons at the top of this page.
Other clients take the same URL; the app's Integrations page has the exact
snippet for each. Use the hosted endpoint unless you specifically want to pin a
version or work offline — the rest of this section covers that local setup.
npx. Without it the server
fails to start. Check with node --version.The config block is the same everywhere; only where you put it differs:
{
"mcpServers": {
"dataville": {
"command": "npx",
"args": ["-y", "@dataville/dataville-mcp"],
"env": {
"DATAVILLE_API_KEY": "dataville_your_key_here"
}
}
}
}
No install step needed — npx fetches and runs the package on demand.
claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonmcpServers if the file already has one),
with your real key.dataville running.Note: the server appears as tools, not in the Connectors directory — that directory only lists remote (hosted) connectors and will not find a local server. Ask naturally ("get Apple's latest revenue from dataville") and the client calls the tool.
claude mcp add dataville -e DATAVILLE_API_KEY=dataville_your_key_here -- npx -y @dataville/dataville-mcp
Restart the session so the tools load. Add -s user to make it available in
every project instead of just the current one.
DATAVILLE_API_BASE_URL is optional and defaults to https://api.dataville.com;
set it to http://localhost:5000 to point at a local backend during development.
The server reads DATAVILLE_API_KEY from its environment and sends it only as
an Authorization: Bearer header to DATAVILLE_API_BASE_URL, which is
https://api.dataville.com unless you change it. It never logs the key or sends
it anywhere else. The base URL must use https. Plain http is accepted only
for localhost, 127.0.0.1 and [::1], so the key never crosses the network
unencrypted.
All four tools are read-only: they search and query Dataville and never create, change or delete anything.
git clone https://github.com/datavilleorg/dataville-mcp.git
cd dataville-mcp
npm install
npm run build
Ask your client one of these. Each answer is checkable on purpose — a model that skipped the tool and answered from memory sounds just as confident, so a reply on its own proves nothing.
Clients show when a tool ran. If you don't see that, say "use dataville" in the prompt to make it explicit, and check the answer against the source.
npm run dev # tsx watch
npm test # node test runner
npm run build # tsc
Publishes run from CI. npm uses trusted publishing (OIDC), so no npm token is
stored; the MCP Registry step signs in with the MCP_PRIVATE_KEY repo secret.
To cut a release: bump the version, update CHANGELOG.md, then publish a GitHub
Release for the new tag. The Publish workflow builds, tests, and publishes to npm,
then publishes server.json to the MCP Registry
(its version is set from package.json, so don't bump it by hand).
The registry name com.dataville/dataville-mcp is authorized by a DNS TXT record
on the dataville.com apex (v=MCPv1; k=ed25519; p=<public key>), checked
against the Ed25519 private key in the MCP_PRIVATE_KEY repo secret (hex). If the
mcp-registry job fails at login, check that record and secret, then re-run just
that job.
SEC filings, Wikipedia, arXiv, US Census and more for AI agents, with every answer source-linked.
{ "mcpServers": { "com.dataville-dataville-mcp": { "url": "https://api.dataville.com/mcp", "headers": {} } }}2 Tools
FAQ
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: DATAVILLE_API_KEY, DATAVILLE_API_BASE_URL.
Dataville wird über HTTP erreicht.
Zuletzt geprüft: 2026-10-23. SEC filings, Wikipedia, arXiv, US Census and more for AI agents, with every answer source-linked.