MCP Integration
Let AI assistants use Clario Scope via Model Context Protocol
What is MCP?
The Model Context Protocol (MCP) is an open standard by Anthropic that lets AI assistants (Claude, Cursor, Windsurf, etc.) connect to external services and call real tools. Datronis exposes an MCP server so any MCP-compatible AI can search jobs, browse news, explore companies, and query platform stats — all without writing a single line of integration code.
Quickest way to test
Paste the server URL into Claude Desktop (or any MCP client) and immediately ask: "Find remote senior React jobs" or "Show me the latest tech news."
Server URL
The MCP server is a single HTTP endpoint. All three HTTP methods are used by the protocol:
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
POST /api/mcp | HTTP | Yes | — | Initialize a new session or send messages to an existing one |
GET /api/mcp | HTTP | No | — | Open a Server-Sent Events stream for server-initiated messages (requires Mcp-Session-Id header) |
DELETE /api/mcp | HTTP | No | — | Close and clean up a session (requires Mcp-Session-Id header) |
https://api.clarioscope.com/api/mcpClaude Desktop Setup
Add the following to your Claude Desktop configuration file. On macOS this is at ~/Library/Application Support/Claude/claude_desktop_config.json.
{
"mcpServers": {
"datronis": {
"command": "npx",
"args": [
"mcp-remote",
"https://api.clarioscope.com/api/mcp"
]
}
}
}mcp-remote
The `mcp-remote` package bridges Claude Desktop (which uses stdio) to any HTTP MCP server. Install it once with: `npm install -g mcp-remote`
Cursor / Windsurf / Cline Setup
These editors support HTTP MCP servers natively. Add the server URL in your editor's MCP settings panel:
{
"mcpServers": {
"datronis": {
"url": "https://api.clarioscope.com/api/mcp",
"type": "http"
}
}
}Available Tools
All tools are public (no API key required). The AI can call them automatically based on your request.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
search_jobs | tool "q""country""city""remote_type""job_type""job_level""skills""salary_min""page""limit" | No | — | Search job listings by keyword, location, remote policy, job type, experience level, and skills. Returns paginated results. |
get_job | tool "slug (required)" | No | — | Get the full details of a job by its slug or ID — including description, requirements, salary, and application URL. |
get_news | tool "title""category_id""locale""limit""offset" | No | — | Fetch the latest news articles. Filter by title keyword, category ID, or locale (language). Returns title, summary, date, and URL. |
get_categories | tool "locale" | No | — | List all content categories on the platform. Used to discover category IDs for filtering news. |
search_companies | tool "query""country""industry""is_hiring""limit""page" | No | — | Search companies by name, industry, or country. Optionally filter to actively-hiring companies. |
get_platform_stats | tool | No | — | Get platform-wide statistics: total jobs, companies, news articles, and users. |
Resources
The MCP server also exposes a readable resource — the platform overview documentation — which AI assistants can read to understand the platform before calling tools:
platform://docs/overviewHow Sessions Work
The server uses the Streamable HTTP transport (MCP spec 2025-03-26):
- Step 1 — Client sends
POST /api/mcpwith aninitializemessage (no session ID header). - Step 2 — Server creates a session and returns the
Mcp-Session-Idheader. - Step 3 — All subsequent tool calls include the
Mcp-Session-Idheader. - Step 4 — Client can open a
GET /api/mcpSSE stream for server-initiated notifications. - Step 5 — Client sends
DELETE /api/mcpto close the session when done. - Auto-expiry — Sessions auto-expire after 30 minutes of inactivity.
# Step 1: Initialize a session
curl -X POST https://api.clarioscope.com/api/mcp \
-H "Content-Type: application/json" \
-D - \
-d '{"jsonrpc":"2.0","method":"initialize","id":1,"params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'
# Note the Mcp-Session-Id in the response headers, then:
# Step 2: List available tools
curl -X POST https://api.clarioscope.com/api/mcp \
-H "Content-Type: application/json" \
-H "Mcp-Session-Id: <your-session-id>" \
-d '{"jsonrpc":"2.0","method":"tools/list","id":2}'
# Step 3: Call search_jobs
curl -X POST https://api.clarioscope.com/api/mcp \
-H "Content-Type: application/json" \
-H "Mcp-Session-Id: <your-session-id>" \
-d '{"jsonrpc":"2.0","method":"tools/call","id":3,"params":{"name":"search_jobs","arguments":{"q":"React","remote_type":"REMOTE","limit":5}}}'Locale Reference
The locale parameter in get_news and get_categories accepts a number from 1–18:
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
1 | English | No | — | Default |
2 | Arabic | No | — | RTL |
3 | Persian / Farsi | No | — | RTL |
4 | French | No | — | |
5 | German | No | — | |
6 | Spanish | No | — | |
7 | Italian | No | — | |
8 | Portuguese | No | — | |
9 | Russian | No | — | |
10 | Turkish | No | — | |
11 | Chinese | No | — | |
12 | Japanese | No | — | |
13 | Korean | No | — | |
14 | Hindi | No | — | |
15 | Urdu | No | — | RTL |
16 | Bengali | No | — | |
17 | Swahili | No | — | |
18 | Dutch | No | — |
Example AI Prompts
Once connected, try these natural language prompts in any MCP-aware AI:
- "Find remote senior React developer jobs in Europe"
- "What are the latest tech news articles in English?"
- "Search for fintech companies actively hiring in London"
- "How many jobs and companies are on the platform?"
- "Get the job details for slug 'senior-frontend-engineer-acme-corp'"
- "List all available news categories"