InnoDay

Get current user profile and organization info

Get project updates for the requirements workflow. Returns all updates, questions, and clarifications for the project scope.

Get a single release by version string or by ID, including its tickets. Provide exactly one of `version` or `release_id`. Looking up by version returns a synthetic release summary (with tickets but no persisted id) if no Release row exists yet but tickets already reference that version — this happens for versions that came from Jira/Linear before InnoDay registered them explicitly.

Get issues for a specific repository. Returns repository issues with their current status, assignees, and other metadata.

Get a standup-style summary of a project's active and recently-completed work. Groups the project's tickets into in_progress, in_review, todo, and recently_done (completed in the last 7 days), plus blocked-looking urgent items. Use this at the start of a scrum/standup to see what's moving without reading through the full ticket list.

Get a structured summary of all work grouped by platform and status. Use this at the start of a session to orient yourself on the team's current work across all connected boards and repositories. Returns counts and highlights so you can quickly understand where things stand.

List all boards registered with InnoDay. Returns board information including sync status and ticket counts.

List repositories for the current authenticated user's organization

List tickets for the current authenticated user's organization

List all organizations, optionally filtered to those the current user belongs to. Use this to find your organization_id if you don't have it yet.

List releases for an organization, optionally filtered by project and status. Returns each release with aggregate ticket_count and open_ticket_count, ordered by version descending. Use this to see release history or find the most recent release for a project.

List all Git repositories registered with InnoDay. Returns repository information including sync status, issue counts, and archive/deletion status.

List tickets for an organization. Returns tickets with their current status, assignees, and metadata. DRAFT tickets are excluded unless status="DRAFT" is explicitly requested.

Parse text into tickets using Claude AI and optionally create them on a board. This combines text parsing with ticket creation. Set auto_create=true to automatically create the parsed tickets, or false to just preview them. The board's credential is resolved server-side if auto_create needs one.

Parse unstructured text into structured tickets using Claude AI. Converts meeting notes, requirements, or conversations into actionable tickets with titles, descriptions, priorities, and other metadata.

Test that a board is reachable and credentials are valid before running a full sync. Calls POST /organizations/{org_id}/boards/{board_id}/probe which: 1. Validates the stored board registration exists 2. Makes a lightweight API call to the board provider to confirm auth works 3. Returns the top 5 tickets that are actively in progress (not done, todo, or backlog) so you can visually confirm the right board is connected Use this after setup_org_with_env or register_board to confirm the org is wired correctly before calling sync_all_boards.

Register an external board (Trello, Jira, Linear, Notion, GitHub) with InnoDay. The token is used only to validate access — it is NOT stored in the database. After registration, call sync_all_boards to pull tickets into InnoDay. Board URL formats: - Trello: https://trello.com/b/abc123/board-name - Jira: https://company.atlassian.net/jira/software/projects/KEY/boards - Linear: https://linear.app/workspace/team/TEAM-ID - Notion: https://www.notion.so/workspace/<database-id> - GitHub: https://github.com/org/repo

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 board_summaries table. This is the second half of the two-step summarize flow: no Anthropic call happens here either, it's a plain persistence call. Once saved, the summary is retrievable via list_board_summaries / summary-latest exactly like summaries written under the old flow.

Full org onboarding in one call: creates the org, creates a first project, optionally registers a board, and writes env/orgs/<slug>. This is the MCP equivalent of `innoday orgs env-setup`. Call it when setting up a new client org from scratch. After this, call sync_all_boards to pull tickets. Returns org_id, project_id, board_id (if created), and the env file path.

Create a new organization in InnoDay. The specified user (or INNODAY_USER_ID) becomes the org owner. Returns the created organization including its ID, which you'll need for subsequent setup_project and sync_all_boards calls. Requires INNODAY_USER_ID to be set (or pass user_id explicitly).

Create a new project inside an organization. Projects are the central organizing unit — boards and repositories attach to projects. After creating a project, register a board with register_board and trigger sync_all_boards to pull in tickets. Returns the project ID needed for scope and board operations.

Switch to a different organization context

Sync all registered boards for an organization, pulling latest tickets into InnoDay. Iterates every active board registration and triggers a sync. Tokens are read from environment variables (TRELLO_TOKEN, JIRA_TOKEN, LINEAR_API_KEY, etc.). Returns a per-board result summary. Call this after register_board or whenever you want fresh ticket data.

Synchronize a Jira or Trello board with InnoDay. Fetches latest tickets from the board and updates InnoDay's database. Requires BOARD_API_EMAIL and BOARD_API_TOKEN environment variables.

Sync a registered Linear team board with InnoDay. Fetches issues from Linear and upserts them into InnoDay's central ticket store. Uses incremental sync by default (only issues updated since last sync). Use full_sync=True to re-import everything.

Sync a repository using stored integration tokens

Update a project's scope, goals, description, or status. Use this to refine the project after initial setup — add goals, clarify what's out of scope, or mark a project active once tickets are synced. Only fields you provide are updated; omitted fields are left unchanged.

Update project status (e.g., approve scope by setting status to active). This is used for the approval workflow at the project level.

Attach or update a release summary narrative for a given version. Looks up the release by version string and patches the notes field. Use this after running a sync or writing release notes to record them against the release record. The release must already exist (created automatically during ticket sync or via github-ops).

Update a scope document with refined information. Used to iteratively refine the scope based on clarifications and feedback.

Update an existing ticket. Updates specified fields of a ticket and returns the updated ticket.