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

# MoltSets MCP Server

> Connect Claude, Claude Code, and any MCP client to MoltSets. Give your AI agent live access to contact enrichment, HEM and IP resolution, and the full identity graph in one tool call.

> Legacy enrichment tools are form-based and manual. MoltSets is prompt-and-go. It's an MCP built specifically for AI agents — so your agent can de-anonymize website visitors, resolve hashed emails (HEMs) to real identities, enrich contacts from LinkedIn, and connect the dots between IP addresses, MAIDs, and people. The full identity graph, accessible in a single tool call.

## What is the MoltSets MCP Server?

The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) is an open standard that lets AI assistants connect directly to external tools and data sources instead of relying on their training data.

The **MoltSets MCP Server** gives any compatible AI tool direct access to MoltSets enrichment capabilities — every endpoint, parameter, and response schema — so your agent can enrich contacts, resolve identities, and look up visitor data without leaving the conversation.

**MCP Server URL**

```text theme={null}
https://mcp.moltsets.com/mcp
```

***

## Why Use It?

AI models are trained on static snapshots of the internet. When they generate code for an API, they often:

* Hallucinate endpoints that don't exist
* Use outdated parameter names
* Return incorrect response shapes

With the MoltSets MCP Server connected:

| Without MCP                | With MCP                                 |
| :------------------------- | :--------------------------------------- |
| AI guesses endpoint URLs   | AI reads the real API reference          |
| Outdated parameter names   | Always up-to-date parameter schemas      |
| Incorrect response shapes  | Accurate response structures from source |
| Back-and-forth corrections | Correct code on the first try            |

***

## Setup

