
Atono
io.atonoPublished by atono.iov1.1.1Updated Oct 24, 2026
Give your AI coding tools your team's product context: stories, bugs, epics, and glossary.
Overview
Connects AI coding tools to an Atono workspace so assistants can read and write stories, bugs, epics, subtasks, and product context.
- What you can do
- Exposes 41 tools for reading and writing Atono work items: stories, bugs, epics, subtasks, acceptance criteria, attachments, timeboxes, and linked items. It also surfaces workspace setup data such as users, teams, workflows, and the glossary of product concepts, plus per-item AI context. Assistants can create and update items, assign them, move them through workflow steps, and document bug fixes.
- When to use it
- Use it when an assistant needs your team's product context while coding or reviewing, so it works against real stories, bugs, and epics instead of guessing. It suits teams already using Atono who want agents to read and update work items directly.
- Requirements
- Docker Desktop v27.0 or later running locally, an MCP-enabled client, and an Atono API key supplied as the X_API_KEY environment variable. The server runs as a local Docker container over stdio. An Atono workspace is required; the key reaches only that workspace.
Installation
In SourceWeft
- Open Atono in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Atono MCP Server
Give your AI coding tools your team's product context.
Your AI tools are fast, confident, and guessing at how your product actually works. They can only act on the context they can reach — so they produce work that looks right, passes review, ships, and fails weeks later.
The Atono MCP server connects Claude Code, Claude Desktop, Cursor, VS Code, Copilot, Windsurf, and Codex directly to an Atono workspace. 41 tools for reading and writing stories, bugs, epics, subtasks, acceptance criteria, and timeboxes — plus the two things that actually change output quality: your workspace glossary of product concepts, and per-item AI context (design decisions, investigations, summaries).
Agents stop relearning your domain on every session.
Quick start
Prerequisites
- Docker Desktop v27.0 or later, running in the background
- An Atono API key — workspace settings → Manage API keys
- An MCP-enabled tool
Claude Code
Run /mcp to confirm Atono appears.
Claude Desktop
claude_desktop_config.json:
Cursor
One-step install via the Cursor MCP directory,
or add to mcp.json:
VS Code (GitHub Copilot)
Copilot Chat → Configure Tools → Add MCP Server → Docker Image → atonoai/atono-mcp-server:latest,
then use the same JSON in .vscode/mcp.json and restart the server.
Windsurf
Same JSON as Cursor, in mcp_config.json. Restart Windsurf.
OpenAI Codex
~/.codex/config.toml:
Verify: ask your assistant "What Atono MCP tools are available?"
Updates: none required. --pull=always fetches the latest image on restart.
The 41 tools
Setup & context (5) atono_configuration · atono_list_users · atono_list_teams · atono_get_team_workflow · atono_get_glossary
Stories (10) atono_get_story · atono_list_story_personas · atono_create_story · atono_update_story_title · atono_update_story_content · atono_update_story_ac · atono_update_story_additional_content · atono_update_story_team · atono_update_story_step · atono_update_story_assignee
Bugs (7) atono_list_environments · atono_get_bug · atono_create_bug · atono_update_bug · atono_update_bug_step · atono_update_bug_assignee · atono_document_bug_fix
Epics (7) atono_create_epic · atono_get_epic · atono_update_epic_title · atono_update_epic_description · atono_update_epic_user_stories · atono_add_story_to_epic · atono_remove_story_from_epic
Subtasks (4) atono_get_subtasks · atono_create_subtask · atono_update_subtask · atono_delete_subtask
Attachments (3) atono_upload_file_url · atono_create_attachment · atono_get_attachment
Timeboxes (2) atono_list_timeboxes · atono_list_timebox_items
Linked items (1) atono_link_bugs_or_stories
AI context (2) atono_get_ai_context · atono_update_ai_context
Full reference: docs.atono.io/docs/atono-mcp-tools
Agent cautions
- Always call
atono_get_ai_contextbeforeatono_update_ai_context. - Some writes replace rather than append.
atono_update_story_acandatono_update_epic_user_storiesreplace all criteria/statements. Same foratono_update_epic_descriptionandatono_update_story_additional_content. Read first. - The server reaches only the workspace the API key authenticates to. It exposes defined Atono actions and nothing else.
- Treat API keys as passwords. Never commit them.
- Agent actions are attributed and auditable — MCP-performed changes show "Performed by MCP server" in Activities, and the human driver stays the attributed author.
Plans
The MCP server works on every Atono plan, including Free (up to 25 users).
One thing worth knowing up front: Glossary and AI Context are a 30-day trial on the Free plan. Connect an agent to a Free workspace past its trial and you'll find the tools present but the context they fetch empty. That's a licensing state, not a bug — it's the most common surprise, so we'd rather say it here.
About Atono
Atono is the product engineering platform that keeps product context connected to the work, so your team and its AI agents build what you actually intend — not just what looks right.
A story in Atono carries its acceptance criteria, the feature flag controlling its rollout, the usage data proving whether it worked, and the AI context agents read — in one object. In a conventional stack those four live in four products, and the context is destroyed at every seam.
Source: Readme.md at commit a9fee13
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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