Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Unofficial CLI and MCP server for the Toptal Talent platform — personal-productivity tool
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ttctl": {
"command": "npx",
"args": [
"-y",
"ttctl"
]
}
}
}Run this in your terminal
claude mcp add ttctl -- npx -y ttctlPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ttctl": {
"command": "npx",
"args": [
"-y",
"ttctl"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ttctl": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ttctl"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account alexey-pelykh, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Personal-productivity CLI and MCP server for your own Toptal Talent profile.
TTCtl is NOT affiliated with, endorsed by, or supported by Toptal LLC. It is a personal-productivity tool that interacts with Toptal Talent's web/mobile interfaces using your own session, exclusively for your own profile's data.
This tool is built for fair use and shared in case it's useful to other Toptal talents who want similar tooling for their own profiles. It is NOT to be used for:
If you encounter misuse of TTCtl, please see Abuse reporting in SECURITY.md.
Architectural friction in the codebase (sequential rate limits, single-credential design, no batch parallelism on automation-prone endpoints) is intentional. Don't remove it.
"Toptal" is a trademark of Toptal LLC. The name appears in this project's description as nominative fair use only — TTCtl is not a Toptal brand.
TTCtl gives you (and your AI assistants, via MCP) programmatic access to your own Toptal Talent profile:
applications stats; confirm / reject open Interest Requests via applications confirm / applications reject; fetch interview detail (interviewer with TopChat thread handle, client-side contact, scheduled slot, agenda link, prep-guide ref) via applications interview show ; read your interview prep notes via applications interview notes show ; fetch availability-request detail (status, kind, recruiter Fixed rate, comment, lifecycle timestamps, job) via applications availability-request show engagements statsjobs recommended feed, the per-job jobs match-quality match-score breakdown, and the per-job jobs rate-insight rate-intelligence panel); manage saved / viewed / not-interested signals; configure search subscription; direct-apply via jobs apply --consent (legal-compliance gate is mandatory). Add --suggest-answers to fetch your own historical answers to similar prior questions as advisory autocomplete suggestions (opt-in, off the critical apply path; failures degrade gracefully). The MCP tool ttctl_jobs_apply_similar_answers exposes the same surface to agents.payments summary), and payment methods; show current hourly rate via payments rate current (lightweight) or the unified payments rate show projection; submit rate-change requestsSurfaces are gated to read-heavy / personal use. Operations that would enable mass automation against the platform are deliberately not exposed.
The following Toptal Talent surfaces are out of scope by design — they enable abuse (mass-automation or spam vectors), require third-party SDKs TTCtl doesn't depend on, target client-onboarding rather than the talent-side workflow, belong to staff- or sourcing-side workflows, or are one-time / mobile-only UI affordances with no recurring CLI value:
UpdateJobAlertSettings, UpdateSmsNotificationsSettings, UpdateTimesheetReminderSettings, UpdateNotificationSetting (abuse-prevention — silencing alerts is a precursor to other abuse)applications interview show (full surface tracked in #23)SEND_CONTRACTS, testimonial publishing, snapshot history (staff-side — Toptal-staff surfaces, not talent-side)CreateTalentSignal, GetTalentSignalSetup (sourcing-side — recruiter / staff identifying talent, not talent-side)Note: The
scheduler.toptal.comsurface (interview scheduling) is currently absent rather than out by design — deferred until reverse-engineering research closes.
See What It Does above for the positive scope.
op) for credential resolutionTTCtl uses node-wreq for Chrome TLS-fingerprint impersonation on the Cloudflare-protected surfaces (profile editing). That transport ships as a prebuilt native binary, available for:
| OS | Architecture | libc | Supported |
|---|---|---|---|
| macOS | x64 (Intel) | — | ✅ |
| macOS | arm64 (Apple Silicon) | — | ✅ |
| Linux | x64 | glibc | ✅ |
| Linux | x64 | musl (Alpine) | ✅ |
| Linux | arm64 | glibc | ✅ |
| Linux | arm64 | musl (Alpine) | ❌ not yet |
| Windows | x64 | — | ✅ |
| Windows | arm64 (Windows on ARM) | — | ❌ not yet |
On an unsupported platform, npm install -g ttctl still succeeds (the native binary is an optional dependency) and mobile-gateway commands keep working — but any Cloudflare-protected command (anything that edits your profile) fails with a clear NATIVE_MODULE_UNAVAILABLE error naming your platform and this supported set. If you need one of the two not-yet-supported targets, please open an issue.
npm install -g ttctl
Or run directly with npx:
npx ttctl --help
For maximum supply-chain safety, install with postinstall hooks disabled:
npm install -g --ignore-scripts ttctl
--ignore-scripts blocks preinstall / postinstall / prepare hooks across the entire dependency tree at install time. This prevents a compromised transitive dep (PhantomRaven, Shai-Hulud, etc.) from executing code on your machine during install — closing the most-exploited supply-chain attack vector against package-manager users.
TTCtl itself ships no install-time hooks. Disabling them is purely a defense against malicious behavior in dependencies you don't directly control. See SECURITY § User-install supply-chain hardening.
# 1. Install
npm install -g ttctl
op CLI is installed) or Form B (literal credentials,ttctl auth init
ttctl auth signin
ttctl auth status
ttctl profile show
`ttctl auth init` scaffolds a fresh
~/.ttctl.yamlinteractively. Choose Form A (1Password reference, recommended) or Form B (literal credentials, discouraged — guarded by an explicit warning). On Form A with theopCLI installed, a vault picker and a LOGIN-category item picker run. Withoutopor on JSON-shape failure, the prompt falls back to a freeformop://VAULT/ITEMreference. The output file is written atomically at mode0600and refuses to overwrite an existing file unless--forceis passed. The command is interactive only — pipe stdin or a non-TTY context exits non-zero with a clear message.
`ttctl auth signin` runs the
EmailPasswordSignInGraphQL mutation, captures the session bearer, and writes it BACK into the same~/.ttctl.yamlfile underauth.token(atomic write; comments preserved; mode0600). All subsequent commands replay it asAuthorization: Token token=on every GraphQL request. TheopCLI is invoked only at signin time to resolve your credentials. There is no separate token file — your config and your live session live in one YAML.
Hand-authoring the config also works (drop a YAML file at
~/.ttctl.yaml,chmod 600); see the Configuration section below for the four validauthshapes.ttctl auth initis the recommended starting point.
TTCtl uses a single config file — no profiles. The config-file path is resolved deterministically (highest precedence wins):
--config flag — explicit override (per-invocation).TTCTL_CONFIG_FILE env var — process-scoped (CI, direnv).~/.ttctl.yaml — POSIX home dotfile (only fallback).XDG paths ($XDG_CONFIG_HOME/ttctl/config.yaml, ~/.config/ttctl/config.yaml) and the current-working-directory ./.ttctl.yaml are not auto-discovered. To use a project-local config, point TTCTL_CONFIG_FILE at it via direnv:
# .envrc in your project root (requires `direnv` installed and `direnv allow` run)
export TTCTL_CONFIG_FILE="$PWD/.ttctl.yaml"
TTCtl refuses to persist the captur
Only the beginning is shown; read the rest in the repo