List your agent

ainote

MCP server● Hosted · onlineInstallablev1.3.2

Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate business workflows.
All AI agents to automate business workflows, ranked →

Similar tools

Listed for the same task: automate business workflows

Reviews

No review yet. Used ainote? Be the first to help others choose.

What it does

ainote is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

From the publisher's description, Electra Index matched it to one capability: api integration. That makes it a candidate for tasks such as automate business workflows or build an internal tool.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version1.3.2
Packagesnpm
PriceNot in the registry
First seen26 Sept 2026
Last checked20h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

  • https://api.ainote.dev/api/mcp streamable-http

Install package

  • NPM @ainote/mcp v1.3.2 · runs locally (stdio)

Required: Authorization, AINOTE_API_KEY (get them from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "ainote": {
      "url": "https://api.ainote.dev/api/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE ainote answered an MCP connection on 14 Nov 2026 and introduced itself as ainote-mcp-http 1.0.0 (MCP protocol 2025-06-18).

35 tools offered to AI assistants

  • delete_task · Soft-delete a task by ID. Destructive but reversible within 30 days (TaskCleanupJob purges trash daily at 2am KST). Returns 404 if the task does not exist or is not owned by the authenticated user.
  • list_papers · List notes/papers from AI Note. Supports keyword search across title and content, category filtering, pagination, and sorting. Returns id/title/content_preview/category_id/created_at. Use this when the user asks 'find my note about X', 'wha
  • project_read · List the authenticated user's projects (L2 intent layer), or fetch one by id. Each entry includes riskiest_assumption — the single highest-priority unverified assumption (or, if all are verified, the highest-criticality one).
  • project_write · Create or update a project (L2 intent layer). Omit `id` to create, pass it to update. There is no delete tool — use status: 'archived' to retire a project.
  • assumption_write · Create or update an assumption under a project (L2 intent layer). Omit `id` to create, pass it to update. There is no delete tool. 🔴 `verdict` is REJECTED with an error if passed — verdict is confirmed only through a human judgment decision
  • judgment_submit · Request a human judgment (L3 layer) by attaching evidence — approval, evidence, or verdict. This is the ONLY door an agent has into the judgment queue. 🔴 `decision` is REJECTED with an error if passed — judgments are always created with dec
  • judgment_list · List the authenticated user's own judgments (L3 layer) — use this to check your own blocking status (risk_tier 1 pending = execution blocked). Default order matches the /command queue: risk_tier ascending, then arrival order.
  • delete_dev_doc · Soft-delete a dev document by title or UUID. Reversible from trash. Pass `category` when multiple docs share the same title across subcategories (memory/claude/cursor/env/docs).
  • get_setup_guide · Get instructions for setting up AI Note MCP in Claude Desktop, Cursor, or other MCP clients. No authentication required.
  • vault_create · Create a new private vault as a GitHub repository under the user's account. Requires the user to have completed the GitHub App install flow first.
  • vault_sync · Wrapper around vault file sync. action=list|pull|push to work against the primary vault. list/pull are paginated — narrow with `path`/`since` and follow `next_cursor` instead of pulling the whole vault. To fetch specific files, pull with `p
  • sync_push · Push a markdown file into the primary vault. Optional CAS via base_sha to detect concurrent multi-PC writes (Layer 3 of multi-PC sync plan). WAF-bypass tip: large bodies (~10KB+) that get false-positive blocked at Cloudflare can be sent via
Show 23 more
  • sync_push_batch · Push MANY files into the primary vault in ONE call. Use this instead of looping sync_push whenever you have more than a couple of changed paths — the cost of sync_push is round trips, not bytes. Per-item semantics are identical to sync_push
  • sync_changes · Read changes from the primary vault in sequence order, including deletions. Start with since_seq=0 for a full listing; then pass next_seq and feed_epoch on each page. Default limit 500, max 1000. On reset_required, discard the cursor and re
  • sync_delete · Delete a file from the primary vault. Optional CAS via base_sha to detect concurrent multi-PC writes. Protected paths (global/memory/, global/skills/, global/planning/, global/intent/, global/claude-config/, handoffs/) require base_sha or e
  • sync_audit_layer5 · Record the result of a client-side Layer 5 codex review (sync.py merge gate) as a vault_events row. Body of the review is NOT stored — only an HMAC digest of the summary so operators can correlate without exposing review content. Opt-in: se
  • handoff_save · Save a session handoff note for cross-device / cross-session continuation. Stored at handoffs/{project}-{topic}-{YYYY-MM-DD}.txt in the user's primary vault. Use the optional `time` param (HHMM, KST) to disambiguate multiple handoffs saved
  • graph_soft_delete · Soft-delete an env_sync graph node (sets deleted_at; .live scope hides it from reads). Idempotent — re-deleting a deleted node is a no-op success.
  • env_sync.secret_push · Push a new client-encrypted secret. Ciphertext only — server never sees plaintext. Recipients must include the pushing device's own pubkey.
  • env_sync.secret_pull · Pull an encrypted secret blob. Response is ciphertext_b64 only — server never sees and never returns plaintext.
  • env_sync.secret_rotate · Rotate a secret: soft-delete the old node, create a new live node with the same alias and the new ciphertext+recipients. 7-day grace before hard delete of old ciphertext bytes.
  • env_sync_txn_push · Ingest a batched envelope of client-recorded env_sync mutations. HLC-skew gated, partial-success on conflict.
  • env_sync_txn_rollback · Inverse-apply a prior env_sync transaction. Safety gates: ownership, idempotency, descendant-conflict (force opt-out).
  • tasks_read · Read tasks and task categories. action: tasks | categories (consolidated surface — same handlers as the legacy tools)
  • task_write · Create or update a task. action: create | update. Deletion is a separate tool (delete_task). (consolidated surface — same handlers as the legacy tools) Required per action — create: content | update: id.
  • dev_docs_read · Read dev docs. action: get | list | categories | pull (consolidated surface — same handlers as the legacy tools)
  • dev_doc_write · Create or update a dev doc. action: create | update. Deletion is a separate tool (delete_dev_doc). (consolidated surface — same handlers as the legacy tools) Required per action — create: title, content | update: content.
  • sync_read · Read-only vault sync operations. action: list | pull | diff | merge | conflicts. Writes (push/delete) are separate tools — they carry CAS semantics. (consolidated surface — same handlers as the legacy tools) Required per action — diff: path
  • vault_read · Read vault metadata. action: list | clone | status (consolidated surface — same handlers as the legacy tools) Required per action — clone: name.
  • env_sync_read · Read env-sync state. action: devices | drift | status | txn_pull. Secret reads are a separate tool (env_sync.secret_pull). (consolidated surface — same handlers as the legacy tools)
  • env_sync_write · Non-destructive env-sync writes. action: enroll | request_share | heartbeat. Secret push/rotate are separate tools. (consolidated surface — same handlers as the legacy tools) Required per action — enroll: alias, age_pubkey, enrollment_token
  • graph_read · Read knowledge-graph nodes. action: get | list (consolidated surface — same handlers as the legacy tools)
  • graph_write · Add or update a graph entity. action: add | update. Deletion is a separate tool (graph_soft_delete). (consolidated surface — same handlers as the legacy tools) Required per action — add: node_type, alias, payload, device_id | update: node_i
  • handoff_read · Read session handoffs. action: get | list (consolidated surface — same handlers as the legacy tools) Required per action — get: project, topic.
  • memory_read · Read agent memory. action: get | search (consolidated surface — same handlers as the legacy tools) Required per action — get: source | search: query.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install package@ainote/mcpDECLAREDSRC-001 Official MCP Registry20h ago
Hosted endpointhttps://api.ainote.dev/api/mcpDECLAREDSRC-001 Official MCP Registry20h ago
Package registriesnpmDECLAREDSRC-001 Official MCP Registry20h ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry20h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry20h ago
Websitehttps://docs.ainote.devDECLAREDSRC-001 Official MCP Registry20h ago
Repositoryhttps://github.com/seunghan91/ainoteDECLAREDSRC-001 Official MCP Registry20h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry20h ago
Version1.3.2DECLAREDSRC-001 Official MCP Registry20h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry20h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run ainote? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor ainoteLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of ainote?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/ainote?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/ainote/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about ainote

How do I connect ainote?

Use the hosted endpoint https://api.ainote.dev/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does ainote need an API key or token?

Yes. The registry entry lists required values: Authorization, AINOTE_API_KEY. Get them from the publisher.

What tools does ainote offer?

When Electra Index connected on 14 Nov 2026, it listed 35 tools: delete_task, list_papers, project_read, project_write, assumption_write, judgment_submit, judgment_list, delete_dev_doc and more. The full list is in "Live check" above.

Is ainote online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use ainote for?

Based on its description, it is most relevant to: automate business workflows, build an internal tool, integrate two APIs, build data pipelines.