MCP Integration — Claude
Seek-api provides a fully managed MCP (Model Context Protocol) infrastructure. This architecture allows you to expose Seek-api capabilities to Claude without any local installation, simply by configuring the remote endpoint.
MCP Server Endpoint
Section titled “MCP Server Endpoint”Use the following address to configure your connector:
https://mcp.seek-api.com/mcpPlease use the full URL (including the HTTPS protocol and the /mcp path) when configuring the remote MCP server.
Prerequisites
Section titled “Prerequisites”- Compatible Client: An instance of Claude supporting custom connectors (e.g., Claude Desktop).
- Seek-api Account: A valid API key. The connection flow will guide you through account association via OAuth or direct entry.
Connector Configuration
Section titled “Connector Configuration”Terminology may vary slightly depending on your Claude client version.
-
Go to Customize settings in Claude.
-
Navigate to the Connectors section.
-
Select Add custom connector.
-
Enter the MCP server URL:
https://mcp.seek-api.com/mcp -
Validate the addition.
-
Authentication: Activate the connector and follow the authorization steps to link your Seek-api account.
-
Validation: In a new conversation, tools prefixed with
seekapi_*should now be available.
Available Tools Directory
Section titled “Available Tools Directory”Once integrated, Claude can orchestrate Seek-api capabilities via the following tools:
| Tool | Function | Auth Required |
|---|---|---|
seekapi_list_workers | Explores the catalogue (category, tags, search filters) | No |
seekapi_get_worker | Retrieves worker specifications (schemas, readme) | No |
seekapi_check_balance | Checks current balance and available credits | Yes |
seekapi_run_worker | Orchestrates submission and result polling | Yes |
seekapi_get_job | Polls the status of a specific job (job_uuid) | Yes |
Focus: seekapi_run_worker
Section titled “Focus: seekapi_run_worker”This tool encapsulates the entire lifecycle (Submission $\rightarrow$ Polling $\rightarrow$ Result).
| Parameter | Description |
|---|---|
worker_id | Unique identifier of the target worker |
input_json | Payload conforming to the worker’s input_schema |
max_billable_events | (Optional) Consumption ceiling for per_event workers |
max_wait_seconds | Maximum wait time before timeout (default: 120s) |
Typical Use Cases
Section titled “Typical Use Cases”“Which workers are available for sentiment analysis?” (Claude uses
seekapi_list_workersto explore the catalogue).
“Summarize this report into 3 key points: [Text]” (Claude identifies the appropriate worker, analyzes its schema, and executes
seekapi_run_worker).
“Check my current credit balance.” (Claude calls
seekapi_check_balance).
Troubleshooting
Section titled “Troubleshooting”Server Connection Failure
- Verify the URL accuracy:
https://mcp.seek-api.com/mcp(no spaces, HTTPS required).
Authentication Error (401)
- Your API key may be invalid or revoked. Generate a new one at console.seek-api.com.
Insufficient Balance (402)
- Your account has run out of credits. Please top up your balance via the dashboard.
Connector Not Visible
- Ensure you are using the latest version of Claude. Remote MCP connectors require recent application versions.