Getting Started
Get up and running with the LookC MCP server in minutes. This guide covers authentication setup, initial configuration, and your first successful connection.
Prerequisites
Before connecting to the LookC MCP server, ensure you have the following:
LookC Account Access
Active LookC account with API access permissions enabled by your account manager.
MCP-Compatible Client
AI client or framework that supports the Model Context Protocol (Claude Desktop, CrewAI, etc.).
System Requirements
- Network Access: HTTPS connectivity to
api.lookc.io - Protocol Support: MCP version
2024-11-05or later - Transport: HTTP/HTTPS client with JSON-RPC 2.0 support
Authentication
The LookC MCP server uses API key authentication with bearer token authorization.
Obtaining Your API Key
Contact Your Account Manager: LookC API keys are provisioned on a per-account basis. Contact your LookC account manager to request API access and receive your authentication credentials.
Your account manager will provide:
- API Key: Your unique authentication token
- Account Scope: Specific data access permissions
- Rate Limits: Request quotas and throttling information
Secure Key Storage
Store your API key securely using your preferred method:
Environment variable storage
export LOOKC_API_KEY="your_api_key_here"
Security Best Practices: Never commit API keys to version control or share them in public channels. Use environment variables or secure credential management systems in production environments.
MCP Inspector
The MCP Inspector is an essential tool for exploring and testing MCP servers during development.
Installation
Install the MCP Inspector to explore available tools and test connections:
npm install -g @modelcontextprotocol/inspector
Connecting to LookC
Launch the inspector with your LookC MCP server configuration:
mcp-inspector https://api.lookc.io/mcp \
--auth-header "Authorization: Bearer YOUR_API_KEY"
Inspector Features
The MCP Inspector provides:
- Tool Discovery: Browse all available LookC tools and their parameters
- Interactive Testing: Execute tools with custom parameters and view responses
- Schema Validation: Verify parameter types and required fields
- Error Debugging: Detailed error messages and troubleshooting guidance
Tool Exploration
Discover available tools and understand their capabilities before integration.
Parameter Testing
Test different parameter combinations to understand tool behavior.
Response Analysis
Examine response structures and data formats for integration planning.
First Connection
Let's establish your first connection to the LookC MCP server and verify everything is working correctly.
Basic Connection Test
Connection verification
curl -X POST https://api.lookc.io/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'
Expected Response
A successful connection will return the available tools:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"tools": [
{
"name": "get_employee_list",
"description": "Retrieve employees for an organization with filtering options",
"inputSchema": {
"type": "object",
"properties": {
"org_id": {
"type": "string",
"description": "LookC organization UUID"
}
},
"required": ["org_id"]
}
}
]
}
}
Testing Tools
Once connected, test the available tools to ensure proper functionality.
Organization ID Lookup
Start by converting a LinkedIn URL to a LookC organization ID:
Organization ID test
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "get_organization_ids",
"arguments": {
"linkedin_url": "https://www.linkedin.com/company/openai"
}
}
}
Employee List Retrieval
Use the organization ID to retrieve employee information:
Employee list test
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "get_employee_list",
"arguments": {
"org_id": "550e8400-e29b-41d4-a716-446655440000",
"title_regex": "engineer",
"limit": 5
}
}
}
Troubleshooting
Common issues and their solutions:
- Name
401 Unauthorized- Type
- error
- Description
Cause: Invalid or missing API key Solution: Verify your API key is correct and properly formatted in the Authorization header
- Name
403 Forbidden- Type
- error
- Description
Cause: API key lacks required permissions Solution: Contact your account manager to verify account scope and permissions
- Name
429 Rate Limited- Type
- error
- Description
Cause: Exceeded request rate limits Solution: Implement exponential backoff and respect rate limit headers
For additional debugging guidance, see our Debugging documentation.
Next Steps
Now that you have a working connection:
- Explore Integration Options: Choose your preferred integration method
- Review Available Tools: Study the complete tools documentation
- Build Your First Agent: Follow our inspiration guide for use case examples
Ready to integrate with your preferred platform? Check out our platform-specific guides:
