Integrations

Connect BARK to Claude

Read-only access to the EU regulatory corpus, over OAuth 2.1

BARK’s connector puts the EU regulatory corpus directly inside Claude. Ask a question in plain language, and Claude retrieves the actual provision — the article text, the version in force on a date, the reference chain, the EBA and SFSA guidance behind it — instead of answering from memory.

The connector is read-only. It retrieves regulation. It cannot change anything in BARK, and it never reaches into your own systems.

Before You Connect

You need:

Everyone connects with their own BARK account. Credentials and tokens are never shared between users, and your BARK permissions carry over: the connector can retrieve exactly what your account is entitled to retrieve.

Connect

The server URL is the same everywhere:

https://mcp.barktechnologies.tech/mcp

Claude.ai

  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Set Name to BARK.
  4. Set Remote MCP server URL to the URL above.
  5. Leave OAuth Client ID and OAuth Client Secret blank.
  6. Select Add. You are sent to BARK to sign in with your BARK account and approve the connection, then returned to Claude.

On Team and Enterprise workspaces an owner adds the connector once for the workspace; each teammate then signs in with their own BARK account.

Claude Code

claude mcp add --transport http bark https://mcp.barktechnologies.tech/mcp

Then run /mcp in a session and choose Authenticate.

Codex CLI

codex mcp add bark --url https://mcp.barktechnologies.tech/mcp
codex mcp login bark

What You Can Ask

The connector gives Claude eleven retrieval operations over two sources: the EU regulation graph, and BARK’s library of EBA and SFSA documents. You do not need to name the operations — ask the question, and Claude picks the route.

Read a provision as it stood on a date

Using BARK, show me Article 125 of Regulation (EU) No 575/2013 as it was in force on 21 July 2026, and tell me what changed since the original text.

Retrieves the article and its version chain.

Follow a reference chain

Using BARK, what does Article 92 of the CRR depend on? Trace the references outward two steps and show me where the own funds definitions come from.

Traces dependencies and resolves the definitions behind them.

Find the guidance behind a requirement

Using BARK, find the passage in EBA/GL/2022/14 that covers IRRBB governance and delegation, and quote it with its page number.

Searches the document library and returns the passage with page and source.

Map a concept across regulations

Using BARK, where is “own funds” defined and used across the EU regulations you hold? Show me the definition and the main places it is relied on.

Maps the concept across the corpus.

See what recently changed

Using BARK, what has changed in the regulatory corpus since 1 June 2026?

Sweeps recent amendments corpus-wide.

A tip that improves every answer: tell Claude to use BARK rather than its own knowledge, and to keep BARK’s warnings and citations intact. BARK returns provenance with every result — the source, the version, and any caveat about coverage — and that is what makes an answer checkable.

What BARK Sees

To answer, the connector receives the search terms and identifiers your question produces, and which BARK account is asking. That is what it needs to find the provision.

It does not receive your Claude conversation, your files, or anything from your own systems. BARK’s corpus is published regulation — EU legislation and supervisory guidance — so no customer data is involved on either side.

The service runs in the EU (Google Cloud, europe-north1). Access uses OAuth 2.1; you can revoke the connection at any time from Claude’s connector settings or by contacting us, and revoking it immediately ends the connector’s access to your BARK account.

How BARK handles personal data is described in our Privacy Policy.

If Something Does Not Work

“BARK connector access is not enabled”

Your BARK organisation does not have the MCP module enabled, or your account is disabled. Contact your BARK administrator or us.

The connector cannot reach the URL

Check that you used the exact URL above, with no trailing path and no redirect in front of it.

“Client ID not found”

Remove the connector and add it again. Claude registers a fresh client on the next connection.

Sign-in loops or fails

Confirm you are signing in with the BARK account that belongs to the organisation with MCP enabled, not a personal account.

Support

Email info@barktechnologies.se.