A powerful MCP server built with NitroStack
Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server):
{
"mcpServers": {
// your other mcp servers
"meeting2mission": {
"url": "https://meeting2mission-1-one-piece-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
}
}
}
Connect remote tools directly via Claude's Web UI:
Configure custom tools directly via ChatGPT's Web UI:
Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json):
{
"mcpServers": {
// your other mcp servers
"meeting2mission": {
"serverUrl": "https://meeting2mission-1-one-piece-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
}
}
}
Add the following configuration block to your Codex configuration file (~/.codex/config.toml):
[mcp_servers.meeting2mission] url = "https://meeting2mission-1-one-piece-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
Connect directly using the Server-Sent Events endpoint:
https://meeting2mission-1-one-piece-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp
Import a meeting from Zoom, Teams, Google Meet, Slack Huddles, or MP4 upload. Extracts metadata, participants, and transcript.
Extract key decisions, action items, risks, and deadlines from a meeting transcript. Applies confidence scoring and owner detection. Owner names are resolved to real identities automatically — never pass or expect email addresses here.
Create a real Jira ticket from a decision with owner assignment and deadline. If confidence is below 80%, no ticket is created and the decision is flagged for manual approval instead.
Update a Jira ticket status/transition and optionally add a comment.
Fetch the current status of a Jira ticket.
Transition a Jira ticket to Done with a resolution comment.
Create a real Google Calendar event (deadline reminder) for a task.
Create a real Google Calendar deadline event for a task (alias of create_calendar_event with eventType=deadline).
Create a real Google Calendar reminder event ahead of a task deadline.
Send a real Slack message summarizing decisions, owner assignments, and deadlines from a meeting.
Send a real Slack escalation ping for an overdue task to the manager/escalation channel.
Send a real Slack approval request for a low-confidence decision (confidence < 80%) before any ticket/owner/deadline is created.
Create a real GitHub issue linked to a task, and record the issue URL on the task.
Fetch real pull requests from the configured GitHub repository.
Fetch real commits from the configured GitHub repository.
Link an existing GitHub pull request number to a task/decision, tracking merge status.
Generate and publish a real weekly execution report to Notion, aggregating meetings, decisions, and task status for the given period.
Create a real Notion project page.
Append a real status update block to an existing Notion project page.
Get the Control Tower Dashboard snapshot: decisions detected, tasks created/completed/overdue, pending approvals, escalations triggered, completion rate, upcoming deadlines, and team accountability.
Send a real email to one or more recipients.
Send a real email reminder ahead of a task deadline.
Generate and email a real weekly execution report (meetings, decisions, task status) to the founder/CTO or any recipient list.
Resolve a person's name (as mentioned in a meeting transcript) into their email, Slack user ID, Jira account ID, and GitHub username. Returns a clarification request if the name is ambiguous or unknown, instead of failing.
Register or update a team member's identity mapping (name -> email/Slack/Jira/GitHub IDs), so future references to their name resolve automatically without asking again.
Run the full close-the-loop pipeline for an already-imported meeting in ONE call: extract decisions, resolve owners and deadlines automatically, create Jira tickets for high-confidence decisions, schedule calendar deadlines, and send a Slack follow-up. Low-confidence or unresolvable decisions are returned as pending approvals instead of guessed. Prefer this over manually chaining extract_decisions -> create_jira_ticket -> create_calendar_event -> send_followup.