Company and people data.
In your agent.

Claude web and Desktop

Using the terminal? See Claude Code setup.

1. Open Customize → Connectors, then Add custom connector.
2. Name it Datalayer and paste the server URL above.
3. Connect, complete Datalayer sign-in, then enable the connector in your conversation.

For managed workspaces, an organization owner may need to add the connector first. If your client does not offer custom connectors, check its availability with your administrator.

Claude’s connector guide ↗

Claude Code

Run this command in the project where you want Datalayer available:

claude mcp add --transport http datalayer https://mcp.datalayer.so/mcp

Open Claude Code, run /mcp, and authenticate Datalayer in the browser.

Claude Code’s MCP guide ↗

Codex

With Codex CLI installed, add the remote server:

codex mcp add datalayer --url https://mcp.datalayer.so/mcp

Complete browser sign-in when prompted. If authentication is still needed, run codex mcp login datalayer. Open a Codex CLI session and use /mcp to inspect the connection.

OpenAI’s MCP setup guide ↗

Cursor

Merge this entry into ~/.cursor/mcp.json for personal use, or .cursor/mcp.json for one project. Keep your existing servers.

{
  "mcpServers": {
    "datalayer": {
      "url": "https://mcp.datalayer.so/mcp"
    }
  }
}

Open Cursor’s MCP settings and follow Datalayer’s sign-in prompt.

Cursor’s MCP guide ↗

Muse

Ask Muse to build a custom connector using Datalayer’s REST API. Meta documents custom connectors and a Secure Credentials Store; this route does not require Muse to support MCP sign-in.

1. In your Datalayer dashboard, create a dedicated API key for Muse in the production workspace.
2. Copy the setup prompt below into Muse. Supply your key only through Muse’s secure credential-entry flow, never in the conversation or generated code.
3. Have Muse check authentication first. A successful check returns {"authenticated":true} and uses no profiles.

Build a custom Datalayer REST API connector.
Base URL: https://api.datalayer.so
Ask me to supply a Datalayer API key through your secure credential flow. Store it in the Secure Credentials Store and send it only to this API host as an Authorization: Bearer header. Never include the key in chat, URLs, logs or source code. If secure entry is unavailable, stop and tell me.

First test only GET /v1/auth. Expect {"authenticated":true}. Do not run searches or lookups during setup.

Expose four operations, all POST with Content-Type: application/json:
- search_companies: /v1/companies/search — query (required), limit and offset.
- get_company: /v1/companies/lookup — exactly one of company_id or domain.
- search_people: /v1/people/search — query or company required; optional title, country (two uppercase letters), skill, limit and offset.
- get_person: /v1/people/lookup — exactly one of person_id or profile_url (public https://www.linkedin.com/in/... URL). Only add include: ["work_email"] when I explicitly request work email.

IDs are positive integer strings. Text filters are 1–200 characters. Limit is 1–25 (default 10); offset is 0–1000 (default 0). Send only the listed fields. For data requests, generate an Idempotency-Key and reuse it only when retrying the same operation and body. Respect errors and the account's profile allowance. Ask before the first data request.

This is a custom API connector recipe, not a prebuilt Muse integration. Authentication and data retrieval inside Muse still need verification. An active profile allowance is required for searches and lookups. Revoke the dedicated key in Datalayer when you remove the connector.

Meta’s connector guide ↗

Antigravity

In the IDE’s agent panel, open the menu, choose MCP Servers, then Manage MCP Servers and View raw config. Add Datalayer to your existing mcpServers entries:

{
  "mcpServers": {
    "datalayer": {
      "serverUrl": "https://mcp.datalayer.so/mcp"
    }
  }
}

Save, refresh the server list and follow the authentication prompt. Preserve your other server entries.

Antigravity’s MCP documentation ↗

OpenCode

Add a remote server to the mcp section of your OpenCode configuration, preserving existing entries:

{
  "mcp": {
    "datalayer": {
      "type": "remote",
      "url": "https://mcp.datalayer.so/mcp"
    }
  }
}

Run opencode mcp auth datalayer and complete browser sign-in.

OpenCode’s MCP documentation ↗

Grok Bot

Grok Bot installs integrations through its Marketplace. Datalayer does not yet have a published Grok Bot plugin, and a custom remote MCP installation flow has not been verified.

When an integration is available, Grok Bot’s documented flow is Marketplace → Add → browser sign-in, then attach the plugin with @ in a chat.

Grok web is a separate client with custom connector support. Its settings should not be used as instructions for Grok Bot.

Grok Bot’s plugin guide ↗

Check the connection first

Use your client’s tool list to confirm all four names appear. This check does not retrieve data:

• search_companies · Find company previews
• get_company · Retrieve a company profile
• search_people · Find professional profile previews
• get_person · Retrieve a professional profile

Once your workspace has an active allowance, try “Find up to three companies matching Stripe.” A new company or person lookup uses one profile; eligible repeats within 24 hours are included. Work email is only included when explicitly requested and available.

Private beta: client compatibility is still being tested. If setup fails, use dashboard support with your client name and version.

If you get stuck

Sign-in is unavailable for your account

Access remains restricted. Google sign-in also uses a restricted test audience. An installation link cannot authorize a new account.

Connected, but no profiles available

Check Usage in your dashboard. An active allowance is required for searches and lookups. Live checkout is disabled.

Authorization fails after disconnecting

Disconnect blocks that authorization. If reconnecting fails, use dashboard support rather than repeatedly reinstalling.

You need help with a client error

Use dashboard support with the client name/version and error code. Keep keys, tokens and profile data out of the message. Replies appear in the dashboard.

For a client that requires an API key, use its private Bearer-token setting with a key created in your dashboard. Never put a key in a shared configuration, URL or chat.