Sponsored by Deepsite.site

Tag

#management

632 results found

Gantta MCP

Turn conversations into project plans. Gantta connects your AI assistant to a full project management backend — plan projects, manage tasks, chase actions, and generate reports, all through natural language. What you can do Create project plans — Describe your project in plain language and get a structured plan with milestones, dependencies, deadlines, and deliverables Break down tasks — Automatically decompose projects into prioritised actions with owners, due dates, and status tracking Assign owners — Allocate tasks to team members and track who is responsible for what across every project Chase actions automatically — Follow up on overdue or pending actions with automatic owner notifications so nothing slips through the cracks Capture meeting transcriptions — Log meeting notes, standups, or any conversation and extract structured action items automatically Generate reports and slide decks — Produce project status reports, progress summaries, and presentation-ready slide decks directly from your project data Track timelines — View project schedules, milestone progress, and dependency chains at a glance Who it's for Product managers, project leads, founders, and agency teams who run projects across multiple clients and want to manage everything from their AI assistant without switching tools. No account needed to start Try Gantta instantly — your AI assistant can create project plans right away. When you're ready to save your work, collaborate with your team, and unlock full reporting, claim your workspace at gantta.co. Why Gantta over traditional PM tools Traditional project management tools require manual data entry, constant tab-switching, and rigid workflows. Gantta lets you manage projects the way you actually think — by talking. Your AI assistant becomes your project manager, handling the structure while you focus on the work. Built for teams who plan through conversation, not spreadsheets.

Testdino MCP

TestDino MCP is a Model Context Protocol server that lets AI agents work directly with your Playwright test data, without leaving your editor or opening a browser. Once connected, your AI assistant can browse TestDino runs, inspect failing tests, and manage manual cases using plain language. Ask it to “show the last 5 failed runs in production,” “debug the checkout flow test,” or “list all critical manual test cases in project X,” and it will call the right tools behind the scenes. The server exposes 12 focused tools for CI runs, debugging, and manual test management. You can: Check account health and validate your PAT Filter runs by branch, commit, author, time window, or environment Drill into a single test case, including errors, logs, steps, screenshots, and traces Run debug_testcase to aggregate historical failures, classify patterns, and get AI‑ready prompts for root‑cause analysis and flakiness Create, update, and organize manual test cases and suites (status, severity, tags, layers, behaviors) TestDino MCP is MCP‑compatible and works with clients like Cursor and Claude Desktop. Configure it via mcp.json using either npx testdino-mcp (no install) or a global install (npm install -g testdino-mcp), and provide a TESTDINO_PAT from your TestDino account. Typical use cases include: speeding up Playwright failure triage from within your IDE, giving AI agents structured access to real test history, and keeping manual test management in sync with how your team actually debugs CI.

Mcp Server For Bitrix24

# mcp-bitrix24 MCP server for Bitrix24 Tasks, Workgroups, and Users. Implements MCP/JSON-RPC over STDIO. ## Features - Tasks: create, update, close, reopen, list - Workgroups: create, list - Users: list, current user, available fields - Task fields: available fields + validation for `create_task.fields` ## Requirements - Node.js >= 18 - Bitrix24 webhook URL ## Install / Build ```bash npm install npm run build ``` Run via npm: ```bash npx mcp-bitrix24 ``` ## Configuration Set the Bitrix24 webhook URL via environment variable: ``` BITRIX24_WEBHOOK_URL=https://<your-domain>/rest/<user_id>/<webhook>/ ``` Example Codex MCP config: ```toml [mcp_servers.bitrix24] command = "npx" args = ["-y", "mcp-bitrix24"] [mcp_servers.bitrix24.env] BITRIX24_WEBHOOK_URL = "https://<your-domain>/rest/<user_id>/<webhook>/" ``` ## Tools ### Tasks - `create_task` - Input: `title` (string, required), `description?` (string), `responsible_id?` (number), `group_id?` (number), `fields?` (object) - Output: `{ task_id: number }` - Note: if `fields` is provided, keys are validated against `get_task_fields`. - `update_task` - Input: `task_id` (number, required) + at least one of: `title?`, `description?`, `responsible_id?`, `group_id?` - Output: `{ task_id: number }` - `close_task` - Input: `task_id` (number, required) - Output: `{ task_id: number }` - `reopen_task` - Input: `task_id` (number, required) - Output: `{ task_id: number }` - `list_tasks` - Input: `responsible_id?` (number), `group_id?` (number), `start?` (number), `limit?` (number) - Output: `{ tasks: [{ id, title, status }] }` - `get_task_fields` - Input: `{}` - Output: `{ fields: { [field: string]: object } }` - `list_task_history` - Input: `task_id` (number, required), `filter?` (object), `order?` (object) - Output: `{ list: [ { id, createdDate, field, value, user } ] }` ### Workgroups - `create_group` - Input: `name` (string, required), `description?` (string) - Output: `{ group_id: number }` - `list_groups` - Input: `limit?` (number) - Output: `{ groups: [{ id, name }] }` ### Users - `list_users` - Input: - `filter?` (object) - `sort?` (string) - `order?` ("ASC" | "DESC") - `admin_mode?` (boolean) - `start?` (number) - `limit?` (number) - Output: `{ users: [{ id, name, last_name, email?, active }] }` - Note: `filter` supports Bitrix24 `user.get` filters (including prefixes like `>=`, `%`, `@`, etc.). `start` controls paging (Bitrix returns 50 records per page); `limit` is a local slice after the API response. - `get_user_fields` - Input: `{}` - Output: `{ fields: { [field: string]: string } }` - `get_current_user` - Input: `{}` - Output: `{ user: { id, name, last_name, email?, active } }` ## Architecture Clean architecture layers: - `mcp/` — protocol, transport, server - `adapters/` — MCP tools mapping to domain - `domain/` — entities, services, ports - `infrastructure/` — Bitrix24 REST client ## Development Notes - Input validation uses `zod`. - Transport: STDIO only. - Build: `tsc` (`npm run build`). ## Contributing See `CONTRIBUTING.md` for guidelines.