Setup
Connect your client.
API clients connect to https://ai.turkservis.online/v1 and MCP clients to https://ai.turkservis.online/mcp over Streamable HTTP. No local relay process or hidden background service is installed.
Claude Code, Codex and AITURK IDE: use the AITURK CLI
These clients can run commands, so they reach TurkServis teams through the AITURK CLI, not MCP. The teams then work as agents that read your project and, when you allow it, edit files and run commands. Your main model and approvals stay unchanged.
- Install the official AITURK CLI, then sign in with
aiturk login - Check the connection:
aiturk doctor - Optional: add the helper skill so your main AI picks these commands by itself. Helper skill package
aiturk fusion "question" -c "context" -s orta
aiturk agent run --read-only --project . -m <model> --goal "review"
aiturk agent run --project . -m <model> --goal "task"
aiturk hedef "goal" --project . -m <model>
aiturk media list --jsonDo not add the TurkServis MCP server to Claude Code or Codex when the AITURK CLI is installed. The MCP steps below are for clients that cannot run commands.
0. If you installed the CLI
Type aiturk in your terminal and follow the prompts. Claude Code and Codex need no further setup; the MCP steps below are only for clients that cannot run commands.
MCP for clients that cannot run commands (Cursor, Cline, LibreChat and similar)
Use this path only when your client cannot run the aiturk command, or while the AITURK CLI is not installed or aiturk doctor reports a failure. Over MCP the teams return advice, research and media; they cannot read your files or run commands.
1. Load the key for this session
Use an input method that keeps the secret off the screen and out of command history.
# PowerShell
$secret = Read-Host "TurkServis API anahtarı" -AsSecureString
$env:TURKSERVIS_API_KEY = [Net.NetworkCredential]::new("", $secret).Password# macOS / Linux
read -rsp "TurkServis API anahtarı: " TURKSERVIS_API_KEY
export TURKSERVIS_API_KEY
printf '\n'2. Clients that read TOML settings
This block doesn't change your model or provider. It only adds the TurkServis advisor tools and keeps the prompt behavior for tool approval.
[mcp_servers.turkservis]
url = "https://ai.turkservis.online/mcp"
bearer_token_env_var = "TURKSERVIS_API_KEY"
tool_timeout_sec = 1800
enabled = true
default_tools_approval_mode = "prompt"Add this block to your client’s user-level TOML settings file, preserving your existing settings. Do not add it to Codex when the AITURK CLI is installed: Codex reaches TurkServis teams through the aiturk commands, and the helper skill package writes no MCP entry.
3. Clients that read JSON settings (Cursor, Cline and similar)
Your client must support HTTP MCP and environment variable expansion in headers. Merge the block below into your client’s MCP settings file, preserving existing settings. Do not add it to Claude Code when the AITURK CLI is installed: Claude Code reaches TurkServis teams through the aiturk commands.
{
"mcpServers": {
"turkservis": {
"timeout": 1800000,
"type": "http",
"url": "https://ai.turkservis.online/mcp",
"headers": {
"Authorization": "Bearer ${TURKSERVIS_API_KEY}"
}
}
}
}4. Verify the connection and permissions
Open the tool list in your client and check that only the advisor and research tools you expect are visible. Read the tool approval request on the first call. If an unexpected tool asks for file, command, repository, or merge access, disable the server and report it to [email protected] with the details.
5. Optional local Assist engine
aiturk assist diagnose --project . --goal "..." makes the CLI gather local file and test evidence; the public MCP processes only explicitly selected text, diffs and evidence. --max-workers 20 caps the shared CLI/MCP pool within one parent task. File writing never turns on without the selected profile and task permission.