MCP

Connect straight from your client.

AI clients connect directly to https://ai.turkservis.online/mcp — no local bridge, no background process, no relay tool required.

Start using it MCP client setup (Cursor, Cline, LibreChat) Compatibility matrix Security boundaries

Advice and implementation, in your own IDE

Keep your chosen main model. In Claude Code, Codex and AITURK IDE the TurkServis teams are reached through the AITURK CLI: they read your project and, when you allow it, edit files and run commands. MCP is for clients that cannot run commands.

Sign in and create your own member API key. Calls use your TurkServis balance/quota; the main IDE subscription does not pay for them.
Claude Code, Codex, AITURK IDE: install the official AITURK CLI 1.10.33+ and sign in with aiturk login. Do not add the MCP server to these clients; advice is aiturk fusion, reviews and work are aiturk agent run / aiturk hedef, media is aiturk media.
Helper skill for Windows: download the package below. It installs only the automatically discoverable aiturk-work skill for Claude Code or Codex. It writes no MCP entry, asks for no API key and leaves existing MCP settings untouched.
Close your IDE, extract the ZIP and run one command below from its folder; then restart the IDE and its terminal.
Clients that cannot run commands (Cursor, Cline, LibreChat and similar): add the remote MCP connection.
Ask normally: “Fix this login bug, preserve the current behavior and test it.” Your main AI selects useful advice and implementation tools. You do not need to request teams every time.

Download helper skill package · 1.1.0 · ZIP File verification details

.\setup.ps1 -Target claude

.\setup.ps1 -Target codex

For both IDEs use -Target both. To verify without changes, add -Check.

SHA-256: 5fa9ddc522f2575a50b8d3da45d3be1896c7651159d3fef892b5222adb79a42f · 11870 bytes

Readable setup and skill files, not a new executable release. SHA-256 alone is not publisher authentication. The signed CLI files and release verification stay unchanged. Do not bypass your organization’s script policy.

What runs where?

When the AITURK CLI is installed, use it instead of MCP. MCP stays available for clients that cannot run commands, and as a fallback while the CLI is not installed or aiturk doctor reports a failure.

AITURK CLI: the teams run as local agents that read the project and, within the explicitly authorized project, can edit and run commands. MCP-only: the teams return advice, research or code; your main AI applies and tests it. A suggested patch is not a completed edit; ask for the actual diff and test evidence.

The helper package does not read or change MCP settings, the main model or approval settings. Locally edited skills are not overwritten; the rest of the setup still completes. Replaced files get backups. No API key is requested; the CLI uses your aiturk login session.

Automatic selection depends on the IDE and model’s tool/skill support. This release does not promise an always-on distributed task queue, unlimited nested agents or recovery of every running process after disconnection. If the local worker cannot run, the main AI can continue with its own approved editing tools.

Connection contract

Transport is Streamable HTTP; authentication is a bearer token read from an environment variable. Tool calls follow your client's own approval policy.

Endpoint and protocol

Protocol traffic goes only to the /mcp endpoint on ai.turkservis.online; turkservis.online/mcp is this documentation page. The server accepts protocol versions 2026-07-28 and 2025-11-25. The JSON request-body limit is 512 KiB.

https://ai.turkservis.online/mcp

Published tools

The server publishes the following advisory, research and media tools. They cannot independently read the local file system or execute commands.

ask_team: Asks the bounded TurkServis advisor panel.
review_plan: Reviews an explicitly supplied plan.
diagnose_problem: Diagnoses supplied symptoms and evidence.
review_patch: Reviews an explicitly supplied patch and test evidence.
research_topic: Enqueues source-grounded web research.
scan_innovations: Enqueues a source-grounded innovation scan.
verify_result: Verifies supplied claims against supplied evidence.
get_job: Gets one research job owned by the member.
cancel_job: Cancel your queued or running research job. Measured usage from completed calls is retained.
list_models: Discover the models available to your account.
list_capabilities: Discover available media models.
generate_media: Generate media with your TurkServis account.

Identity boundary

Only a member-owned API key is accepted. Missing or invalid credentials return 401; a master administrator or service credential returns 403. The raw key is never passed into tool context or logs.

Support boundary

Your client must support remote Streamable HTTP and a bearer token from an environment variable. If it does not, we do not pretend automatic integration exists.