Claude Desktop Integration

Connect Claude Desktop to the LookC MCP server for seamless company research capabilities directly in your conversations.

Overview

Claude Desktop's MCP integration allows you to enhance conversations with real-time company data from LookC's research databases. This integration uses the streamable HTTP transport for reliable connectivity and supports all LookC MCP tools.

Native Integration

LookC tools appear directly in Claude Desktop's interface for seamless research workflows.

Conversational Research

Ask Claude to research companies and employees using natural language queries.

Configuration

Configure Claude Desktop to connect to the LookC MCP server using the streamable HTTP transport.

Claude Desktop Configuration File

Configuration Location: The Claude Desktop configuration file is typically located at:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Claude Desktop configuration

{
  "mcpServers": {
    "lookc": {
      "command": "node",
      "args": [
        "-e",
        "const { spawn } = require('child_process'); const client = spawn('curl', ['-X', 'POST', 'https://api.lookc.io/mcp', '-H', 'Content-Type: application/json', '-H', `Authorization: Bearer ${process.env.LOOKC_API_KEY}`, '--data-binary', '@-'], { stdio: ['pipe', 'pipe', 'inherit'] }); process.stdin.pipe(client.stdin); client.stdout.pipe(process.stdout);"
      ],
      "env": {
        "LOOKC_API_KEY": "your_lookc_api_key_here"
      }
    }
  }
}

Environment Variables Setup

For security, store your LookC API key as an environment variable:

Environment setup

# Add to ~/.bashrc or ~/.zshrc
export LOOKC_API_KEY="your_lookc_api_key_here"

# Reload shell configuration
source ~/.bashrc  # or ~/.zshrc

Restart Claude Desktop

After updating the configuration:

Close Claude Desktop completely
Restart the application
Verify connection by checking for LookC tools in the interface

Usage Examples

Once configured, you can use LookC research capabilities directly in Claude conversations.

Basic Company Research

Research conversations

User: "Can you research the engineering team at Stripe? I'm particularly interested in senior engineers and technical leaders."

Claude: I'll help you research Stripe's engineering team using LookC's database. Let me start by getting their organization information and then find their technical staff.

[Claude calls get_organization_ids with Stripe's LinkedIn URL]
[Claude calls get_employee_list with engineering title filters and senior seniority levels]

Based on the LookC data, here's what I found about Stripe's engineering team:

**Technical Leadership:**
- [Detailed list of VPs, Directors, and Senior Engineers]
- [Team structure and key personnel]
- [Recent hiring patterns and growth areas]

Advanced Research Workflows

Complex research tasks

User: "I'm analyzing the fintech space. Can you research the technical teams at Stripe, Square, and Plaid? Focus on their payments infrastructure and API teams."

Claude: I'll conduct a comprehensive analysis of the technical teams at these leading fintech companies, focusing specifically on payments infrastructure and API development roles.

[Claude uses multiple LookC tool calls with specific filters]
[Analyzes team structures and identifies key personnel]
[Provides strategic insights based on the data]

**Fintech Technical Team Analysis:**

1. **Payments Infrastructure Teams:**
   - Team sizes and growth patterns
   - Key technical leaders and their backgrounds
   - Infrastructure specializations

2. **API Development Focus:**
   - Developer experience teams
   - Platform engineering leadership
   - Recent API-focused hires

3. **Strategic Insights:**
   - Hiring trends and competitive positioning
   - Technical expertise gaps and opportunities
   - Market positioning based on team structure

Tool-Specific Examples

Individual tool usage

User: "What's the LookC organization ID for Anthropic?"

Claude: I'll look up Anthropic's organization information using their LinkedIn URL.

[Calls get_organization_ids with Anthropic's LinkedIn URL]

Anthropic's LookC organization details:
- **Organization ID**: 550e8400-e29b-41d4-a716-446655440000
- **Name**: Anthropic
- **LinkedIn ID**: 80309071
- **Sales Navigator ID**: company:80309071

Troubleshooting

Common issues and solutions for Claude Desktop integration:

Connection Issues

Name
Server not found
Type
error
Description
Symptoms: Claude Desktop shows "LookC server not available" Solution: Verify the configuration file syntax and restart Claude Desktop
Name
Authentication failed
Type
error
Description
Symptoms: "401 Unauthorized" errors in tool calls Solution: Check that your LOOKC_API_KEY environment variable is set correctly
Name
Tools not appearing
Type
error
Description
Symptoms: LookC tools don't show up in Claude's interface Solution: Ensure the MCP server configuration is in the correct location and format

Configuration Validation

Validation steps

# Verify environment variable
echo $LOOKC_API_KEY

# Test API connectivity
curl -X POST https://api.lookc.io/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $LOOKC_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Performance Optimization

Request Batching

Ask Claude to research multiple companies in a single conversation to leverage batching.

Specific Filters

Use specific title and seniority filters to reduce response times and improve relevance.

Next Steps

With Claude Desktop configured for LookC integration:

Explore Use Cases: Try the examples in our Inspiration guide
Advanced Integration: Set up Custom Agents for specialized workflows
Development Tools: Configure VSCode and Cursor for development workflows

For additional integration options, see our LLM Frameworks guide for CrewAI and OpenAI Assistants API setup.