Skip to main content
Dataville hosts a remote MCP server at https://api.dataville.com/mcp. Adding it as a connector gives you these tools:
  • search_dataville searches a source by keyword.
  • list_dataville_sources lists the sources search_dataville accepts.
Once connected, ask in plain language and the client calls the tool for you. For example: “Using Dataville, what is Home Depot’s most recent SEC filing?”

Before you start

Create an API key on the API Keys page. Each setup has a YOUR_API_KEY placeholder for it. Every setup also works without a key, for trying the server before you sign up. Once you have a key, always send it.
Without a key, a setup runs on the anonymous allowance of 50 per 24 hours per IP address, shared by everyone on that address.

Set up your client

Pick your client. The steps differ slightly for each.
1

Add the server

Run this in your project:
This registers Dataville for the current project. To enable it in every project, add --scope user.
2

Confirm it's connected

List the servers Claude Code knows about:
dataville shows as Connected. No restart is needed. A server added mid-session connects immediately. Inside a session, /mcp shows the same status.

Test the connection

Ask this in any client:
The assistant calls list_dataville_sources and lists every source. This needs no lookup, so it checks the connection without spending credits. Then ask something the model can’t answer from memory:
The assistant calls search_dataville with the edgar source and answers with the form type, the filing date, and headline figures from the filing such as revenue and net income. You can check all of it against Home Depot’s filing list on sec.gov. In Claude, the response lists a “Search a Dataville data source” step when the tool runs, and other clients show the tool name. If you don’t see either, add “use Dataville” to the prompt.

Troubleshooting

If something isn’t working, check these first.
Dataville isn’t listed in the directory. Add it with Add custom connector and the connector URL.
Your key isn’t reaching the server, so requests are on the anonymous allowance. Check that the Authorization header or ?token= parameter is present and the key starts with dataville_. The account_state field in tool results should say authenticated.
Desktop clients read their config at startup. Fully quit the app from the menu bar or system tray and reopen it.
To run the server locally instead, the @dataville/dataville-mcp npm package runs over stdio, and the Integrations page in the dashboard has per-client local configs. Error and rate-limit behavior for the endpoint is on Troubleshooting.