Skip to content

Developers

UK company intelligence your agent can call.

Developer overview for DataGardener MCP: a remote Model Context Protocol server with OAuth authorisation, read-only task-level tools across twelve UK intelligence layers, a built-in query knowledge base, and usage reported with results.

How MCP fits

A remote server your MCP host already knows how to talk to.

Your host (Claude, or any MCP client that supports remote servers) connects to DataGardener MCP over HTTPS, discovers its tools, and lets the model call them. You do not write integration code for each dataset; you add one server and the model learns the tools from their definitions.

# Conceptual flow
host ──(MCP over HTTPS, OAuth)──▶ DataGardener MCP
      ◀── tools/list: 34 tools across 12 layers
model ──▶ tools/call search_companies {...}
      ◀── structured result + usage
model ──▶ tools/call search_ukgaap {company_registration_number}
      ◀── filed financials + source + period

Tested today with Claude (web, desktop and mobile, via Connectors). Any MCP client that supports remote servers with OAuth authorisation can connect. Clients beyond those listed are not yet tested by DataGardener.

Design principles

  • Task-level tools

    Search tools accept plain parameters such as region, county, industry or value band. Query tools accept full DSL for anything a search cannot express. The agent picks the lightest tool that answers the question.

  • Server-side defaults

    Dissolved and dormant companies are excluded by default from company queries unless the user asks for them, so results reflect the live business population.

  • Read only

    Every tool reads. The server rejects write operations, so an agent can investigate freely without being able to change anything.

  • Entitled access

    Identity travels with the OAuth connection. An agent sees the modules its DataGardener entitlement allows and nothing else.

  • Metered by record

    Record-returning tools are metered per company record returned. Describe and count tools are designed to be used freely before an agent commits to a larger pull.

  • Knowledge base first

    A built-in knowledge base returns the correct field names, nesting rules and KPI templates, so an agent writes correct queries rather than guessing at a schema.

Tool families

12 families, 34 tools, one entitlement.

Developer questions

What transport does DataGardener MCP use?

DataGardener MCP is a remote MCP server. Clients connect over HTTPS using the Model Context Protocol with OAuth authorisation. A legacy login-link flow exists for older SSE connections.

Do I pass a session token?

On OAuth connections, no. The server reads identity from the connection's bearer token. Tools still accept a legacy session_token argument for older connections; pass an empty string on OAuth connections.

How do I write a correct query?

Call query_knowledge_base with a plain description of what you want. It returns the field names, nesting rules and query pattern to use with the execute_* tools.

What happens on an error?

Tool errors are returned as MCP tool results with a message. Typical causes are a malformed DSL body, an unknown field, or a module the connection is not entitled to. The agent can read the message and retry.

Are dissolved companies included?

Not by default. Company queries exclude dissolved and dormant companies unless the user explicitly asks for them.

Build on an operated intelligence layer.

Talk to DataGardener about agent access, design partnerships or OEM terms.