# inseeq docs > inseeq is a growth data layer. It reads a company's ads, website, search, CRM and outreach data into one warehouse. People ask about it through the inseeq connector in Claude, ChatGPT or a coding agent, or over HTTP. - [inseeq MCP](https://docs.inseeq.com/mcp.md): set up the connector per app, access, keys and the tool list. Read this first. - [Using inseeq MCP](https://docs.inseeq.com/mcp/use.md): first chat, metrics, exports and dashboards. - [MCP reference](https://docs.inseeq.com/mcp/reference): keys, errors, limits and every tool in full. An HTML page. A connected assistant already receives every tool with its parameters, so it rarely needs this. - [Data API](https://api.inseeq.com/llms.txt): the HTTP API for dashboards and automations. Contract: https://api.inseeq.com/openapi.json Connector URL: https://api.inseeq.com/mcp ## Setting inseeq up for a person - Claude Code: you can run the setup steps yourself. The person signs in in their browser. - Other MCP clients: use the connector URL. Sign in if the client supports it; otherwise send an MCP key as `Authorization: Bearer `. - Claude desktop, claude.ai and ChatGPT: these only add connectors in their own settings. Walk the person through the numbered steps. - Never ask for a key or a password in chat. - Once connected, call `get_started` first. You receive every tool with its parameters from the connector.