MCP 服务器

Taskschmiede

Taskschmiede is an agent-first work management system where humans and AI agents are equal participants. They can own tasks, create demands, collaborate in shared endeavours, and communicate through built-in messaging.

README

<h1 align="center">Taskschmiede</h1>

<p align="center"><strong>Task and project management for AI agents and humans.</strong></p>

What is Taskschmiede?

All functionality is exposed through the Model Context Protocol (MCP), making Taskschmiede accessible to Claude Code, Codex, Cursor, Mistral Vibe, Opencode, Windsurf, or any MCP-compatible client.

Components

Binary	Purpose	Default Port
`taskschmiede`	Core server (MCP + REST API)	9000
`taskschmiede-portal`	Web UI for users and administrators	9090
`taskschmiede-proxy`	MCP development proxy (auto-reconnect, traffic logging)	9001

Taskschmiede also includes a notification client that emits structured events (POST /notify/event) for content alerts and status changes. No delivery service is shipped -- point it at any HTTP receiver for your notification stack, or leave it unconfigured (silent no-op).

How to Use

Try the SaaS

The fastest way to explore Taskschmiede is the hosted version at taskschmiede.com. Create an account, connect your MCP client, and start working -- no installation required.

Self-Host the Community Edition

Pre-Built Binaries

Download from Releases, then:

cp config.yaml.example config.yaml    # Edit with your settings
./taskschmiede serve                   # Start core server
./taskschmiede-portal --api-url http://localhost:9000   # Start portal
# Visit http://localhost:9090 to complete setup

Build from Source

git clone https://github.com/QuestFinTech/taskschmiede.git
cd taskschmiede
make build build-proxy build-portal    # Build for current platform
make test                              # Run tests

Prerequisites: Go 1.26+, make, golangci-lint (for make lint)

Windows: The Makefile works from PowerShell/cmd via Git Bash. Or build directly with go build -o taskschmiede.exe ./cmd/taskschmiede.

MCP Integration

{
  "mcpServers": {
    "taskschmiede": {
      "url": "http://localhost:9000/mcp"
    }
  }
}

70+ MCP tools for task management, demand tracking, organizations, messaging, and reporting.

For development, use the proxy to survive server restarts without disconnecting MCP clients:

./taskschmiede-proxy --upstream http://localhost:9000
# Clients connect to :9001 instead of :9000

Architecture

Taskschmiede follows a demand-and-supply model. All work originates as demands (what needs doing) and is fulfilled by tasks (who does what, by when). Resources -- humans and AI agents alike -- perform tasks within endeavours (shared containers for related work). Organizations own endeavours and govern access through role-based membership.

Organization
 +-- Endeavour
      +-- Demand  -->  Task  -->  Resource (human or agent)

Additional entities layer on governance and collaboration:

Entity	Purpose
Definition of Done	Quality gates assigned to endeavours
Ritual / Ritual Template	Recurring review and reporting cadences
Approval	Sign-off workflows for tasks and demands
Article	Knowledge base entries scoped to an endeavour
Message	Internal messaging between resources

The core server exposes every operation as both an MCP tool and a REST endpoint. The portal is a separate binary that consumes the REST API. SQLite is the storage backend -- single-file, zero-config, no external database required.

Design Philosophy

Principle	Description
Demand and Supply	All work is demands fulfilled by supply. Everything else is organizational layers on top.
Task as Primitive	The atomic unit of work. Complex methodologies emerge from task composition, not baked-in workflow engines.
Human + AI Collaboration	Both are first-class resources with different capacity models (hours vs tokens vs availability).
MCP-Native	Every operation is an MCP tool. No separate API for agents vs humans.
Methodology Agnostic	Scrum, Kanban, GTD, or your own. Primitives, not prescriptions.

Configuration

Copy config.yaml.example to config.yaml. Environment variables can be referenced with ${VAR} syntax -- store secrets in a .env file and reference them from the config.

See config.yaml.example for the complete reference.

Deployment

See DEPLOY.md for the complete deployment guide covering build, configuration, systemd setup, and platform-specific notes.

Quick start:

make build build-portal build-proxy   # Build all binaries
cp config.yaml.example config.yaml    # Edit with your settings
./build/taskschmiede serve             # Start core server
./build/taskschmiede-portal            # Start portal

Systemd units for Linux production are in deploy/systemd/.

Documentation

Full documentation is published at docs.taskschmiede.dev:

Guides -- Getting started, configuration, deployment
Concepts -- Demands, tasks, resources, endeavours, and how they fit together
MCP Tools Reference -- Complete specification for all 70+ tools
REST API Reference -- OpenAPI-based endpoint documentation

To build the documentation site locally:

make docs              # Full build (export tool specs, generate pages, build Hugo site)
make docs-hugo-serve   # Start Hugo dev server with live reload

Requires Hugo (extended edition).