Connect and authenticate
Add the server. Authorise. Ask.
How to connect an MCP client to DataGardener MCP: add the remote server URL, authorise with OAuth so identity is bound to the connection, confirm the tool list, and run a first query. Legacy login-link flow for older SSE connections.
1. Get an entitlement
DataGardener MCP access is tied to a DataGardener customer entitlement. Existing platform customers ask their account contact to enable agent access; new customers start with a demo or design-partner conversation.
2. Add the remote server
In Claude, open Settings, then Connectors, and add a custom connector with the DataGardener MCP server URL. Other MCP clients that support remote servers take the same URL in their MCP server configuration.
Server URL: provided with your entitlement
(TODO: set NEXT_PUBLIC_MCP_ENDPOINT once the public URL is confirmed)3. Authorise with OAuth
On first use the client opens the DataGardener consent screen. Sign in with your DataGardener account. From then on, identity travels with the connection’s bearer token. You never paste a key into a conversation, and tools accept an empty session_token argument on OAuth connections.
Older SSE connections use a login-link flow instead: the server returns a link, you sign in once, and a session token is stored by the client. If a tool ever replies that you are not logged in, the client falls back to that flow.
4. Confirm the tool list
Your client should list the DataGardener MCP tools, for example search_companies, execute_query, search_contracts, search_ukgaap, search_psc. If the list is empty, the connection has not been authorised or the entitlement has not been enabled.
5. Run a first query
Prompt: "Find live precision engineering companies in the West Midlands."
→ tools/call search_companies
{ query: "precision engineering", region: "west midlands",
company_status: "live", size: 10 }
← Found N matching companies (showing top 10)
each with name, registration number, status, industry,
location, size band, company age
usage reported with the response6. Set tool permissions
Hosts such as Claude let you choose, per tool, whether to always allow, ask first, or block. DataGardener MCP tools are read-only, so a common setting is to allow search, describe and count tools and to ask before execute_* tools that can return larger record sets.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| No tools appear | OAuth not completed, or entitlement not enabled | Reconnect and complete consent; contact DataGardener support |
| “You are not logged in” | Legacy SSE connection without a session | Follow the login link the server returns, or switch to the OAuth URL |
| A module returns nothing | The connection is not entitled to that module | Check your entitlement with your account contact |
| Query error on execute_* | Malformed DSL or unknown field | Call query_knowledge_base first and reuse the returned pattern |
| Counts differ from the web platform | Default filters exclude dissolved and dormant companies | Ask explicitly to include them if needed |
At a glance
- Transport
- Remote MCP over HTTPS
- Authorisation
- OAuth; legacy login-link for SSE
- Identity
- Bound to the connection
- Access
- Read-only tools; writes rejected
- Entitlement
- Per customer, per module
- Usage
- Reported with results
- Tested clients
- Claude (web, desktop and mobile, via Connectors)
- Support
- support@datagardener.com
Any MCP client that supports remote servers with OAuth authorisation can connect. Clients beyond those listed are not yet tested by DataGardener.
Need an entitlement to get started?
Design partners and POCs are open now.