01
Add server
Register Crawlora as a remote Streamable HTTP MCP server using the hosted URL.
Developer guides
Connect MCP-capable clients and agent-native workflows to Crawlora's hosted Streamable HTTP endpoint for structured public web data tools.
Hosted MCP endpoint
https://mcp.crawlora.net/mcp
Connection
URL: https://mcp.crawlora.net/mcp
Transport: Streamable HTTP
Auth header: Authorization: Bearer $CRAWLORA_API_KEY
Server card: https://crawlora.net/.well-known/mcp/server-card.jsonMCP URL
https://mcp.crawlora.net/mcp
Transport
Streamable HTTP
Auth header
Authorization: Bearer
Crawlora exposes a hosted MCP endpoint at https://mcp.crawlora.net/mcp. Configure MCP-capable clients with Streamable HTTP transport and pass the same server-side Crawlora API key as Authorization: Bearer. The MCP endpoint also accepts x-api-key for clients that support custom headers.
Developer workflow
MCP lets AI clients discover and call tools exposed by a server. Crawlora's agent-native APIs fit this model because supported endpoints have clear inputs and structured JSON outputs.
Developer workflow
Developer workflow
Use the hosted endpoint directly when your client supports remote Streamable HTTP MCP servers.
Developer workflow
Use these values in MCP-capable hosts. Keep the API key outside model-visible prompts and browser code.
MCP URL: https://mcp.crawlora.net/mcp Transport: Streamable HTTP Authentication: Authorization: Bearer $CRAWLORA_API_KEY Alternate auth: x-api-key: $CRAWLORA_API_KEY Server card: https://crawlora.net/.well-known/mcp/server-card.json
codex mcp add crawlora \ --url https://mcp.crawlora.net/mcp \ --bearer-token-env-var CRAWLORA_API_KEY
{
"mcpServers": {
"crawlora": {
"url": "https://mcp.crawlora.net/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer $CRAWLORA_API_KEY"
}
}
}
}curl https://crawlora.net/.well-known/mcp/server-card.json
Developer workflow
01
Register Crawlora as a remote Streamable HTTP MCP server using the hosted URL.
02
Pass the Crawlora API key as Authorization: Bearer from the MCP client or server-side host. Use x-api-key only when the host supports custom headers but not bearer token configuration.
03
Let the MCP client list available tools and resources before choosing an endpoint.
04
Send only documented inputs for the selected Crawlora tool and cap result sizes where possible.
05
Surface 401, plan, credit, rate-limit, and upstream errors clearly to the agent-native workflow.
Developer workflow
Developer workflow
Illustrative schema for a wrapper tool. Use exact generated tool names from endpoint docs where available.
{
"name": "crawlora_google_search",
"description": "Search public Google results through Crawlora and return normalized JSON.",
"inputSchema": {
"type": "object",
"properties": {
"keyword": { "type": "string" },
"country": { "type": "string" },
"language": { "type": "string" },
"limit": { "type": "number" }
},
"required": ["keyword"]
},
"output": "Crawlora JSON envelope with result items, status, and message fields."
}Developer workflow
Use this pattern only when you need to run a private MCP server that wraps Crawlora REST APIs behind your own policy layer.
async function callCrawloraTool(args: {
keyword: string;
country?: string;
language?: string;
limit?: number;
}) {
const response = await fetch("https://api.crawlora.net/api/v1/google/search", {
method: "POST",
headers: {
"x-api-key": process.env.CRAWLORA_API_KEY ?? "",
"Content-Type": "application/json",
},
body: JSON.stringify({
keyword: args.keyword,
country: args.country ?? "us",
language: args.language ?? "en",
limit: args.limit ?? 10,
page: 1,
}),
});
if (!response.ok) {
throw new Error(`Crawlora request failed: ${response.status} ${await response.text()}`);
}
return response.json();
}
// Register this handler with the MCP SDK version used by your server.Developer workflow
Developer workflow
Use Crawlora for structured public web data workflows. Customers are responsible for compliance with applicable laws, third-party rights, platform rules, and Crawlora terms. Keep API keys server-side, validate inputs, and avoid collecting or storing unnecessary sensitive data.
Read Crawlora termsDeveloper workflow
Use these pages to move between endpoint discovery, examples, pricing, and responsible-use guidance.
Developer workflow
Common questions for this Crawlora developer integration path.
Model Context Protocol is a pattern for exposing tools and resources to AI clients through a server interface.
Yes. Use the hosted Streamable HTTP endpoint at https://mcp.crawlora.net/mcp with Authorization: Bearer. The MCP endpoint also accepts x-api-key for clients that support custom headers.
Yes. Wrap narrow Crawlora HTTP calls behind server-side MCP tools and keep the API key in the server environment.
Search, Maps, Geocoding, Airbnb, TripAdvisor, Zillow, YouTube, TikTok, App Store, Google Play, Spotify, Spotify Podcasts, Apple Podcasts, Amazon, Product Hunt, Trustpilot, and review endpoints are useful candidates when they match your agent's task.
Store keys server-side, restrict tool access, validate inputs, and avoid logging secrets.
Yes. Tool calls that invoke Crawlora API endpoints can consume credits according to endpoint billing rules.
MCP focuses on a protocol for exposing tools to clients. LangChain tools are framework-level wrappers inside LangChain workflows.
Start with the hosted MCP URL, validate Authorization: Bearer or the x-api-key fallback, then call one narrow search, travel, property, review, app-review, podcast, or music catalog tool.