InnoDay MCP server

Read from the package source without running it. The installed server may list more.

• add_project_updatewrite action

  Add an update to the project requirements workflow.

• analyze_conversations

  Analyze conversations using Claude AI.

• analyze_temporal_patterns

  Analyze temporal patterns in messages.

• blastoff
• check_status

  Check InnoDay API connectivity and status without leaving the session.

• clear_board

  Logically delete all tickets synced from a board (sets deleted_at). The board stays registered and active. Reversible via re-sync -- tickets still present at source are revived on the next sync. Use dry_run=true to preview.

• create_board_ticketwrite action

  Create a ticket directly on a Trello, Jira, or Linear board.

• create_releasewrite action

  Create a new release record in InnoDay.

• create_scope_documentwrite action

  Create an initial scope document for a project.

• create_ticketwrite action

  Create a new ticket in InnoDay.

• create_tickets_from_textwrite action

  Break a block of text into individual tickets and create them in InnoDay.

• finalize_scope

  Finalize a scope document, marking it as ready for approval.

• get_all_work

  Get all work items (tickets + GitHub issues) across all boards and repositories.

• get_assignment_summary

  Get a project's open tickets grouped by assignee.

• get_board_lists

  Get available lists/columns for a board.

• get_board_summary_data

  Fetch the raw structured data (active tickets, recent completions, stats, and a suggested prompt) needed to write a board summary. This tool does NOT call Claude/Anthropic and does NOT write a summary itself.

• get_current_release_tickets

  Every ticket in the release this project is currently cutting.

• get_current_scope

  Get the current active scope document for a project.

• get_project_timeline

  📋 A project's curated event history, newest first — releases, board attachments, ticket syncs, repo changes, and the daily scrum summary.

• get_project_updates

  Get project updates for the requirements workflow.

• get_release

  Get a single release by version string or by ID, including its tickets.

• get_release_content
• get_repository_issues

  Get issues for a specific repository.

• get_scrum_summary

  🚀 Assemble what actually moved on a project — tickets, branches, PRs — over a window, for the whole team (`scope="scrum"`) or just you (`scope="me"`).

• get_work_summary

  Get a structured summary of all work grouped by platform and status.

• list_boards

  List all boards registered with InnoDay.

• list_organizations

  List all organizations, optionally filtered to those the current user belongs to.

• list_releases

  List releases for an organization, optionally filtered by project and status.

• list_repositories

  List all Git repositories registered with InnoDay.

• list_tickets

  List tickets for an organization, or for one project.

• parse_and_create_ticketswrite action

  Parse text into tickets using Claude AI and optionally create them on a board.

• parse_text_to_tickets

  Parse unstructured text into structured tickets using Claude AI.

• probe_board

  Test that a board is reachable and credentials are valid before running a full sync.

• register_board

  Register an external board (Trello, Jira, Linear, Notion, GitHub) with InnoDay.

• save_board_summary

  Persist a board summary that YOU (Claude Code) already wrote -- after calling get_board_summary_data and composing the summary text yourself -- to InnoDay's `summaries` table.

• save_project_summary
• setup_projectwrite action

  Create a new project inside an organization.

• setup_project_workspace

  Onboard OR refresh a project workspace by alias — the programmatic equivalent of the pixelfuel-claude `onboard-project` skill, now inside InnoDay (auth P4). Shares ONE algorithm with `innoday init`/`refresh`:

• sync_all_boards

  Sync all registered boards for an organization, pulling latest tickets into InnoDay.

• sync_board

  Synchronize a Jira or Trello board with InnoDay.

• sync_linear_board

  Sync a registered Linear team board with InnoDay.

• sync_repository

  Sync a project's repositories from GitHub by topic label.

• update_project_scopewrite action

  Update a project's scope, goals, description, or status.

• update_project_statuswrite action

  Update project status (e.g., approve scope by setting status to active).

• update_releasewrite action

  Attach or update a release summary narrative for a given version.

• update_scope_documentwrite action

  Update a scope document with refined information.

• update_ticketwrite action

  Update an existing ticket.

• Code scan181 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

65/100

higher than 20% of 1,119 Developer tools servers

Tools

47

the typical Developer tools server has 7

Tools that change things

28%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

1,883

more than 95% of 430 Developer tools servers with a package

InnoDay: common questions

Is InnoDay MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the InnoDay safety report

How do I install InnoDay?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does InnoDay need an API key?

No secret keys are declared. It reads 2 settings from the environment.

Is InnoDay maintained?

The latest release is v0.112.2-beta.

What can I use instead of InnoDay?

Servers from other publishers that do the same job: GitHub MCP server, Gk CLI MCP server and Atlassian Dc Jira MCP server.

How does InnoDay compare with other Developer tools MCP servers?

safety score 65/100 (higher than 20% of 1,119 Developer tools servers); tools 47 (the typical Developer tools server has 7); tools that change things 28% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.