ReportRaja

Weekly client reports: accomplishments, hours, blockers. Free.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
83%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,467Tokens (tool definitions)
~2.9 KBTypical response size
Moderate attention impact (1.15% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "report-raja": {
      "url": "https://report-raja.magicteams.ai/mcp"
    }
  }
}

Remote endpoints

https://report-raja.magicteams.ai/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢create_weekly_report(client_name, week_start, accomplishments, hours_logged, blockers, ...)

Build a structured weekly client report (report ID, week start/end, accomplishments, hours, blockers, next-week plan) as data fields. Nothing is stored. Use when the report data will be processed or shown as fields. Do NOT use for a ready-to-send text version; use render_report_text.

Input Schema

{
  "type": "object",
  "properties": {
    "client_name": {
      "type": "string",
      "minLength": 1,
      "description": "Client the report is for, e.g. \"Globex\""
    },
    "week_start": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First day of the reported week, YYYY-MM-DD (normally the Monday; use week_bounds to find it), e.g. 2026-09-28. The week ends 6 days later."
    },
    "accomplishments": {
      "type": "array",
      "minItems": 1,
      "items": {
        "type": "string"
      },
      "description": "What was done this week, one short item per entry (at least one), e.g. [\"Shipped login\", \"Fixed 3 bugs\"]"
    },
    "hours_logged": {
      "type": "number",
      "minimum": 0,
      "description": "Total hours worked this week, >= 0, e.g. 32. Omit if not tracked."
    },
    "blockers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Open issues blocking progress, one per entry, e.g. [\"Waiting on API review\"]. Default none."
    },
    "next_week": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Planned tasks for next week, one per entry. Default none."
    }
  },
  "required": [
    "client_name",
    "week_start",
    "accomplishments"
  ]
}

Output Schema

{
  "type": "object",
  "properties": {
    "report_id": {
      "type": "string",
      "description": "Report identifier, WR-YYYYMMDD-NNNN."
    },
    "client_name": {
      "type": "string",
      "description": "Client name as given."
    },
    "week_start": {
      "type": "string",
      "description": "Week start date as given, YYYY-MM-DD."
    },
    "week_end": {
      "type": "string",
      "description": "Week end date, week_start + 6 days, YYYY-MM-DD."
    },
    "accomplishments": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Accomplishments as given."
    },
    "hours_logged": {
      "type": [
        "number",
        "null"
      ],
      "description": "Hours logged, or null when not provided."
    },
    "blockers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Blockers (empty array if none)."
    },
    "next_week": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Next-week plan items (empty array if none)."
    }
  },
  "required": [
    "report_id",
    "client_name",
    "week_start",
    "week_end",
    "accomplishments",
    "hours_logged",
    "blockers",
    "next_week"
  ]
}
🟢render_report_text(client_name, week_start, accomplishments, hours_logged, blockers, ...)

Build a weekly client report from the same inputs as create_weekly_report and return it as plain text (header, accomplishments, hours, blockers, next week) ready to paste into an email or chat. Use when the user wants a readable report to send. Do NOT use when structured fields are needed; use create_weekly_report.

Input Schema

{
  "type": "object",
  "properties": {
    "client_name": {
      "type": "string",
      "minLength": 1,
      "description": "Client the report is for, e.g. \"Globex\""
    },
    "week_start": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First day of the reported week, YYYY-MM-DD (normally the Monday; use week_bounds to find it), e.g. 2026-09-28. The week ends 6 days later."
    },
    "accomplishments": {
      "type": "array",
      "minItems": 1,
      "items": {
        "type": "string"
      },
      "description": "What was done this week, one short item per entry (at least one), e.g. [\"Shipped login\", \"Fixed 3 bugs\"]"
    },
    "hours_logged": {
      "type": "number",
      "minimum": 0,
      "description": "Total hours worked this week, >= 0, e.g. 32. Omit if not tracked."
    },
    "blockers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Open issues blocking progress, one per entry, e.g. [\"Waiting on API review\"]. Default none."
    },
    "next_week": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Planned tasks for next week, one per entry. Default none."
    }
  },
  "required": [
    "client_name",
    "week_start",
    "accomplishments"
  ]
}

Output Schema

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "description": "The weekly report rendered as multi-line plain text."
    }
  },
  "required": [
    "text"
  ]
}
🟢report_templates

List the built-in report layouts (freelancer weekly, agency client update, standup digest) and the sections each one covers. Use when the user asks what report styles exist or which sections to include. Do NOT use to build a report; use create_weekly_report or render_report_text.

Input Schema

{
  "type": "object",
  "properties": {}
}

Output Schema

{
  "type": "object",
  "properties": {
    "templates": {
      "type": "array",
      "description": "Built-in report templates.",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Template id, e.g. freelancer-weekly."
          },
          "name": {
            "type": "string",
            "description": "Human-readable template name."
          },
          "sections": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Sections the template covers, in order."
          }
        },
        "required": [
          "id",
          "name",
          "sections"
        ]
      }
    }
  },
  "required": [
    "templates"
  ]
}
🟢week_bounds(date)

Return the Monday-to-Sunday week containing a given date (UTC). Use to turn a date like 'Oct 2' into the week_start for a report. Do NOT use to build the report itself; use create_weekly_report or render_report_text.

Input Schema

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Any date in the week, YYYY-MM-DD, e.g. 2026-10-02"
    }
  },
  "required": [
    "date"
  ]
}

Output Schema

{
  "type": "object",
  "properties": {
    "week_start": {
      "type": "string",
      "description": "Monday of that week, YYYY-MM-DD."
    },
    "week_end": {
      "type": "string",
      "description": "Sunday of that week, YYYY-MM-DD."
    }
  },
  "required": [
    "week_start",
    "week_end"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools