Finbud MCP Server

The official MCP Server for the Finbud Data API

Local serverstdioTypeScript

What is the Finbud MCP server?

Finbud MCP server exists for a simple reason — assistants are far more useful when they can act on Finbud directly instead of describing what you should do. The official MCP Server for the Finbud Data API.

What you get

This library provides convenient access to the Finbud Data REST API from server-side TypeScript or JavaScript.

What the assistant can call

Once Finbud is connected, these are the calls the assistant has available:

  • Retries — Certain errors will be automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network
  • Timeouts — Requests time out after 1 minute by default. You can configure this with a timeout option:
  • Logging — The Logging tool exposed by this server

Configuration and credentials

You will need one environment variable: FINBUD_DATA_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

TypeScript >= 4.9 is supported. The following runtimes are supported: - Web browsers (Up-to-date Chrome, Firefox, Safari, Edge, and more) - Node.js 18 LTS or later (non-EOL) versions. - Deno v1.28.0 or higher. - Bun 1.0 or later. - Cloudflare Workers. - Vercel Edge Runtime. - Jest 28 or greater with the "node" environment ("jsdom" is not supported at this

Setting it up

Installation goes through your MCP client rather than a global install: point it at finbud-data on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Finbud's toolset — Retries, Timeouts, Logging — is a fair guide to whether it matches your workflow. It is maintained by glaksmono; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the finbud mcp server does with a few real requests.

Available tools

ToolWhat it does
RetriesCertain errors will be automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict, 429 Rate Limit
TimeoutsRequests time out after 1 minute by default. You can configure this with a timeout option:
LoggingThe Logging tool exposed by this server.

How to install the Finbud MCP server

{
  "mcpServers": {
    "finbud-data": {
      "command": "npx",
      "args": ["-y", "finbud-data"],
      "env": {
        "FINBUD_DATA_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

TypeScript >= 4.9 is supported. The following runtimes are supported: - Web browsers (Up-to-date Chrome, Firefox, Safari, Edge, and more) - Node.js 18 LTS or later (non-EOL) versions. - Deno v1.28.0 or higher. - Bun 1.0 or later. - Cloudflare Workers. - Vercel Edge Runtime. - Jest 28 or greater with the "node" environment ("jsdom" is not supported at this

VariableDescriptionRequired
FINBUD_DATA_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Finbud to Retries.
  • Use Finbud to Timeouts.
  • Use Finbud to Logging.

Frequently asked questions

It connects Finbud to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Retries, Timeouts, Logging) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Finbud directly.