"Information on Becoming a Project Manager" matching MCP tools:

• create_project

  EchoRelay

  Create a new project on your account so an agent can bootstrap from a fresh account. The slug is derived from the name and validated server-side (format, reserved words, uniqueness). Each plan includes a fixed number of active projects (free tiers one; paid plans more — see list_subscription_plans); at the limit this returns an error telling you to archive a project or upgrade. Requires an ACCOUNT-scoped token and the `config` scope. Returns the created project ({id, slug, name, apiBaseUrl, archived}); mint a project-scoped token in the panel to then configure it.

  Connector

• list_projects

  EchoRelay

  List the projects on your account (archived included), each with `id`, `slug`, `name`, `apiBaseUrl` and `archived`. Requires an ACCOUNT-scoped token (one minted with no project) and the `read` scope. A project-scoped token cannot call this — use it on its own project's tools instead.

  Connector

• set_attention_budget

  freedom-mcp

  Set the founder's attention budget — the maximum pending review cards before they are 'overloaded' (a whole number 1–100; default 7) — for a manager or the founder. Use when the founder (or a manager on their behalf) wants to raise or lower their overload threshold (e.g. "set my overload threshold to 10", "I can handle more pending cards before you flag me", "lower my attention budget to 5"). This is the founder's OWN constraint, so it is gated: an autonomous agent CANNOT change it (surface a recommendation instead); only a human-present company manager can. Always call get_attention_budget first and explain why a change helps the founder. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]

  Connector

• save_comment

  linear

  Create or update a comment on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. If `id` is provided, updates the existing comment; otherwise creates a new one. To start a new thread, pass `body` and exactly one of `issueId`, `projectId`, `initiativeId`, `documentId`, `milestoneId`, or `statusUpdateId` — comments on issues/projects/initiatives become top-level discussion threads; comments on documents/milestones become description comments. A status update holds a single thread, so a comment on an update that already has one is added to it as a reply. To reply to an existing thread, pass `parentId` and `body`; the reply inherits the parent's thread type, so no entity reference is needed. Parent reference fields are ignored when `id` or `parentId` is provided (`statusUpdateType` is rejected instead).

  Connector

• acc_create_issue

  ACC MCP

  Create a new ACC issue (field observation, coordination clash, safety, quality, etc.) in the target project via the APS Construction Issues API. When to use: The user wants to log a new issue — e.g. 'open a high-priority issue about the leaking valve on level 3' or a downstream agent detected a defect during a model review and needs to record it for the project team. When NOT to use: Do not use to modify an existing issue (use acc_update_issue) and do not use for RFIs (use acc_create_rfi). APS scopes: data:read data:write account:read. Rate limits: ACC Issues API limited to ~100 req/min per app; APS default ~50 req/min per endpoint — batch creations with backoff. Errors: 401 (APS token expired — refresh); 403 (user lacks 'Create Issues' permission on the project or scope insufficient — surface to user); 404 (project_id not found — verify the 'b.' prefix and that the project belongs to a hub the app can see via acc_list_projects); 422 (validation — required field like title/description missing or priority enum invalid); 429 (rate limit — retry after 60s); 5xx (ACC upstream — retry with jitter, do not double-create). Side effects: Creates a persistent issue record visible to all project members. NOT idempotent — a retry on a 5xx may create duplicates; dedupe by title before retrying.

  Connector

• twprojects-create_custom_item_record

  mcp

  Create a record (row) on a custom item type. For example, add a Contract on the Contracts type. Pass field values by name; the tool resolves names to the API's internal IDs. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

  Connector

• get_pm_playbook

  AIOProductOS MCP

  How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.

  Connector

• create_project

  Epovest

  Create a project to file trackers under: one project per BRAND, never per language. It can carry the brand canon: the reference wording every publication reuses as is, written in ONE language, its canonical language (carried at creation, it is recorded as canon version 1). The canon is never translated: localized expressions on the pages are outputs, not a second canon. Nothing is filed by this call: pass the returned id as project_id when creating or updating a tracker. Refused with project_exists when a project with this name already exists, and the answer carries the existing project: reuse its id instead of duplicating.

  Connector

• get_about

  Follow On Tours

  Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.

  Connector

• twprojects-get_custom_item

  mcp

  Get a custom item type with its fields and sections inline, so you can see its schema before creating or updating records. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

  Connector

