InnoDay

io.github.havilandsoftwarePublished by GitHub account havilandsoftwarev0.112.2-betaUpdated Oct 24, 2026

Unified ticketing MCP server for Jira, Linear, Trello, Notion, and GitHub Issues.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Local MCP server that connects an assistant to a self-hosted InnoDay API for unified ticketing across Jira, Linear, Trello, Notion and GitHub Issues.

What you can do
  • Work with tickets across Jira, Linear, Trello, Notion and GitHub Issues through one InnoDay API instance.
  • The manifest lists no individual tools, so the exact operations are not documented here; expect ticket-oriented actions against the configured InnoDay backend.
  • Optionally target a default organization, or pass an organization per call.
When to use it
Useful when you already run an InnoDay API instance and want an assistant to work with tickets from several trackers through one interface instead of separate integrations.
Requirements
Runs as a local process installed from the innoday PyPI package over stdio, so a Python environment is needed. Requires a reachable InnoDay API instance; INNODAY_API_URL defaults to and only needs setting for another port or a remote host. INNODAY_ORGANIZATION_ID is optional and can be supplied per tool call instead.
Before you install
The server talks to your own InnoDay API, which in turn reaches third-party trackers, so ticket data passes through that backend. No authentication is declared, so anyone who can reach the API URL may be able to use it. Ticket operations may create or change items in connected trackers; the manifest does not list the tools, so confirm what it can write before use.

Installation

In SourceWeft

  1. Open InnoDay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.112.2-betaLatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.