Search / ai.annsa/annsa
protogridR0· no sign-inAI agent management: choose what to build, direct every agent from one plan, and learn as you go.
v1.0.4 · active · website · descriptor JSON · versions
{
"mcpServers": {
"annsa": {
"type": "http",
"url": "https://app.annsa.ai/mcp"
}
}
}claude mcp add --transport http annsa https://app.annsa.ai/mcp[mcp_servers.annsa]
url = "https://app.annsa.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"annsa": {
"type": "remote",
"url": "https://app.annsa.ai/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"annsa": {
"type": "http",
"url": "https://app.annsa.ai/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=annsa&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBwLmFubnNhLmFpL21jcCJ9"
}{
"servers": {
"annsa": {
"type": "http",
"url": "https://app.annsa.ai/mcp"
}
}
}{
"mcpServers": {
"annsa": {
"httpUrl": "https://app.annsa.ai/mcp"
}
}
}extensions:
"annsa":
enabled: true
name: "annsa"
type: streamable_http
uri: "https://app.annsa.ai/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltool list is cacheable (ttlMs 300000)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations8 of 8 tools declare readOnlyHint or destructiveHinttools.directory_hints5 of 8 tools declare all four hints; missing: annsa_priorities (destructiveHint, idempotentHint); annsa_spec (destructiveHint, idempotentHint); annsa_ask (destructiveHint, idempotentHint)tools.token_costabout 5,608 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history recorded for 0 of the 7 days neededNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% +updated-1d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
[email protected] npmthis version is not known to the dependency resolver
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://app.annsa.ai/mcp streamable-http | none | yes | 100% | 1514 ms | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26 | 2026-10-20 |
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
annsa | npm | 1.0.4 | – |
annsa_askread-only | Answers a question about your feedback data (the default): search and synthesis across feedback, priorities, specs and outcomes, such as rankings, 'what can I safely park?', 'what should I ship next?', 'what am I missing?', 'did feedback go quiet after we shipped X?'. about='annsa': how Annsa works, from its docs, or a file with `topic`. about='surveys': every survey, where it runs and its response count. about='customer': one person's feedback, priorities, ships, transcripts and account facts; give `customer` (name, email or id), and `account` to narrow; an ambiguous name returns candidates. A read. Names and quotes follow the workspace's per-surface setting. annsa.help and annsa.surveys are older names for two modes. [production · app.annsa.ai] |
annsa_boarddestructive | Arrange the board: stage, severity, merge, regroup, park, correct, bets, assign, retract, pick, cut, direction. Returns the change and its undo. Skill: annsa-working (annsa.ask topic=working). [production · app.annsa.ai] |
annsa_decidedestructive | Answer a Needs you question, sign a decision, approve or dismiss a proposed spec update, propose or retire a principle. Skill: annsa-working (annsa.ask topic=working). [production · app.annsa.ai] |
annsa_file | Put new rows into the record: feedback or a finding, a priority from a title, a transcript, a direction doc's lines. Returns where each row went. Skill: annsa-working (annsa.ask topic=working). [production · app.annsa.ai] |
annsa_prioritiesread-only | Lists the ranked active priorities (open, ready, building) with trend, confidence and evidence counts. `stage` reads shipped, shared or closed instead. `weekly: true` returns the weekly digest; `view: 'radar'` what is rising, shipped and quiet. `priority_number` returns one row, `mine: true` this seat's rows, `picked: true` a person's picked list, `release_number` one release. Rows carry `next_action` when something waits on an agent; the spec carries the open asks (`decision`), principles and authority; a shipped priority that customers report again comes back open with `came_back`. A read. [production · app.annsa.ai] |
annsa_sharedestructive | Tell the customers who asked that their priority shipped, by email or the widget. An email cannot be unsent. Skill: annsa-working (annsa.ask topic=working). [production · app.annsa.ai] |
annsa_specread-only | Full engineering spec for a priority. The document has 5 sections: Problem, Signals and direction, What to build, Files to touch, Done When. Alongside it, as linked records rather than prose: Verification status, Decision, Evidence, Activity, Details. Takes priority_number, priority_id or spec_id. The read is short: Problem, What to build, Done When, `ruled_out`, and `decision` (the open asks), `authority` (what a sign delegated: may_decide, must_come_back, answered_by) and `principles` when a person set them; an escalate on a may_decide topic is not raised. `include_signals` adds Signals and direction, Files to touch and `evidence`; `include: repo_rules` adds the repo's agent files. Pending section changes come back as `updates`. `batch: true` exports specs as markdown by stage and ship date; `status: 'shipped'` with no id lists what shipped, and empty means nothing has. `investigate: true` returns a deep dive instead: trajectory, linked feedback, memory, related briefs. A read. [production · app.annsa.ai] |
annsa_work | Do the work on a priority, and settle routine asks with undo. Ship records completion; it deploys nothing. Skill: annsa-working (annsa.ask topic=working). [production · app.annsa.ai] |
Schemas: list_tools.
{
"name": "ai.annsa/annsa",
"title": "Annsa",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://app.annsa.ai/mcp",
"type": "streamable-http"
}
],
"version": "1.0.4",
"packages": [
{
"version": "1.0.4",
"transport": {
"type": "stdio"
},
"identifier": "annsa",
"registryType": "npm"
}
],
"websiteUrl": "https://annsa.ai",
"description": "AI agent management: choose what to build, direct every agent from one plan, and learn as you go."
}