aictrl

dev.aictrlPublished by aictrl.devOfficial publisherv1.0.0-beta.3Updated Nov 7, 2026

Project context, backlog tasks, and controlled workflows for coding agents. OAuth sign-in.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper ToolsAI & ML

Overview

AI-generated overview

Hosted MCP server that gives coding agents project context, backlog tasks, code-review findings and controlled workflow execution on aictrl.dev.

What you can do
  • Read project context and account readiness for your aictrl organization
  • List backlog tasks and published workflows available to you
  • Retrieve code-review findings from the hosted service
  • Start published workflows under their permissions and approval gates
  • Pair with bundled engineering skills for issue creation, implementation, code review and root-cause analysis
When to use it
Use it when your coding agent should work from an aictrl organization's backlog and project context, or when you want reviewed pull requests produced through aictrl.dev's controlled, approval-gated workflows instead of purely local runs.
Requirements
Remote Streamable HTTP endpoint at aictrl.dev/mcp; no API key or local process. Needs an aictrl account and membership of an aictrl organization, plus OAuth sign-in through the browser. Repository-backed work also needs a GitHub repository connected via the aictrl GitHub App.
Before you install
OAuth grants the server access to your organization's project data, following your membership. Workflow execution can start real cloud jobs that change repositories and may incur costs, bounded by the workflow's permissions, approval gates and cost limits. The hosted server's source is private, and what it collects is described only in its privacy policy and terms.

Installation

In SourceWeft

  1. Open aictrl in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.aictrl%2Faictrl/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "aictrl": {
      "type": "http",
      "url": "https://aictrl.dev/mcp"
    }
  }
}

README

[GitHub Stars] [Skills]

aictrl.dev engineering skills and plugin

Essential, vendor-neutral AI engineering skills for the AI SDLC: turning bug reports and requests into well-defined issues, root-cause analysis, implementing changes, code review and explaining pull requests. Install the skills alone, or install the aictrl.dev plugin to add the same skills plus OAuth-connected workflows that run in the cloud on aictrl.dev, turning backlog work into reviewed pull requests.

aictrl MCP server

The hosted aictrl MCP server gives coding agents access to project context, backlog tasks, code-review findings, and controlled workflow execution. Connect to https://aictrl.dev/mcp using Streamable HTTP and sign in with OAuth. No API key or local server process is required.

You need an aictrl account and membership of an aictrl organization. Repository-backed work also needs a GitHub repository connected through the aictrl GitHub App. Access follows your organization membership; workflow execution follows the published workflow's permissions and approval gates.

GitHub Copilot in VS Code:

  1. Open the Command Palette and run MCP: Add Server.
  2. Choose HTTP (HTTP or Server-Sent Events) and enter https://aictrl.dev/mcp. Name the server aictrl and choose the configuration destination.
  3. Start the server from VS Code's MCP controls and complete the browser sign-in when prompted.

See VS Code's MCP setup guide for configuration destinations and server controls.

In other MCP clients, add the same remote URL and complete OAuth when prompted. The Claude Code and Codex plugins below already include the MCP configuration. See SETUP.md for connection checks and troubleshooting.

Try these prompts after connecting:

  • "Check my aictrl account readiness."
  • "Which aictrl organizations can I use?"
  • "Show the backlog tasks for my organization."
  • "List the published workflows I can run."

This public repository contains the skills, client configuration, and registry metadata for the hosted service. The hosted server's source code is private.

Install

Skills only — Codex, Claude Code, OpenCode, and compatible agents

bash
npx skills add aictrl-dev/skills

Claude Code plugin

/plugin marketplace add aictrl-dev/skills/plugin install aictrl@aictrl-public

Codex plugin

bash
codex plugin marketplace add aictrl-dev/skills --ref maincodex plugin add aictrl@aictrl-public

OpenCode — install the skills with npx skills add aictrl-dev/skills, then add the connected-workflow server to opencode.json and sign in:

json
{ "mcp": { "aictrl": { "type": "remote", "url": "https://aictrl.dev/mcp", "enabled": true } } }
bash
opencode mcp auth aictrl

Cursor / direct OpenCode skills — skills use the cross-tool Agent Skills standard:

git clone https://github.com/aictrl-dev/skills && cd skills./scripts/install.sh cursor       # or: opencode | all

