> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datalayer.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude

> Connect Claude to Datalayer with a remote MCP connector and OAuth sign-in.

The original four profile operations passed in the native Claude desktop app on October 17, 2026.
This guide uses a personal custom connector. Web and managed-workspace availability
can differ; an organization owner may need to add the connector first.

**1. Open your Datalayer workspace**

Sign in and open [Connections](https://app.datalayer.so/#connect). Use the same
account when Claude asks you to authorize Datalayer. Keep an existing working
Datalayer connector.

**2. Add the custom connector in Claude**

Open **Customize → Connectors → Add custom connector**. Name it **Datalayer**
and use this server URL:

```text Server URL theme={null}
https://mcp.datalayer.so/mcp
```

**3. Sign in and enable Datalayer**

Choose sign-in authentication. If an OAuth client method is requested, choose
automatic registration. Complete Datalayer sign-in in the browser, review
the authorization request and enable the connector in your conversation.
This route does not require pasting an API key into Claude.

**4. Check the tools before researching**

Confirm the connector exposes the [fifteen tools](https://docs.datalayer.so/tools.md), including
`find_companies`, `get_company_profile`, `find_people`, `get_person_profile`,
and `get_account_details`. Listing the tools uses no credits. When you ask
about your account or remaining credits, Claude should call
`get_account_details`; that read also uses no credits.

## Claude Code plugin

Claude Code also has an installable Datalayer plugin. Use the existing
[Datalayer marketplace](https://gitlab.com/datalayer/plugins), then start a fresh
Claude Code session:

```bash theme={null}
claude plugin marketplace add https://gitlab.com/datalayer/plugins.git
claude plugin install datalayer-plugin@datalayer
```

Already installed? Update instead:

```bash theme={null}
claude plugin marketplace update datalayer
claude plugin update datalayer-plugin@datalayer
```

Use version **2.1.1** or newer. Sign in through `/mcp` using the plugin's
`datalayer-2` server and your Datalayer account, then ask for your remaining
credits. The `get_account_details` check is free.

An older installation named `datalayer@datalayer` is a different package. Install
and verify the current package before disabling an obsolete one. A manual MCP
connection to the same URL can take precedence over the plugin; inspect and reuse
a working connection, or deliberately remove a redundant manual entry before
signing in to the plugin. Do not overwrite a separate legacy service connection.

The Claude Code package is separate from Claude web/desktop custom connectors.
Installation from our marketplace does not mean Datalayer is listed in Claude's
public directory. See the [setup and troubleshooting guide](https://gitlab.com/datalayer/plugins/-/blob/main/docs/setup.md).

## Try a search

Once your account has an active allowance, copy this into Claude:

```text theme={null}
Use Datalayer to search for Stripe. Show up to three company matches and their websites. Wait for me to choose a match before opening a full profile.
```

On the published plan for new signups, a search with results costs 1 credit. An empty search costs nothing. A new profile costs 1 credit, and a verified work email costs 2.
Ask Claude to report `meta.credits_used`. Review the result in your
[dashboard](https://app.datalayer.so/#connect) and see [profiles and usage](https://docs.datalayer.so/profiles-and-usage.md).

If custom connectors are unavailable, check with your workspace administrator.
For failed authorization after disconnecting, use **Finish disconnecting** in
Datalayer Connections before trying to sign in again. See [help](https://docs.datalayer.so/help.md).

Using the terminal? Follow [Claude Code setup](https://docs.datalayer.so/integrations/other-clients.md#claude-code).
[Claude's connector documentation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
explains client availability.

The hosted connector lists fifteen tools: `find_people`, `get_person_profile`, `find_work_email`, `validate_email`, `find_companies`, `get_company_profile`, `find_job_postings`, `get_tech_stack`, `find_sites_using_tech`, `list_technologies`, `get_list_filters`, `preview_list`, `build_list`, `get_list_results`, and `get_account_details`. [What you can do](https://docs.datalayer.so/tools.md) explains each one and what it costs. You can paste the [universal setup prompt](https://docs.datalayer.so/getting-started.md#copy-this-into-your-assistant) and let Claude walk through sign-in. The October 17 acceptance covered the original four profile operations. Acceptance of the full fifteen-tool catalog in this installed client is still open.

`find_job_postings` searches indexed postings across companies. A page with at least one posting costs 1 credit. An empty successful page and failures cost zero. The identical search repeats free within 24 hours. Each posting includes a shortened description, salary when present, function, employment type, close date and status, source domain, and first-seen and updated dates. Indexed postings are not confirmed hires. A technology stack is a separate lookup from a company profile. Request `dry_run` for a maximum estimate before a larger task, set `max_credits` to cap spending, and inspect section coverage and the credit receipt.

Explicitly requested employer-associated business-email candidates may be returned
as **UNVERIFIED** for zero email credits. Keep the email assessment,
verification status, checked dates and catch-all uncertainty separate; an email assessment of
`valid` with unknown catch-all status is not conclusive verification.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.