• weekly_project_update_ppt

  L&T MCP

  SKILL: weekly_project_update_ppt Team: Project Management Weekly Project Update PPT — L&T Format Call this tool to get the complete guide for 'weekly_project_update_ppt'. Read the 'content' field and follow its instructions. This tool takes NO parameters. Full content: --- name: weekly_project_update_ppt description: > Use this skill to create a weekly project update PowerPoint presentation in L&T branded format. Use when user asks for weekly update, weekly report, project status PPT or weekly project summary presentation. --- # Weekly Project Update PPT — L&T Format ## When To Use - "Create weekly update for project X" - "Make weekly PPT for project LE20M143" - "Generate project status presentation for this week" - "Weekly report PPT" --- ## Step 1 — Collect Information From User Ask the user for all of these in ONE message before doing anything. NEVER assume or fill in values yourself. Ask exactly this: ``` To create your weekly project update PPT I need the following: 1. 📋 Project Name (e.g. Mumbai Metro Line 7) 2. 📌 Project Code (e.g. LE20M143) 3. 📅 Week Number (e.g. Week 24) 4. 📅 Date Range (e.g. 09-Jun-2025 to 15-Jun-2025) 5. ✅ Accomplishments This Week (list what was completed) 6. 📌 Planned Next Week (list what is planned) 7. ⚠️ Risks & Issues (list risks, mention HIGH / MEDIUM / LOW if known) 8. 👤 Prepared By (your name) ``` Wait for the user to reply with all details. Do NOT move to Step 2 until user has provided the information. --- ## Step 2 — Generate The PPT Use the execute_code tool to generate a 5 slide PowerPoint file. Use python-pptx library. Download the L&T logo from this URL and place it on every slide: https://upload.wikimedia.org/wikipedia/commons/thumb/c/cd/L%26T.png/320px-L%26T.png If the logo cannot be downloaded, write the text "L&T" in orange as a substitute in the same position. --- ## Slide Specifications ### SLIDE 1 — Title Slide Background: Full navy blue (#002B5C) covering the entire slide Top of slide: - Thin orange (#F47B20) horizontal bar across the full width at the very top - L&T logo placed top right corner - Text "L&T Construction" in small orange text top left Center of slide: - Large white bold text: "Weekly Project Update" - Below that in orange bold text: the Project Name - Small navy chip/box containing the Project Code in orange text - Below that in white normal text: Week Number and Date Range - Below that in grey text: "Prepared by: [name]" Bottom of slide: - Thin orange horizontal bar across the full width at the very bottom - Small grey italic text: "Generated by L&T Enterprise MCP Agent" with today's date and time --- ### SLIDE 2 — Accomplishments This Week Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Full width navy blue bar, height about 1 inch - White bold text on the left: "✅ Accomplishments This Week" - Below the title in small orange text: Week Number and Date Range - L&T logo on the right side of the header bar - Thin orange line immediately below the navy header bar Content area: - White rounded rectangle card covering most of the slide - Thin orange vertical stripe on the left edge of the card - Each accomplishment as a bullet point using a right arrow symbol - Font size 16, dark grey color - Adequate spacing between bullets so it is easy to read Footer bar at bottom: - Full width navy blue bar - White small text on left: "L&T Construction | Confidential | For Internal Use Only" - Orange small text on right: "Prepared by: [name]" --- ### SLIDE 3 — Plan for Next Week Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Same style as Slide 2 - Title text: "📌 Plan for Next Week" - L&T logo on the right side of the header bar Content area: - White rounded rectangle card covering most of the slide - Thin navy blue vertical stripe on the left edge of the card (navy stripe instead of orange to visually distinguish from Slide 2) - Each planned item as a bullet point using a right arrow symbol - Font size 16, dark grey color - Adequate spacing between bullets Footer bar: - Same style as Slide 2 --- ### SLIDE 4 — Risks & Issues Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Same style as Slide 2 - Title text: "⚠️ Risks & Issues" - L&T logo on the right side of the header bar Content area — Table: - Table with two columns: "Risk / Issue" and "Severity" - Table header row: navy blue background with white bold text - Data rows alternate between white and light grey background - "Risk / Issue" column takes about 75% of the width - "Severity" column takes about 25% of the width - Each severity value shown as a colored pill/badge: HIGH → red (#DC3545) pill with white text MEDIUM → amber/orange (#FFA500) pill with white text LOW → green (#28A745) pill with white text - If user did not specify severity, default to MEDIUM - Show maximum 6 risks in the table - Below the table show a small legend: 🔴 HIGH — Immediate action required 🟡 MEDIUM — Monitor closely 🟢 LOW — Awareness only Footer bar: - Same style as Slide 2 --- ### SLIDE 5 — Closing Slide Background: Full navy blue (#002B5C) covering the entire slide Same orange bars at top and bottom as Slide 1 Center of slide: - L&T logo centered in the upper half - Large white bold text below logo: "Thank You" - Orange text below: Project Name and Project Code - White text below: Week Number and Date Range Bottom area: - Small grey italic text centered: "L&T Construction — Enterprise Information Platform" --- ## Overall Design Rules Colors: - Primary background (dark slides): Navy blue #002B5C - Primary background (content slides): Light grey #F4F4F4 - Cards and content boxes: White #FFFFFF - Accent color: Orange #F47B20 - Body text: Dark grey #444444 - Footer text: White on navy backgrounds - Headings on dark backgrounds: White - Headings on light backgrounds: Navy blue Typography: - Main title on title slide: 38pt bold white - Slide titles in header bar: 22pt bold white - Project name on title slide: 26pt bold orange - Bullet points: 16pt dark grey - Footer text: 8pt - Week/date labels: 9-10pt orange Logo placement: - Title slide: top right, width about 1.9 inches - Content slides: right side of the navy header bar, width about 1.3 inches - Closing slide: centered, width about 2.1 inches Slide size: 13.33 inches wide by 7.5 inches tall (widescreen 16:9) Every content slide must have: - Navy header bar at top with title and logo - Thin orange line below the header bar - Navy footer bar at bottom with confidentiality note and prepared by --- ## Step 3 — Save and Return Save the file with this name format: Weekly_Update_{ProjectCode}_{WeekNumber without spaces}.pptx Example: Weekly_Update_LE20M143_Week24.pptx After the file is generated show this to the user: ``` ✅ Your Weekly Project Update PPT is ready! 📎 Download: {download_url} 📋 Project: {Project Name} ({Project Code}) 📅 Period: {Week Number} | {Date Range} 📊 Slides: 5 slides generated 1. Title 2. Accomplishments This Week 3. Plan for Next Week 4. Risks & Issues 5. Closing File expires in 24 hours — please download promptly. ``` --- ## Important Rules - NEVER generate the PPT without collecting user input first - NEVER make up project name, code, dates or any content - ALWAYS download the L&T logo from the URL given above - ALWAYS use navy and orange as the primary colors - ALWAYS include the logo on every slide - ALWAYS include the footer on every content slide - ALWAYS call execute_code tool — never just describe the slides - ALWAYS show the download link to the user after generation - If execute_code returns an error, fix the code and retry up to 3 times

  Connector

