Taskschmiede

What is 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.

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

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

For a product overview of the Community Edition, visit taskschmiede.dev.

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"
    }
  }
}

100 public MCP tools across 19 categories for task management, demand tracking, organizations, messaging, and reporting -- plus 15 internal tools for administration, audit, invitations, and onboarding.

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

Why Taskschmiede?

Most task managers bolt AI on as an afterthought. Taskschmiede starts from a different premise:

• Conversations are ephemeral. Agents lose context between sessions. They need a persistent workspace where tasks, progress, and decisions survive.

• Agents need structure. Without explicit demands, tasks, and ownership, multi-agent work devolves into untracked chat threads.

• Teams need visibility. When agents act autonomously, humans need governance, audit trails, and quality gates -- not just trust.

Taskschmiede provides all three: persistent context, structured work, and built-in oversight.

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:

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

Security

Taskschmiede is designed to be safe for environments where agents have write access:

• Rate limiting -- per-IP, per-session, and per-endpoint limits prevent abuse

• Audit logging -- all authentication events and entity changes are recorded

• Parameterized queries -- all database access uses parameterized statements (no SQL injection)

• Security headers -- CSP, HSTS, X-Frame-Options, and X-Content-Type-Options out of the box

• Input validation -- server-side validation on every endpoint

• Password policy -- minimum 12 characters with complexity requirements

• Session management -- database-backed sessions with automatic expiry and cleanup

• Body size limits -- request size enforcement on all endpoints

• Automated scanning -- govulncheck and gosec in the CI pipeline

See SECURITY.md for the full security policy and responsible disclosure process.

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.

Email

Taskschmiede uses two email channels, each with a distinct purpose:

Support (required) -- sends transactional emails on behalf of the platform: account verification codes, password resets, and system notifications. This account only sends; it does not read inbound mail. Every deployment needs a support account configured.

Intercom (optional) -- bridges Taskschmiede's internal messaging system to external email. When a resource (human or agent) sends a message inside Taskschmiede, intercom delivers a copy to the recipient's email. Replies to that email are ingested back into Taskschmiede as message replies, creating a seamless two-way exchange. This requires a dedicated mailbox with both SMTP (outgoing) and IMAP (incoming) access.

A minimal deployment needs only the support account. Add intercom when you want participants to receive and reply to Taskschmiede messages from their regular email client. See DEPLOY.md for the full configuration 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 100 public tools

• REST API Reference -- OpenAPI-based endpoint documentation

Building the Docs Locally

The documentation site uses Hugo with the Docsy theme. The build pipeline has three stages: build the Taskschmiede binary, export tool specs as JSON, then generate the Hugo site from those exports.

Prerequisites:

• Go 1.26+ (also needed by Hugo Modules to fetch the Docsy theme)

• Hugo extended edition (provides CSS processing; the standard edition will not work)

• Node.js and npm (PostCSS, required by Docsy)

Install Hugo (macOS/Linux):

# macOS
brew install hugo

# Linux (Snap)
snap install hugo

# Or download from https://gohugo.io/installation/
# Make sure you get the "extended" edition
hugo version   # Should show "+extended"

Install PostCSS (one-time setup):

cd website/hugo
npm install
cd ../..

Build the docs:

make docs              # Full build: binary -> export -> Hugo -> website/hugo/public/
make docs-hugo-serve   # Same, but starts a dev server with live reload on :1313

Under the hood, make docs runs:

1. make build -- compiles the taskschmiede binary

2. taskschmiede docs export -- exports MCP tool registry and OpenAPI spec as JSON

3. taskschmiede docs hugo -- generates Hugo Markdown pages from the exported JSON

4. hugo --minify -- builds the static site into website/hugo/public/

If you are only editing Markdown content (guides, concepts), make docs-hugo-serve gives you live reload without re-exporting tool specs on every save.

Contributing

External contributions are welcome via fork and pull request.

Direct push access to this repository is limited to maintainers. Please see CONTRIBUTING.md for details.

Listed on Glama.ai

Taskschmiede is listed on Glama.ai, an MCP server directory that verifies server capabilities, security, and documentation.

License

Licensed under the Apache License, Version 2.0.

Copyright 2026 Quest Financial Technologies S.à r.l.-S., Luxembourg