Fedlex Connector vs Kentucky Code

A side-by-side look at the Fedlex Connector and Kentucky Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Fedlex Connector logoFedlex ConnectorLegal · Remote HTTP/SSESearch Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.59GoodAuth: not declaredKentucky Code logoKentucky CodeLegal · Local subprocess (stdio)Kentucky Revised Statutes (KRS) — state statutes by citation and by topic.61GoodAuth: no auth required

Verdict: choose Fedlex Connector for legal work over a hosted endpoint; choose Kentucky Code for legal as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Fedlex Connector logoChoose Fedlex Connector when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like search_by_title, get_article, get_law_text.
Explore Fedlex Connector

Kentucky Code logoChoose Kentucky Code when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like ky_statute, ky_search.
Explore Kentucky Code

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFedlex Connector logoFedlex ConnectorKentucky Code logoKentucky Code
CategoryLegalLegal
Quality signal59/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars70
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools42

Tools & capabilities

Fedlex Connector tools 4

  • search_by_titleSearch Swiss federal legislation titles in the Classified Compilation (RS/SR) on Fedlex. Use to find the RS number of a law when you know its name but not its number. Searches titles only, not article content. Returns only acts currently in force.
  • get_articleRetrieve a single article when you already know the EXACT article number (e.g. from a cross-reference). Do NOT call this tool repeatedly to search for provisions — use get_law_text instead to fetch the full act or a section and locate relevant articles in the text.
  • get_law_textRetrieve the official consolidated text of a Swiss federal act (or a specific title/chapter) directly from Fedlex (fedlex.admin.ch). This is the PRIMARY tool for answering Swiss law questions — always start here. Fetch the full act or a specific section, then locate relevant provisions in the returned text. Prefer this over get_article unless you already know the exact article number.
  • list_amendmentsList consolidation version dates for a Swiss federal act. Returns the dates each consolidated version took effect.

Kentucky Code tools 2

  • ky_statuteGet the FULL TEXT of a section of the Kentucky Revised Statutes (KRS) — Kentucky state law — by citation. "507.020" is murder; "383.580" is the landlord security-deposit statute. Accepts natural forms: "507.020", "KRS 507.020", "§ 507.020". Returns the current statutory text, the catchline, the "Effective:" date, and the legislative "History:" (the Acts that enacted and amended it). Kentucky publishes the CURRENT text only — a prior (pre-amendment) version's text is not available online, only its existence; this tool says so rather than guessing. Keyless. Use for "what does KRS 507.020 say" or to check a Kentucky statute a case or contract relies on.
  • ky_searchSearch the Kentucky Revised Statutes BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Real full-text search over the statutory body text, not just catchlines: a query like "landlord" surfaces KRS 383.580 ("Security deposits") even though that catchline contains neither word. Returns matching citations and catchlines; call ky_statute with a citation for the full text. Keyless.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Fedlex Connector

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fedlex-connector": {
      "url": "https://mcp.fedlex-connector.ch"
    }
  }
}

Kentucky Code

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kentucky-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-kentucky-code"
      ]
    }
  }
}

Frequently asked questions

Fedlex Connector is categorized under Legal and uses a remote HTTP/SSE transport. Kentucky Code belongs to Legal and uses a local stdio subprocess. Pick Fedlex Connector for legal work and Kentucky Code for legal.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Fedlex Connector has no declared pricing — check the project's own site. Kentucky Code is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add fedlex-connector and kentucky-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Fedlex Connector has a quality signal of 59/100 (Good) with 2 views, 0 installs and 7 GitHub stars. Kentucky Code has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.