<Tabs>
  <Tab title="Claude (claude.ai)">
    How you add the connector depends on your account type. On a **personal** plan you add it yourself. On a **Team or Enterprise** plan, an Owner adds it once for the whole organization, then each member connects their own credentials.

    <AccordionGroup>
      <Accordion title="Personal account (Free, Pro, or Max)">
        1. In Claude.ai, go to **Customize → Connectors**.
        2. Click **+**, then **Add custom connector**.
        3. Paste the following into **Remote MCP server URL**:
           ```text theme={null}
           https://mcp.moltsets.com/mcp
           ```
        4. Click **Advanced settings** and enter your MoltSets Connector credentials:
           * **OAuth Client ID:** your Client ID
           * **OAuth Client Secret:** your Client Secret
        5. Click **Add**.

        <Note>
          Free accounts are limited to a single custom connector. Pro and Max accounts can add multiple.
        </Note>
      </Accordion>

      <Accordion title="Team or Enterprise account">
        Only an **Owner or Primary Owner** can add a custom connector to a Team or Enterprise organization. Once added, each member connects to it individually — Claude only ever accesses data that the connecting member is authorized to see.

        **Owner / Primary Owner — add the connector for the organization:**

        1. Go to **Organization settings → Connectors**.
        2. Click **Add**.
        3. Hover over **Custom**, then select **Web**.
        4. Paste the following into **Remote MCP server URL**:
           ```text theme={null}
           https://mcp.moltsets.com/mcp
           ```
        5. Click **Advanced settings** and enter the MoltSets Connector credentials (**OAuth Client ID** and **OAuth Client Secret**).
        6. Click **Add**.

        **Each member — connect to it:**

        1. Go to **Customize → Connectors**.
        2. Find the MoltSets connector (marked with a **Custom** label).
        3. Click **Connect** and complete authentication.
      </Accordion>
    </AccordionGroup>

    <Note>
      To get your credentials, log into [app.moltsets.com](https://app.moltsets.com) and go to **Connectors** to create a new connector.
    </Note>
  </Tab>

  <Tab title="Claude Desktop">
    Claude Desktop shares the same connectors as your Claude account — no config file editing required, and a connector you add on Claude.ai is already available here. How you add it depends on your account type. On a **personal** plan you add it yourself. On a **Team or Enterprise** plan, an Owner adds it once for the whole organization, then each member connects their own credentials.

    <AccordionGroup>
      <Accordion title="Personal account (Free, Pro, or Max)">
        1. In Claude Desktop, go to **Customize → Connectors**.
        2. Click **+**, then **Add custom connector**.
        3. Paste the following into **Remote MCP server URL**:
           ```text theme={null}
           https://mcp.moltsets.com/mcp
           ```
        4. Click **Advanced settings** and enter your MoltSets Connector credentials:
           * **OAuth Client ID:** your Client ID
           * **OAuth Client Secret:** your Client Secret
        5. Click **Add**, then **restart Claude Desktop** so it picks up the connector.

        <Note>
          Free accounts are limited to a single custom connector. Pro and Max accounts can add multiple.
        </Note>
      </Accordion>

      <Accordion title="Team or Enterprise account">
        Only an **Owner or Primary Owner** can add a custom connector to a Team or Enterprise organization. Once added, each member connects to it individually — Claude only ever accesses data that the connecting member is authorized to see.

        **Owner / Primary Owner — add the connector for the organization:**

        1. Go to **Organization settings → Connectors**.
        2. Click **Add**.
        3. Hover over **Custom**, then select **Web**.
        4. Paste the following into **Remote MCP server URL**:
           ```text theme={null}
           https://mcp.moltsets.com/mcp
           ```
        5. Click **Advanced settings** and enter the MoltSets Connector credentials (**OAuth Client ID** and **OAuth Client Secret**).
        6. Click **Add**.

        **Each member — connect to it:**

        1. In Claude Desktop, go to **Customize → Connectors**.
        2. Find the MoltSets connector (marked with a **Custom** label).
        3. Click **Connect** and complete authentication.
        4. **Restart Claude Desktop** so it picks up the connector.
      </Accordion>
    </AccordionGroup>

    <Note>
      To get your credentials, log into [app.moltsets.com](https://app.moltsets.com) and go to **Connectors** to create a new connector.
    </Note>

    ### Configuring Tool Permissions

    By default, all MoltSets tools are set to **Needs Approval** — Claude will prompt you the first time each tool is used. To update permissions in bulk:

    1. Go to **Customize → Connectors**
    2. Click **Configure** beside the MoltSets connector
    3. Use the bulk change tool to set all tools to **Always Allow**

    To restrict specific tools, set them individually to **Blocked**.
  </Tab>

  <Tab title="Claude Code">
    Run the following command in your terminal, replacing the placeholder values with your credentials:

    ```bash theme={null}
    claude mcp add --transport http moltsets https://mcp.moltsets.com/mcp \
      --client-id YOUR_CLIENT_ID \
      --client-secret
    ```

    The `--client-secret` flag takes no value — Claude Code prompts you for the secret (or reads it from the `MCP_CLIENT_SECRET` environment variable).

    By default the server is added at the `local` scope (current project only). Add `--scope user` to make MoltSets available across all your projects:

    ```bash theme={null}
    claude mcp add --transport http moltsets https://mcp.moltsets.com/mcp \
      --scope user \
      --client-id YOUR_CLIENT_ID \
      --client-secret
    ```

    Claude Code will open a browser window and prompt you to approve access on the MoltSets consent screen. Once approved, your token is stored and managed automatically.

    <Note>
      **Personal account:** the command above works as-is.

      **Team or Enterprise account:** on business plans, only admins can add MCP servers to Claude Code. If you sign into Claude Code with your Claude.ai account, any MoltSets connector already added there is available in Claude Code automatically — no `claude mcp add` needed.
    </Note>

    <Note>
      To get your credentials, log into [app.moltsets.com](https://app.moltsets.com) and go to **Connectors** to create a new connector.
    </Note>
  </Tab>
</Tabs>

***

## Example Prompts

Once connected, you can talk to MoltSets the same way you'd talk to a colleague. Here are a few prompts to get started:

**Enrich a contact from LinkedIn**

> "Enrich this LinkedIn profile and give me their business email and phone number: linkedin.com/in/example"

**Look up a visitor**

> "I have an IP address from a site visitor — 192.0.2.1 — can you tell me who this is?"

**Resolve a hashed email**

> "Resolve this HEM to a real identity and return the name and company: `abc123...`"

**Bulk enrich a list**

> "Here are 10 LinkedIn URLs. Enrich each one for business email and return the results as a table."

Visit "[**I Have X, I Want Y**](/use-cases/i-have-x-i-want-y)" for more example prompts.

***

## Tokens & Costs

You only spend tokens on **verified data that is actually returned**. A few rules the agent follows automatically:

* **No data, no charge.** Calls that return `not_found` cost nothing.
* **Counting is free.** `search_linkedin_profile` with `count_only: true` returns match counts without spending tokens — use it to size a search before committing.
* **Free tools.** `get_account`, `get_billing`, and `get_usage` never cost tokens. Call `get_billing` for the per-tool `token_costs` map and your current balance.

### External tokens

MoltSets resolves most contact data from its own database. When the data you need isn't there, MoltSets can reach out to a **third-party source** to try to find it — those calls spend **external tokens**, a balance separate from your regular tokens. Every response includes `external_tokens_used` and `external_tokens_remaining` in its `metadata` so your agent can track spend in real time.

For a full breakdown, see [External Tokens](https://support.moltsets.com/en/articles/15280420-external-tokens) and the [Rate Limits](/getting-started/rate-limits) guide.

<Note>
  New to the API? Start with [Authentication](/getting-started/authentication) to create your keys, then browse the [API Reference Overview](/getting-started/overview) for every endpoint, parameter, and response schema the MCP exposes.
</Note>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection fails after adding the config">
    Restart your AI tool after adding the MCP configuration. Most clients need a full restart to detect new MCP servers.

    Verify the URL is exactly:

    ```text theme={null}
    https://mcp.moltsets.com/mcp
    ```

    No trailing slash, no extra path segments.
  </Accordion>

  <Accordion title="Authentication errors (invalid credentials)">
    Double-check that your Client ID and Client Secret are copied correctly from [app.moltsets.com](https://app.moltsets.com) — no extra spaces, no truncation.

    If your credentials were recently rotated or revoked, generate a new connector from the **Connectors** page and update your config with the new values. Then restart your AI tool.
  </Accordion>

  <Accordion title="Network or timeout errors">
    Check your network connection and try again. If the issue persists, verify the server is reachable by opening `https://mcp.moltsets.com/mcp` in your browser. If you see a response (even an error page), the server is up and the issue is likely local to your config.
  </Accordion>
</AccordionGroup>