• subscribe_addon

  EchoRelay

  Subscribe the project owner to a monthly add-on (RPM upgrade, team seat, extended log retention, extra file storage in +5 GB blocks, …). Charges the saved payment method immediately, then auto-renews every 30 days until `unsubscribe_addon` — or until the subscription ends, after which the already-paid cycle stays active to its own end date and stops without further charges. Requires an active Pro/Scale subscription and a saved PM. RPM upgrades (rpm_*) are per-project and apply to THIS project automatically. Returns `{addonKey, project, monthlyEurCents, transactionId, activatedAt, nextRenewalAt}`. Owner-only; requires a token minted with the billing scope.

  Connector

• load_project

  clipkit

  Import a previously shared project as the current project, by its share id or its editor URL (e.g. https://clipkit.dev/editor?id=…), returning its project_id. Use this to continue working on a project the user opened in the editor or shared earlier — the round-trip for open_in_editor. Pass an existing project_id to load into that project; omit it to load into a new one.

  Connector

• list_projects

  Epovest

  The projects of the account: the folders trackers are filed under (one project per tracker at most; pure organization, no effect on measurement or billing). Each carries its id, name, brand canon with its current version number (canon_version), archived flag and tracker count. The folders still in use come first, then the ones filed away (archive_project). Trackers without a project live under the virtual Default project.

  Connector

• create_graph_relationship

  RationalBloks

  Create a relationship between two nodes in a deployed graph project. The rel_type must match a relationship key from the project schema. Use get_graph_data_schema to see available relationship types. Example: rel_type: "authored" from_id: "alan-turing-001" to_id: "on-computable-numbers-001" data: {"year": 1936} The from_id and to_id must be entity_ids of existing nodes.

  Connector

• query-docs

  xpay✦ DevTools Collection

  Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

  Connector

• get_about

  cricket-travel

  Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.

  Connector

• create_funnel

  convalytics

  Create a new funnel on a project. Steps are 2–10 ordered events or pageview paths. conversionWindowMs caps how long a visitor has between consecutive steps (default 7 days); this is the step-to-step limit, without which a funnel is just event co-occurrence. Returns { id } on success.

  Connector

• get_install_instructions

  petal-components-mcp

  Get the canonical steps for installing petal_components in a Phoenix project. Call this when the user asks to install petal_components, when you are setting up a new Phoenix project that needs UI components, or when verifying an existing installation. Returns step-by-step instructions covering mix.exs, mix deps.get, Tailwind v4 CSS config, and the web module import. Steps are idempotent - safe to follow on a project that is partially configured.

  Connector

• twprojects-update_custom_item_record

  mcp

  Update a record on a custom item type. Only the fields you supply are changed; others are left as-is. Set section_id to null to remove the record from any section. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

  Connector