What you can do with Aki MCP Server

Fix a bug from your phone

You are away from your desk and a bug report lands.

1. 1Open Claude or ChatGPT on your phone and describe the bug.
2. 2It searches the repo, reads the files, and checks git status and the diff.
3. 3It edits the file inside the folder you allowed, then runs your typecheck or tests.
4. 4It shows the diff and sends a desktop notification when the fix is done.

QA a web app in a real browser

Verify a change end-to-end without opening your IDE.

1. 1It checks your dev server and the port it runs on.
2. 2It launches a Chrome profile clone that keeps your existing login session.
3. 3It navigates, interacts with the page, and captures screenshots.
4. 4It reports issues with clear reproduction steps.

Debug an API in Postman

Iterate on a request and its tests hands-free.

1. 1It inspects the request currently open in Postman.
2. 2It sends the request and reads the response and test results.
3. 3It adjusts the request or the tests as needed.
4. 4It re-runs and confirms the fix.

Check on a running job from anywhere

A long build or training run is going and you want a status update.

1. 1Ask the AI to check the background task and tail its log.
2. 2It reads the latest lines and summarizes progress or errors.
3. 3If needed, it cleans temp files or restarts a permitted task.

Scheduled, unattended automation

Pair Grok scheduled prompts with your local server, with nobody at the keyboard.

1. 1A scheduled prompt fires at the time you set.
2. 2It runs the permitted task on your machine: build, cleanup, or a code pull.
3. 3It reports back and can send a desktop notification when done.

Requires your machine to be powered on with the server running when the schedule fires.

Understand a new codebase fast

You just cloned a repo and need the lay of the land.

1. 1It maps the project with a whole-tree path and content search.
2. 2It reads the entry points and key config files.
3. 3It reviews recent git history to see what changed lately.
4. 4It gives you a plain-language tour: structure, stack, and where to start.

Review a change before you merge

A branch is ready and you want a second pair of eyes.

1. 1It reads the git diff and the files it touches.
2. 2It runs your read-only checks, such as typecheck or tests, if they are in your allowlist.
3. 3It flags risky changes, missing tests, or unclear naming.
4. 4It summarizes what the change does and what to double-check.

Writing actions like committing stay off by default; you approve them explicitly.

Ask questions about a local database

You need an answer that lives in a SQLite file.

1. 1It reads the database schema to understand the tables.
2. 2It runs read-only queries to answer your question.
3. 3It explains the result in plain language.

Smoke-test a local API

You want to know if your dev server behaves.

1. 1It checks the dev server and the port it runs on.
2. 2It calls your local endpoints with the SSRF-protected fetcher.
3. 3It reads the responses and reports status, shape, and errors.

Reproduce and capture a UI bug

A bug only shows up in the browser with your logged-in session.

1. 1It launches a Chrome profile clone that keeps your login.
2. 2It navigates to the exact screen and repeats the steps.
3. 3It captures screenshots and reads the console for errors.
4. 4It writes up clean reproduction steps.

Draft release notes from git history

A release is coming and the changelog is empty.

1. 1It reads recent git log and diffs.
2. 2It groups changes into added, changed, and fixed.
3. 3It drafts human-readable notes and copies them to your clipboard.

Tidy a cluttered folder

Downloads or a temp folder has gotten out of hand.

1. 1It searches for large or old files and lists what it finds.
2. 2It groups them so you can decide what to keep.
3. 3With your approval, it removes the ones you confirm.

Deleting needs a write command you add to the allowlist; nothing is removed without your say-so.