ReportRaja MCP

ReportRaja is an MCP server that builds weekly client reports from plain-language input including accomplishments, hours logged, blockers, and next-week plans. It provides tools to create structured data reports, render plain text for email, list templates, and calculate week boundaries. All computations are done per request with no data storage.

Visit MagicTeams

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by MagicTeams

MCP endpoint (Streamable HTTP)

https://report-raja.magicteams.ai/mcp

Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 4 of 4 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 3:53 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Build a structured weekly client report with accomplishments and hours
Render a weekly report as plain text ready for email
List built-in report layouts and sections
Return the Monday-to-Sunday week containing a given date

Source and maintenance

Community listingRegistry 1.0.0

mcp-registry: io.github.everyai-com/report-raja@1.0.0 Source repository

Maintenance checked: Nov 6, 2026, 3:14 PM UTC

Protocol and capabilities

Server: report-raja 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 4 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

ReportRaja builds weekly client reports. Computed per request, nothing stored.

Tools

4 advertised

create_weekly_report — Create weekly report

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

create_weekly_report input schema

{
  "type": "object",
  "required": [
    "client_name",
    "week_start",
    "accomplishments"
  ],
  "properties": {
    "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."
    },
    "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."
    },
    "client_name": {
      "type": "string",
      "minLength": 1,
      "description": "Client the report is for, e.g. \"Globex\""
    },
    "hours_logged": {
      "type": "number",
      "minimum": 0,
      "description": "Total hours worked this week, >= 0, e.g. 32. Omit if not tracked."
    },
    "accomplishments": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "What was done this week, one short item per entry (at least one), e.g. [\"Shipped login\", \"Fixed 3 bugs\"]"
    }
  }
}

create_weekly_report output schema

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

create_weekly_report annotations

{
  "title": "Create weekly report",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

render_report_text — Render report text

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

render_report_text input schema

{
  "type": "object",
  "required": [
    "client_name",
    "week_start",
    "accomplishments"
  ],
  "properties": {
    "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."
    },
    "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."
    },
    "client_name": {
      "type": "string",
      "minLength": 1,
      "description": "Client the report is for, e.g. \"Globex\""
    },
    "hours_logged": {
      "type": "number",
      "minimum": 0,
      "description": "Total hours worked this week, >= 0, e.g. 32. Omit if not tracked."
    },
    "accomplishments": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "What was done this week, one short item per entry (at least one), e.g. [\"Shipped login\", \"Fixed 3 bugs\"]"
    }
  }
}

render_report_text output schema

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

render_report_text annotations

{
  "title": "Render report text",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

report_templates — Report templates

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

report_templates input schema

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

report_templates output schema

{
  "type": "object",
  "required": [
    "templates"
  ],
  "properties": {
    "templates": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "name",
          "sections"
        ],
        "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."
          }
        }
      },
      "description": "Built-in report templates."
    }
  }
}

report_templates annotations

{
  "title": "Report templates",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

week_bounds — Week bounds

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

week_bounds input schema

{
  "type": "object",
  "required": [
    "date"
  ],
  "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"
    }
  }
}

week_bounds output schema

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

week_bounds annotations

{
  "title": "Week bounds",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 305 ms
95th percentile latency: 305 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 3:53 PM UTC · probe · passed · 305 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http reportraja-mcp https://report-raja.magicteams.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add reportraja-mcp --url https://report-raja.magicteams.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable reportraja-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "reportraja-mcp": {
      "type": "streamableHttp",
      "url": "https://report-raja.magicteams.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start reportraja-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "reportraja-mcp": {
      "type": "http",
      "url": "https://report-raja.magicteams.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http reportraja-mcp https://report-raja.magicteams.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://report-raja.magicteams.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

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

Let your agent find its tools

Find servers like ReportRaja MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 5,453

ReportRaja MCP

Endpoint and access

What its tools do

Read-only (4)

Checks and signals

What you can do with it

Source and maintenance

Protocol and capabilities

Server-provided instructions

Tools

Prompts

Resources

90-day uptime

30-day availability

Maintenance history

Connect from your client

Claude Code

Codex

Cursor

Cline

VS Code

Gemini CLI

Claude Desktop

Windsurf

Let your agent find its tools

Other productivity and knowledge servers