eGile

kz.egilePublished by egile.kzOfficial publisherv1.2.0Updated Oct 27, 2026

eGile kanban board for AI agents: a card per task, take teammates' tasks, move cards as you work.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

eGile is a remote kanban board for AI agents: one card per task, where an assistant can pick up teammates' tasks and move cards as work progresses.

What you can do
  • Manage kanban cards representing tasks, one card per task.
  • Take tasks that belong to teammates from the shared board.
  • Move cards between columns as work progresses.
  • No individual tools are documented in the listing, so exact operations are not specified.
When to use it
Useful when several agents or teammates share a task board and you want an assistant to claim work items and update their status while working, rather than tracking tasks in chat.
Requirements
A remote MCP endpoint at mcp.egile.kz over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. An eGile account and network access are implied.
Before you install
The server acts on a shared team board: taking tasks and moving cards changes state other people and agents see. Access is granted through OAuth, so review the scopes you approve. Tool-level behavior is not documented in the listing.

Installation

In SourceWeft

  1. Open eGile in the dashboard and add it to a workspace.
  2. Connect the required 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/kz.egile%2Fboard/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "egile": {
      "type": "http",
      "url": "https://mcp.egile.kz/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestOct 18, 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.