Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
AimYear
Overview
Description from the maker (original English)
Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.aimyear.com/mcpRun this in your terminal
claude mcp add --transport http aimyear https://mcp.aimyear.com/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"aimyear": {
"url": "https://mcp.aimyear.com/mcp"
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"aimyear": {
"type": "http",
"url": "https://mcp.aimyear.com/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.aimyear.com/mcpMenu names can differ slightly by plan and over time.
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.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Yahhi, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 18326 servers in this category
- Published to the registry more recently than 68% of the other 18326 servers in this category
- Basic checks equal to or better than 100% of the other 18326 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is AimYear safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.2) reached the registry 20 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Signoff
by ayuanxx-max
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Runs on your computerUpdated today
Install
README from the maker
Open the README
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.
AimYear MCP server
An accountability partner inside the AI agent you already use. Connect AimYear to Claude, Claude Code, ChatGPT or any MCP client, and your agent keeps one big aim for your year, plans one main step a day toward it, runs the timer while you work and writes down what actually got done. When you start comfortable work while the main step is still open, it asks you to do the step first.
Built for indie developers and makers who build all day but keep postponing the work that moves the goal: selling, talking to users, publishing.
- Free: sign-in on any number of devices, aims, plans, routines, time tracking and reviews through your own agent. No AI runs on AimYear's side, so there are no AI costs.
- Pro ($49/year or $8/month, with the coming phone app): notifications, reviews written by AimYear, AimYear's own AI coach and Google Calendar sync.
Website: aimyear.com · Setup guide: aimyear.com/connect.html · Privacy: aimyear.com/privacy.html · Contact: privacy@aimyear.com
Connect (about a minute)
Endpoint: `https://mcp.aimyear.com/mcp` (Streamable HTTP, OAuth sign-in with Google, Apple or email). Nothing to install.
- Claude (web, desktop, mobile): Settings → Connectors → Add custom connector → paste the endpoint → Connect, then sign in.
- Claude Code:
claude mcp add --transport http aimyear https://mcp.aimyear.com/mcp, then/mcp→ aimyear → Authenticate. - ChatGPT (paid plans, developer mode): Settings → Apps & Connectors → Advanced settings → turn on Developer mode. Then Apps & Connectors → Create: name
AimYear, URL the endpoint above, authentication OAuth → Create, then sign in. - Other MCP clients: add the endpoint as a remote (HTTP) server with OAuth.
Then say: *"Help me set my aim for this year"*. The agent checks that the aim is countable, builds the path of stages, and from then on: *"plan my day"*, *"start the timer"*, *"how was my week?"*.
The skill that teaches an agent the method is in skills/aim/SKILL.md.
What happens to your data
The server stores what your agent saves through the tools (aim, path, plans, sessions and their summaries) in Google Cloud Firestore. Your conversation stays with your agent's provider; AimYear only receives the tool calls. Logs keep the tool name, success and timing, never argument values. To delete your account and data, email privacy@aimyear.com. Details: privacy policy.
Tools (43)
Names say what a tool does: get_ reads one thing, list_ reads several, find_ looks for problems, set_ replaces a whole list, add_ / edit_ / delete_ change one entry.
| Group | Tools |
|---|---|
| Aim | get_goal, check_goal_draft, set_goal, record_progress, set_levers, set_projects |
| Path | get_path, set_milestones, edit_milestone, add_steps, edit_step, delete_step, next_steps |
| Week | get_commitments, set_commitments, get_capacity |
| Day | get_planning_context, get_plan, set_plan, edit_plan_item, delete_plan_item, set_day_mode, get_routines, set_routines |
| Timer and sessions | get_now, start_session, add_note, split_attention, stop_session, stop_timer, add_session, edit_session, delete_session, list_sessions, find_gaps |
| Reviews | summarize_day, summarize_week, find_leaks |
| Settings and devices | get_settings, set_settings, add_device, list_devices, delete_device |
0.4.2 adds the hard-first check: set_plan warns when nothing in the day is on a hard lever, and add_steps / set_levers warn when a stage starts with preparation before the first hard-lever step. The server instructions tell every agent the same rule.
0.4.0 adds routines: small steps that repeat on fixed weekdays ("talk with one person on Reddit"). The server adds them to each matching day's plan, so every device and agent sees the same checks; get_now lists the open ones and summarize_week counts them.
0.3.0 renamed most tools (0.2.x names stop working) and added the editing tools: edit_session, delete_session for finished sessions, edit_milestone, delete_step, edit_plan_item, delete_plan_item, set_projects, and get_settings / set_settings with the timezone.
Protocol details
Stateless Streamable HTTP, POST only. Sign-in is OAuth 2.1 with PKCE and dynamic client registration. The sign-in page uses the same Firebase project as the AimYear app, so the app and every connected AI share one account and one history. Guest (anonymous) accounts cannot be connected. Every tool acts as one signed-in person; see docs/ACCESS.md.
Without a token, the server describes itself (initialize, tools/list, prompts/list, ping); everything else answers 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource/mcp.
Retry-safe writes for apps (0.7)
The server is the source of truth, and a phone may deliver a request long after the tap, or twice. So stop_session, start_session, add_session, add_note, add_steps and delete_session take an optional op_id: an id the app mints before its first attempt and reuses on every retry. The write is applied once; a retry gets the first answer back and writes nothing. Applied ops live in users/{uid}/ops/{op_id} (tool, sessionId, result, at, expiresAt) and are written in the same Firestore transaction as the change they record. Give the ops collection a TTL policy on expiresAt (30 days) in the Firestore console.
stop_session takes end_at and start_session takes start_at (ISO 8601) so a stop queued offline at 14:05 and delivered at 16:40 records 14:05. start_session also takes the app's own session_id (create-if-absent). A request with op_id, end_at or start_at must name its session_id: the server never guesses which session a replay means. Without them, an agent's stop_session / delete_session acts only on its own connection's single running session, and otherwise lists the running sessions with ids.
Two devices can stop one session; the result is the same whatever order the stops arrive in: the earliest end wins (once anyone stopped it, it was not running), done wins over any other outcome, the first summary stays and a different later one goes to the notes. Every stop is kept in the session's stops[], and the answer says applied: ended | shortened | recorded.
The rest of this file is for working on the server itself. You don't need it to use AimYear.
How it is built
| File | What it does |
|---|---|
src/http.ts | The Express app: the MCP endpoint, the OAuth routes, the menu bar endpoints. |
src/access.ts | One table: every MCP method, tool and route → public / auth / admin, with the reason. Every gate reads it. |
src/oauth.ts | OAuth storage in Firestore (codes and tokens stored as SHA-256 hashes) and the sign-in/consent page. The protocol itself is the MCP SDK's mcpAuthRouter. |
src/calllog.ts | One structured log line per MCP call: method, tool, ok, error code, latency, user, client. Never argument values. |
src/tools.ts | Tool registration, annotations (read-only / destructive / idempotent) and the server instructions. |
src/service.ts, src/domain/ | The rules: goal rubric, classification, attention, plans, sessions. |
src/surface.ts | The surface fingerprint behind surface.lock.json. |
.githooks/pre-commit | Regenerates docs/ACCESS.md from src/access.ts and stages it on every commit, so the committed table can't drift (npm ci points core.hooksPath at it through the prepare script; test/access.test.ts still fails on a stale file). |
Data lives in Firestore under users/{uid}/aim/{goal,path,profile}, users/{uid}/days, users/{uid}/sessions, users/{uid}/blocks, users/{uid}/ops (applied op_ids, TTL on expiresAt); OAuth under oauth_clients, oauth_requests, oauth_codes, oauth_tokens; reminders in pending_notifications (claimed by a transactional delete before each push).
Run locally
npm install && npm run buildstdio, one person:
claude mcp add --scope user aimyear -e AIMYEAR_UID= -- node $PWD/dist/index.js
HTTP:
AIMYEAR_TOKENS="sometoken= " PORT=8787 node dist/index.js --http
Credentials: a Firebase admin service account at ~/.aimyear/service-account.json (or AIMYEAR_SERVICE_ACCOUNT= ; falls back to Application Default Credentials).
Env: AIMYEAR_UID (stdio), AIMYEAR_TOKENS (HTTP: static token=uid pairs for Claude Code scripts, the menu bar app and the scheduler), AIMYEAR_BASE_URL (the public URL; the OAuth issuer), AIMYEAR_ALLOWED_ORIGINS (extra browser origins), AIMYEAR_WORKPLACE, AIMYEAR_TZ.
Tests
npm test # access table guard, anonymous gate and batch smuggling, OAuth discovery,annotations, Origin, version negotiation, surface lock, domain rules
npm run test:conformance # a client's path through the real HTTP entry point: initialize and
tools/list without a token, then every tool with a throwaway user
in the real Firestore; cleans up
CONFORMANCE_URL=https://mcp.aimyear.com/mcp npm run test:conformance # read-only tools, live npm run test:oauth # register → consent → real Firebase ID token → code → token (PKCE) →
tool call → refresh rotation, plus every refusal; cleans up
npx tsx test/smoke.ts # the service end to end against Firestore
When you add a tool: give it an entry in src/access.ts (npm test fails without one), run npm run access-doc, bump src/version.ts, run npm run surface-lock.
Hosted (Cloud Run)
gcloud run deploy aimyear-mcp --source . --project aimyear-app --region us-central1 --quietEnv vars on the service: AIMYEAR_TOKENS, AIMYEAR_TZ, AIMYEAR_PROJECT, AIMYEAR_BASE_URL=https://mcp.aimyear.com. mcp.aimyear.com is a Cloud Run domain mapping (CNAME to ghs.googlehosted.com in Route 53) and is in Firebase Auth's authorized domains. Health: /health. The legacy URL https:// /c/ /mcp still works.
Call analytics: scripts/mcp-calls.sh [1d] prints calls per tool and the call sequences per person and client.
License
FSL-1.1-MIT: you can read, run, self-host and change this server, but not offer it as a competing commercial service. Each release becomes MIT two years after it is published. The hosted service is at https://mcp.aimyear.com/mcp.