DataFinder MCP

What this does

DataFinder MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

DATAFINDER_AK
DATAFINDER_SK
DATAFINDER_PROJECT_ID
DATAFINDER_APP_ID
DATAFINDER_SUBJECT_ID
DATAFINDER_ALLOW_PROJECT_WIDE
DATAFINDER_DB_PATH
DATAFINDER_LOCAL_OWNER
DATAFINDER_ALLOW_LOCAL_WRITES
DATAFINDER_ALLOW_UPSTREAM_WRITES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install DataFinder MCP?

Run the Claude Code command in the install section to add DataFinder MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with DataFinder MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to DataFinder MCP as well.

Does DataFinder MCP need an API key?

Yes. Before it can run, set these environment variables: DATAFINDER_AK, DATAFINDER_SK, DATAFINDER_PROJECT_ID, DATAFINDER_APP_ID, DATAFINDER_SUBJECT_ID, DATAFINDER_ALLOW_PROJECT_WIDE, DATAFINDER_DB_PATH, DATAFINDER_LOCAL_OWNER, DATAFINDER_ALLOW_LOCAL_WRITES, DATAFINDER_ALLOW_UPSTREAM_WRITES. They go in the env block of your MCP config.