Install Jentic One Beta

Connect the MeisterTask API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MeisterTask API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmeistertask.com%2Fmeistertask" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmeistertask.com%2Fmeistertask" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MeisterTask API.

Create projects and configure sections that map to Kanban columns

Create or update tasks with assignees, due dates, and section placement

Move tasks between sections to reflect status changes

Add checklists and checklist items to a task for granular subtask tracking

Attach files and post comments on a task to keep context with the work

GET STARTED

Start building with MeisterTask API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MeisterTask API for, with concrete tasks.

★ Bidirectional Sync With Source-Control Issues

Mirror GitHub or Jira issues into MeisterTask so non-technical stakeholders can see engineering status on a Kanban board without entering a developer tool. The /tasks and /sections endpoints let an integration create a task per issue, move it as the upstream status changes, and post comments reflecting upstream activity. Engineering managers use this to keep cross-functional visibility without daily standup overhead.

When a GitHub issue is opened, call POST /projects/{projectId}/tasks to create a matching task in the Backlog section, copying title and description.

Automated Task Intake From Forms or Email

Funnel incoming requests from a form or shared inbox into MeisterTask as tasks with the right project, section, and labels. POST /projects/{projectId}/tasks accepts assignee, due date, and labels in a single payload, and /tasks/{taskId}/comments adds the original message as context. Operations teams use this to remove the manual triage step that drains support time.

Given a parsed support email, create a task in project=ops-intake section=Inbox with title, description, and labels=email,priority-medium.

Time Tracking and Reporting

Log work intervals against tasks so finance and team leads can roll up hours per project or client. /tasks/{taskId}/work_intervals records start and end times, and /work_intervals/{intervalId} supports updates if a timer needs adjustment. Combined with custom fields this becomes a per-client billable-hours feed without leaving MeisterTask.

Create a work interval on task id 5567 with start=2026-06-11T09:00 end=2026-06-11T11:30 and a description tag client=Acme.

Agent-Driven Standup Updates

Hand a team agent the ability to compile a daily standup digest from MeisterTask: tasks moved into Done yesterday, tasks still in Doing, and any new comments on blocked tasks. Through Jentic the agent searches by intent, loads the relevant task and comment schemas, and assembles the digest without any custom integration code. This collapses standup prep into a one-click operation per morning.

List tasks in project=team-app whose section changed to Done yesterday plus tasks still in Doing, fetch their latest comments, and post a Slack digest.

Key Endpoints

59 endpoints — jentic publishes the only available openapi specification for meistertask api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/projects

List projects accessible to the user

POST

/projects/{projectId}/tasks

Create a task in a project

PUT

/tasks/{taskId}

Update a task including its section

POST

/tasks/{taskId}/comments

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring MeisterTask by hand means running its OAuth 2.0 flow, refreshing bearer tokens, and hand-coding each project, task, comment, and checklist call against www.meistertask.com/api. Through Jentic you install once, import the MeisterTask API from the API Directory, store the token once, and your agent calls it.

Permission scoping

MeisterTask puts the project and task ids in the URL path (/projects/{projectId}/tasks, /tasks/{taskId}), so a rule can pin your agent to one project: it can create tasks and add comments there and nothing else. You choose the operations it may call, so updating or moving tasks is included only if you add it.

Credential isolation

Your MeisterTask OAuth 2.0 token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a MeisterTask task in a section' or 'add a comment to a task', and Jentic returns the matching operation with the schema for project, section, assignee, and label fields so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MeisterTask API through Jentic.

Why is there no official OpenAPI spec for MeisterTask API?

MeisterTask publishes a developer reference but not a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MeisterTask API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the MeisterTask API use?

MeisterTask uses OAuth 2.0 bearer tokens issued via the MindMeister OAuth flow with scopes userinfo.profile, userinfo.email, and meistertask. Through Jentic the bearer token is stored encrypted in the vault and refreshed as needed, so the agent does not handle the OAuth handshake.

Can I create tasks in a specific section through the API?

Yes. POST /projects/{projectId}/tasks accepts a section_id field, and you can also POST to /sections/{sectionId}/tasks to scope creation to a known section. The response includes the task id which you can use to attach checklists or labels.

What are the rate limits for the MeisterTask API?

MeisterTask does not publish hard rate limits in this spec; in practice burst calls against /tasks should be paced and bulk reads should batch with pagination. If you receive a 429, back off exponentially before retrying through Jentic.

How do I move a task between sections through Jentic?

Search Jentic for move a MeisterTask task to a section, load the schema for PUT /tasks/{taskId}, and execute with the new section_id. Jentic returns the updated task object so the agent can confirm the move.

Can I track time against tasks?

Yes. POST /tasks/{taskId}/work_intervals to start a time entry and PUT /work_intervals/{intervalId} to close or amend it. These records back per-task and per-project hour reports.

Can I limit what my agent is allowed to do with the MeisterTask API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which MeisterTask operations and credentials your agent may use. Since MeisterTask puts the project and task ids in the URL path (/projects/{projectId}/tasks, /tasks/{taskId}), a rule can pin the agent to a single project so it can, for example, create tasks and post comments there and nothing else. You choose the operations it may call, so updating or moving tasks with PUT /tasks/{taskId} is available only if you add it.

MeisterTask API

Name: MeisterTask API
Brand: MeisterTask API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer59 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage MeisterTask projects, sections, tasks, checklists, labels, comments, and time intervals so an agent can drive a Kanban workflow from any external trigger.

Use for: Create a new task in a MeisterTask project section, Move a task into the Done section of my project, Add a checklist with three items to a task, Post a comment with status notes on a task

Not supported: Does not handle long-form documentation, video conferencing, or accounting - use for MeisterTask projects, sections, tasks, checklists, comments, attachments, labels, work intervals, and memberships only.

Jentic publishes the only available OpenAPI specification for MeisterTask API, keeping it validated and agent-ready. MeisterTask is a Kanban-style task management platform with projects, sections, tasks, checklists, comments, attachments, labels, custom fields, and time tracking via work intervals. The API exposes 59 endpoints covering the full project hierarchy as well as memberships and task relationships. Use it to mirror MeisterTask boards into another tool, automate task creation from external triggers, or run portfolio-level reporting across projects.

Jentic One on Github View OpenAPI Document