Compabase MCP Server

MCP server for 3M+ Polish companies — KRS & CEIDG financials, ownership, and industry search.

Local serverstdio

What is the Compabase MCP server?

Compabase MCP server exists for a simple reason — assistants are far more useful when they can act on Compabase directly instead of describing what you should do. MCP server for 3M+ Polish companies — KRS & CEIDG financials, ownership, and industry search.

What you get

Ask your AI about Polish business in plain language: company financials, ownership structures, industry rankings, board members, and more — all backed by real registry data.

This is the MCP server for Polish companies data. Instead of building API integrations yourself, you connect your AI assistant to the Compabase MCP endpoint and talk to it naturally:

What the assistant can call

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

  • search_companies — Supports filtering by: name, KRS, NIP, city, county, voivodeship, postal code, PKD industry code (primary or any), legal form, revenue, net profit
  • count_companies — The count_companies tool exposed by this server
  • get_company — The get_company tool exposed by this server
  • get_financials — Includes: revenue_total, profit_net, profit_sales, ebitda, total_assets, currency, fiscal period dates
  • get_company_people — The get_company_people tool exposed by this server
  • execute_sql — The execute_sql tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Compabase's toolset — search_companies, count_companies, get_company and 3 more — is a fair guide to whether it matches your workflow. It is maintained by ContentWriterco; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Compabase's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the compabase mcp server does with a few real requests.

Available tools

ToolWhat it does
search_companiesSupports filtering by: name, KRS, NIP, city, county, voivodeship, postal code, PKD industry code (primary or any), legal form, revenue, net profit, operating profit, EBITDA, total assets, share capital, estimated value,
count_companiesThe count_companies tool exposed by this server.
get_companyThe get_company tool exposed by this server.
get_financialsIncludes: revenue_total, profit_net, profit_sales, ebitda, total_assets, currency, fiscal period dates.
get_company_peopleThe get_company_people tool exposed by this server.
execute_sqlThe execute_sql tool exposed by this server.

How to install the Compabase MCP server

{
  "mcpServers": {
    "compabase": {
      "url": "https://compabase.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mcpk_YOUR_KEY_HERE"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Compabase to search companies.
  • Use Compabase to count companies.
  • Use Compabase to get company.

Frequently asked questions

It connects Compabase to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (search_companies, count_companies, get_company, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Compabase directly.