…or copy skills/* into your tool's skills dir (~/.cursor/skills, ~/.config/opencode/skills).

Then ask for the task naturally or invoke a supported slash command, for example /create-issue, /implement-code-change, /code-review, /create-workflow, or /execute-workflow.

The Skills

SkillWhat it doesTry it
create-issueVague feature or chore → code-grounded issue with scope, acceptance criteria, tests, risks, and open questions./create-issue
create-bugSymptoms or regression → reproducible, evidence-backed bug and regression-test requirement./create-bug
spec-reviewIssue/spec → repository-grounded readiness verdict and concrete gap fixes./spec-review
implement-code-changeIssue → tested, reviewed, merge-ready PR locally or through an optional connected workflow./implement-code-change
create-prExact revision + evidence → concise reviewer-ready PR title and body, with rollout and verification claims kept honest./create-pr
code-reviewExact PR head → actionable correctness, security, reliability, and test findings; no code changes./code-review
judge-review-findingsCurrent-head findings → TRUE/FALSE/UNCERTAIN plus FIX/DEFER/IGNORE judgments./judge-review-findings
reply-to-code-reviewAccepted review findings → fixes, verification, evidence-backed replies, and bounded re-review./reply-to-code-review
root-cause-analysisIncident or recurring failure → evidence-driven causal analysis, sibling exposure map, and prevention portfolio./root-cause-analysis
create-workflowWorkflow intent → validated aictrl.dev workflow v2 YAML with portable inline task nodes./create-workflow
execute-workflowPublished workflow → explicitly authorized, idempotent start with safe monitoring, gates, cancellation, and durable handoff./execute-workflow
design-reviewDrop an HTML mock or screenshot — get a sharp, located critique across IA, value prop, hierarchy, trust/friction, and a11y. Ends with "Fix these 3 first."/design-review path/to/mock.html
measurement-planFeature → structured measurement plan: learning objectives, metrics table, product-analytics events, warehouse changes, event pipeline./measurement-plan
recording-product-demoPoint it at a repo with a web UI — it boots the app, preps demo data/auth, records a time-locked Playwright demo synced to prepared narration from your selected speech tools, and builds a publish kit (MP4 + captions + embed)./recording-product-demo
explain-changePR, commit range, or design document → a grounded technical explainer of the design, difficult trade-offs, and real rollout state./explain-change
ui-polishPoint it at a screen — it renders phone and desktop, measures what screenshots hide (column alignment, field widths, labels, tap targets, contrast, dead space), fixes the source and re-measures until the checks pass./ui-polish
ux-testingPoint it at a page or prototype and a few tasks — AI testers act as first-time users through the accessibility tree or screenshots, success is verified from page state (not the tester's claim), then a design-review and fix loop re-tests into a before/after scorecard. Optional simulated users screen layout hypotheses./ux-testing path/to/page.html

design-review in action

Input: a SaaS landing page mock.

Value Proposition — WEAK  Hero headline "Workflows made simple" says nothing about what the product does.  Fix: replace with a one-liner that names the user, the problem, and the outcome.
Actionability — BROKEN  Three competing CTAs above the fold (Start free, Book demo, Watch video).  Fix: one primary CTA above the fold; demote the others below.

Every critique names the element. Every fix is concrete. No generic "improve clarity."

ux-testing in action

On an internal work-queue design, novice agent testers asked to start the most important ready work approved a security review instead (v5: 2 of 2). After the fix loop moved the ready work above the approvals, 3 of 3 started the right issue. Simulated users reproduced the same trap (72% clicked Approve), and checks against page state caught a tester who reported success after creating nothing. Write-up: AI usability testing on a backlog design.

Why these exist

These skills are free and standalone. aictrl.dev adds controlled remote execution, approvals, policy, history, integrations, and cost limits. implement-code-change can use an optional connected workflow, and execute-workflow safely operates an existing published workflow; local mode remains available for every launch skill except the connected-only execute-workflow.

The Claude and Codex plugins and the skills.sh install all consume the root skills/ directory directly. There are no vendor-specific copies to repin or hand-edit. Connected execution always uses the aictrl MCP identity at https://aictrl.dev/mcp; OAuth is requested only when a connected workflow is used.

Privacy, terms and support

The skills run locally and send nothing to aictrl.dev. The bundled aictrl MCP server is used only when you connect it with OAuth; what it collects and keeps is described in the privacy policy and terms. Support: aictrl.dev/support or [email protected]. Security reports: security.txt. Setup guidance for the MCP connection is in SETUP.md.

Optional third-party services and keys

Bundled helpers in two skills can send data to a third-party service, only in the steps below and only when you run them. Nothing runs on install. A key is read only for its step, sent only to the service named in that row, and never printed, logged or stored. Each key belongs to the service it is sent to: Google credentials go only to Google, the TypeSafe key only to TypeSafe, and a custom simulator key only to the endpoint you set alongside it. The bundled aictrl MCP server never receives any of them.

Narration is prepared using the user's selected speech tools (for example, ElevenLabs) or supplied as audio plus measured word timestamps. Those tools receive the narration text/audio under their own configuration. The plugin does not include a narration API client or read speech-provider credentials; its splitter processes the prepared files locally.

No other skill sends data to a third-party service; the browser-based skills (ui-polish, ux-testing) load only the app URL you give them.

SkillStepService and what is sentEnvironment variables read
recording-product-demoUpload to YouTube (publish.cjs --upload with publish.upload.type youtube, opt-in)Google (oauth2.googleapis.com, www.googleapis.com): the rendered MP4, title and description, uploaded to your own channelYT_CLIENT_ID, YT_CLIENT_SECRET, YT_REFRESH_TOKEN
recording-product-demoUpload to a bucket (publish.cjs --upload with publish.upload.type gcs or s3, opt-in)Google Cloud Storage or Amazon S3, through your own gcloud storage cp or aws s3 cp: the whole publish kit (MP4s, poster, captions, embed page, PUBLISH.md) to the bucket path you configureNone: the CLI uses its own signed-in credentials
ux-testingSimulated users (optional; agent testers need no key)TypeSafe (api.typesafe.ai), or an endpoint you set: the page state and candidate actions for each simulated stepTYPESAFE_API_KEY (optional UX_SIM_MODEL overrides the default model), or UX_SIM_ENDPOINT + UX_SIM_API_KEY + UX_SIM_MODEL

Without these variables the local demo pipeline still runs with prepared narration; an explicitly requested upload reports missing configuration, and ux-testing continues with agent testers only. UX_VERIFY_TOKEN is a local token between the ux-testing scripts and their own local server; it is never sent off the machine.

Contributing

PRs that add skills are welcome — see CONTRIBUTING.md. Release owners should also follow the public plugin release runbook.

Source: README.md at commit e494d66

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.0-beta.3LatestOct 29, 2026
  2. v1.0.0-beta.2Oct 26, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Aictrl integrations

aictrl

Published by GitHub account vasparshin

A remote governance layer for AI coding agents, offering knowledge-graph grounding, session audit and policy controls through a hosted endpoint.

Streamable HTTPWeb executable
Developer ToolsNot indexed yetOct 25, 2026