Atalaya

io.atalayahqPublished by atalayahq.ioOfficial publisherv1.1.0Updated Oct 29, 2026

Work management with Spec-Driven Development: tasks, sprints and SDD approvals for coding agents.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Atalaya is a remote MCP endpoint for work management with Spec-Driven Development: tasks, sprints and SDD approvals for coding agents.

What you can do
  • Manage work items such as tasks and sprints for coding agents.
  • Handle Spec-Driven Development approvals through the same workspace.
  • Connect an assistant to the Atalaya workspace over a remote HTTP endpoint.
  • No tool list is published, so the exact operations available are not documented in this entry.
When to use it
Worth adding when a team tracks coding-agent work in Atalaya and wants the assistant to work with tasks, sprints and SDD approvals directly instead of switching to the web app.
Requirements
A remote endpoint at app.atalayahq.io over streamable HTTP. A bearer token is required in the Authorization header; the token is created in Atalaya under Settings › API tokens and has the form Bearer tk_… .
Before you install
The Authorization bearer token is a secret that grants access to the Atalaya workspace; keep it out of logs and shared transcripts. The server can act on work items and approvals, so changes may affect team planning data. No tool list is published, so review what it can modify before connecting.

Installation

In SourceWeft

  1. Open Atalaya in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.atalayahq%2Fatalaya/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "atalaya": {
      "type": "http",
      "url": "https://app.atalayahq.io/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.1.0LatestOct 29, 2026
  2. v1.0.0Oct 15, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.