Skip to main content
Glama
RaportAgent MCP Server

RaportAgent MCP Server

by raportagent

RaportAgent MCP server

A Model Context Protocol server that puts RaportAgent inside any MCP client — Claude Desktop, Claude Code, Cursor. Ask your assistant to research a market or map a regulatory landscape, and it generates a sourced RaportAgent report, then pulls the finished markdown and its audit trail.

Thin wrapper over the RaportAgent REST API (/v1), so it inherits per-key rate limits, the credit model, and the audit trail unchanged.

Tools

Tool

What it does

generate_report

Start a report (query, optional template: compliance/pitch/saas/ecommerce/realestate/local/battlecard/duediligence/fintech). Returns a report_id; optionally polls with wait_seconds. Costs 1 credit (2 for battlecard).

get_report_status

queued / running / completed / failed

get_report

The finished report's full markdown + sections

get_report_audit

Provenance: AI models, agents, source counts, SHA-256 of the exact content

get_report_sources

Every cited source with link-health counts (working / uncertain / dead)

cancel_report

Cancel a queued/in-progress report and refund its credit

list_reports

Your recent reports

get_account

Remaining credits and plan

Related MCP server: INDUSS Research Intelligence MCP Server

Setup

  1. Get an API key: RaportAgent → My account → API keys (an ra_live_… key).

  2. Register it with your MCP client — no clone, no build, npx pulls the published package.

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{
  "mcpServers": {
    "raportagent": {
      "command": "npx",
      "args": ["-y", "@raportagent/mcp"],
      "env": {
        "RAPORTAGENT_API_KEY": "ra_live_xxx"
      }
    }
  }
}

Claude Code

claude mcp add raportagent -e RAPORTAGENT_API_KEY=ra_live_xxx -- npx -y @raportagent/mcp

Cursor

Same command/args/env shape as Claude Desktop above, under Cursor's MCP settings.

Running from source (contributing / debugging only)

git clone https://github.com/raportagent/raportagent-mcp.git
cd mcp-server
npm install
npm run build

Then point command/args at node / dist/index.js with an absolute path instead of npx.

Config

Env

Default

Notes

RAPORTAGENT_API_KEY

—

Required. ra_live_… key.

RAPORTAGENT_BASE_URL

https://raportagent.com

Override for self-hosted / staging.

Notes

  • Generation typically takes ~15 minutes. generate_report returns immediately with a report_id; the assistant should poll get_report_status (or pass wait_seconds) before get_report.

  • stdout is the MCP transport — the server logs only to stderr.

  • The API key is only ever sent to your configured RAPORTAGENT_BASE_URL.

Available Tools

4 tools
get_accountA

Show your RaportAgent account: remaining credits and plan.

Inputs: no named parameters.

get_reportA

Fetch a completed report's full markdown content and section list.

Inputs: report_id (required).

get_report_auditA

Get a report's audit trail / provenance: AI models, agents, source counts, and a SHA-256 of the exact content. Useful for compliance review and verifying a report has not been altered.

Inputs: report_id (required).

get_report_statusA

Check whether a report is queued, in_progress, completed, failed, or cancelled.

Inputs: report_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: status, content, audit trail, and account info. There is no functional overlap.

    Naming Consistency5/5

    All tools follow a consistent 'get_<noun>' pattern, making it predictable for an agent.

    Tool Count5/5

    With four tools, the set is well-scoped for a reporting and account service—neither overly sparse nor bloated.

    Completeness2/5

    The tools are entirely read-only; missing essential CRUD operations like creating, cancelling, or listing reports, which are critical for end-to-end report management.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers